public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v5 00/10] DPP PKEX Changes
Date: Wed,  8 Nov 2023 09:21:45 -0800	[thread overview]
Message-ID: <20231108172155.2129509-1-prestwoj@gmail.com> (raw)

v5:
 * Separate the DPP/PKEX interfaces using a new enum
   to distinguish which interfaces is using the dpp_sm.
   Similarly added a refcount to the dpp_sm object so when
   one interface goes away it won't destroy the SM for the
   other.
 * Removed unneeded checks on the identifier, and added
   some:
      - Assume utf8/null terminated when coming from DBus
        (just check length)
      - Validate utf8/length when coming from the peer.
 * Enforce any user-disabled bands when generating the
   default frequency list.
 * Return error on Stop() if not started. This is an API
   change, but I thought it made sense so its very clear
   when Stop() is called on the incorrect interface.
 * Included autotest changes.

James Prestwood (10):
  dpp-util: fix typo, 'REQUST'
  dpp: introduce dpp_interface type, prep for PKEX
  auto-t: fix testDPP after Stop() change
  doc: document Stop() correctly for both DPP interfaces
  dpp: initial version of PKEX enrollee support
  dpp: initial version of PKEX configurator support
  dpp: Add StartConfigurator, PKEX agent support
  auto-t: add utils for wpa_supplicant PKEX
  auto-t: add APIs for PKEX
  auto-t: add DPP PKEX tests

 autotests/testDPP/connection_test.py |    9 +-
 autotests/testDPP/hostapd.conf       |    2 +-
 autotests/testDPP/hw.conf            |    5 +-
 autotests/testDPP/pkex_test.py       |  209 ++++
 autotests/testDPP/ssidCCMP.psk       |   12 +
 autotests/util/iwd.py                |  152 ++-
 autotests/util/wpas.py               |   40 +-
 doc/device-provisioning-api.txt      |    8 +-
 src/dpp-util.h                       |    2 +-
 src/dpp.c                            | 1722 ++++++++++++++++++++++++--
 10 files changed, 2056 insertions(+), 105 deletions(-)
 create mode 100644 autotests/testDPP/pkex_test.py

-- 
2.25.1


             reply	other threads:[~2023-11-08 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 17:21 James Prestwood [this message]
2023-11-08 17:21 ` [PATCH v5 01/10] dpp-util: fix typo, 'REQUST' James Prestwood
2023-11-08 17:21 ` [PATCH v5 02/10] dpp: introduce dpp_interface type, prep for PKEX James Prestwood
2023-11-08 17:21 ` [PATCH v5 03/10] auto-t: fix testDPP after Stop() change James Prestwood
2023-11-08 17:21 ` [PATCH v5 04/10] doc: document Stop() correctly for both DPP interfaces James Prestwood
2023-11-08 17:21 ` [PATCH v5 05/10] dpp: initial version of PKEX enrollee support James Prestwood
2023-11-08 17:21 ` [PATCH v5 06/10] dpp: initial version of PKEX configurator support James Prestwood
2023-11-08 17:21 ` [PATCH v5 07/10] dpp: Add StartConfigurator, PKEX agent support James Prestwood
2023-11-08 17:21 ` [PATCH v5 08/10] auto-t: add utils for wpa_supplicant PKEX James Prestwood
2023-11-08 17:21 ` [PATCH v5 09/10] auto-t: add APIs for PKEX James Prestwood
2023-11-08 17:21 ` [PATCH v5 10/10] auto-t: add DPP PKEX tests James Prestwood
2023-11-09 16:35 ` [PATCH v5 00/10] DPP PKEX Changes Denis Kenzior

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=20231108172155.2129509-1-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=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