public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH v5 2/4] dpp: add DPP authentication protocol
Date: Fri, 17 Dec 2021 14:19:11 -0600	[thread overview]
Message-ID: <a2bfc724-dfb8-8c75-7f05-1ee6523b48ad@gmail.com> (raw)
In-Reply-To: 20211217191451.179444-2-prestwoj@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

Hi James,

On 12/17/21 13:14, James Prestwood wrote:
> This implements the DPP protocol used to authenticate to a
> DPP configurator.
> 
> Note this is not a full implementation of the protocol and
> there are a few missing features which will be added as
> needed:
> 
>   - Mutual authentication (needed for BLE bootstrapping)
>   - Configurator support
>   - Initiator role
> ---
>   src/dpp.c | 491 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 491 insertions(+)
> 
> v5:
>   * Updated use of wrap/unwrap APIs.
>   * Better commented how AAD is used with wrapping/unwrapping
> 

<snip>

> +static void dpp_free_auth_data(struct dpp_sm *dpp)
> +{
> +	if (dpp->proto_public) {
> +		l_ecc_point_free(dpp->proto_public);
> +		dpp->proto_public = NULL;
> +	}
> +
> +	if (dpp->proto_private) {
> +		l_ecc_scalar_free(dpp->proto_private);
> +		dpp->proto_private = NULL;
> +	}
> +
> +	if (dpp->i_proto_public) {
> +		l_ecc_point_free(dpp->i_proto_public);
> +		dpp->i_proto_public = NULL;
> +	}

Should we be paranoid and explicit_bzero the nonces and keys?

Applied, thanks.

Regards,
-Denis

             reply	other threads:[~2021-12-17 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 20:19 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-17 21:18 [PATCH v5 2/4] dpp: add DPP authentication protocol James Prestwood
2021-12-17 19:14 James Prestwood

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=a2bfc724-dfb8-8c75-7f05-1ee6523b48ad@gmail.com \
    --to=iwd@lists.linux.dev \
    /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