Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Michael Janssen <jamuraa@google.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 6/6] shared/att: Fix signed write without transparent signing
Date: Fri, 27 Feb 2015 16:27:02 +0100	[thread overview]
Message-ID: <1758603.Tr6JIHPuTr@uw000953> (raw)
In-Reply-To: <CAJLTA8gDLn-AkGHfCyye4s_RHL5=pcrMVSFtA4dTac3cHXxoeQ@mail.gmail.com>

Hi Michael,

On Friday 27 of February 2015 07:21:51 Michael Janssen wrote:
> Hi Szymon,
> 
> On Fri, Feb 27, 2015 at 7:01 AM, Szymon Janc <szymon.janc@tieto.com> wrote:
> > If local key wasn't set by bt_att_set_local_key() assume that signing
> > is done by bt_att_send() caller ie. gattrib code.
> > ---
> >  src/shared/att.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/src/shared/att.c b/src/shared/att.c
> > index 9787377..b20af21 100644
> > --- a/src/shared/att.c
> > +++ b/src/shared/att.c
> > @@ -308,7 +308,7 @@ static bool encode_pdu(struct bt_att *att, struct att_send_op *op,
> >
> >         sign = att->local_sign;
> >         if (!sign)
> > -               goto fail;
> > +               true;
> 
> This should be 'return true;' I think?

Good catch. I've got this right locally but forgot to amend before generating
patch :)

> 
> >
> >         if (!sign->counter(&sign_cnt, sign->user_data))
> >                 goto fail;
> > --
> > 1.9.3
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 
> 

-- 
Best regards, 
Szymon Janc

  reply	other threads:[~2015-02-27 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 15:01 [PATCH 1/6] android/gatt: Fix client signed write on encrypted link Szymon Janc
2015-02-27 15:01 ` [PATCH 2/6] android/bluetooth: Store if CSRK is authenticated Szymon Janc
2015-02-27 15:01 ` [PATCH 3/6] android/bluetooth: Add support for CSRK authetication level Szymon Janc
2015-02-27 15:01 ` [PATCH 4/6] android/gatt: Fix check if CSRK is authenticated Szymon Janc
2015-02-27 15:01 ` [PATCH 5/6] android/gatt: Fix error message in signed_write_cmd Szymon Janc
2015-02-27 15:01 ` [PATCH 6/6] shared/att: Fix signed write without transparent signing Szymon Janc
2015-02-27 15:21   ` Michael Janssen
2015-02-27 15:27     ` Szymon Janc [this message]
2015-02-27 16:02       ` Luiz Augusto von Dentz
2015-02-27 21:33 ` [PATCH 1/6] android/gatt: Fix client signed write on encrypted link Szymon Janc

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=1758603.Tr6JIHPuTr@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=jamuraa@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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