Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@codecoup.pl>
To: linux-bluetooth@vger.kernel.org,
	"Łukasz Rymanowski" <lukasz.rymanowski@codecoup.pl>
Cc: "Łukasz Rymanowski" <lukasz.rymanowski@codecoup.pl>
Subject: Re: [PATCH BlueZ] tools/btgatt-client: Add option to set BT_SECURITY_FIPS
Date: Wed, 13 May 2020 13:03:26 +0200	[thread overview]
Message-ID: <4555946.31r3eYUQgx@ix> (raw)
In-Reply-To: <20200508132349.6495-1-lukasz.rymanowski@codecoup.pl>

Hi Łukasz,

On Friday, 8 May 2020 15:23:49 CEST Łukasz Rymanowski wrote:
> Need for GAP/SEC/SEM/BI-10-C
> ---
>  tools/btgatt-client.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/btgatt-client.c b/tools/btgatt-client.c
> index 82a9e3fe0..bc762dba1 100644
> --- a/tools/btgatt-client.c
> +++ b/tools/btgatt-client.c
> @@ -1492,8 +1492,8 @@ static void usage(void)
>  		"\t-d, --dest <addr>\t\tSpecify the destination address\n"
>  		"\t-t, --type [random|public] \tSpecify the LE address 
type\n"
>  		"\t-m, --mtu <mtu> \t\tThe ATT MTU to use\n"
> -		"\t-s, --security-level <sec> \tSet security level (low|"
> -								
"medium|high)\n"
> +		"\t-s, --security-level <sec> \tSet security level (low|
medium|"
> +								
"high|fips)\n"
>  		"\t-v, --verbose\t\t\tEnable extra logging\n"
>  		"\t-h, --help\t\t\tDisplay help\n");
>  }
> @@ -1537,6 +1537,8 @@ int main(int argc, char *argv[])
>  				sec = BT_SECURITY_MEDIUM;
>  			else if (strcmp(optarg, "high") == 0)
>  				sec = BT_SECURITY_HIGH;
> +			else if (strcmp(optarg, "fips") == 0)
> +				sec = BT_SECURITY_FIPS;
>  			else {
>  				fprintf(stderr, "Invalid security 
level\n");
>  				return EXIT_FAILURE;

Patch applied, thanks.

-- 
pozdrawiam
Szymon Janc



      reply	other threads:[~2020-05-13 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 13:23 [PATCH BlueZ] tools/btgatt-client: Add option to set BT_SECURITY_FIPS Łukasz Rymanowski
2020-05-13 11:03 ` Szymon Janc [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4555946.31r3eYUQgx@ix \
    --to=szymon.janc@codecoup.pl \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@codecoup.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox