public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v4 1/4] doc: PKEX support for DPP
Date: Tue, 7 Nov 2023 20:28:51 -0600	[thread overview]
Message-ID: <86b15990-4f85-4fdc-9747-8ba8f9e263be@gmail.com> (raw)
In-Reply-To: <20231107170629.1831655-2-prestwoj@gmail.com>

Hi James,

On 11/7/23 11:06, James Prestwood wrote:
> PKEX is part of the WFA EasyConnect specification and is
> an additional boostrapping method (like QR codes) for
> exchanging public keys between a configurator and enrollee.
> 
> PKEX operates over wifi and requires a key/code be exchanged
> prior to the protocol. The key is used to encrypt the exchange
> of the boostrapping information, then DPP authentication is
> started immediately aftewards.
> 
> This can be useful for devices which don't have the ability to
> scan a QR code, or even as a more convenient way to share
> wireless credentials if the PSK is very secure (i.e. not a
> human readable string).
> 
> PKEX would be used via the three DBus APIs on a new interface
> SharedCodeDeviceProvisioning.
> 
> ConfigureEnrollee(a{sv}) will start a configurator with a
> static shared code (optionally identifier) passed in as the
> argument to this method.
> 
> StartEnrollee(a{sv}) will start a PKEX enrollee using a static
> shared code (optionally identifier) passed as the argument to
> the method.
> 
> StartConfigurator(o) will start a PKEX configurator and use the
> agent specified by the path argument. The configurator will query
> the agent for a specific code when an enrollee sends the initial
> exchange message.
> 
> After the PKEX protocol is finished, DPP bootstrapping keys have
> been exchanged and DPP Authentication will start, followed by
> configuration.
> ---
>   doc/device-provisioning-api.txt | 142 ++++++++++++++++++++++++++++++++
>   1 file changed, 142 insertions(+)
> 

Applied, thanks.

Regards,
-Denis


  reply	other threads:[~2023-11-08  2:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 17:06 [PATCH v4 0/4] DPP PKEX Changes James Prestwood
2023-11-07 17:06 ` [PATCH v4 1/4] doc: PKEX support for DPP James Prestwood
2023-11-08  2:28   ` Denis Kenzior [this message]
2023-11-07 17:06 ` [PATCH v4 2/4] dpp: initial version of PKEX enrollee support James Prestwood
2023-11-08  3:11   ` Denis Kenzior
2023-11-08 12:42     ` James Prestwood
2023-11-08 15:07       ` Denis Kenzior
2023-11-08 15:14         ` James Prestwood
2023-11-07 17:06 ` [PATCH v4 3/4] dpp: initial version of PKEX configurator support James Prestwood
2023-11-07 17:06 ` [PATCH v4 4/4] dpp: Add StartConfigurator, PKEX agent support 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=86b15990-4f85-4fdc-9747-8ba8f9e263be@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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