($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Ronan Pigott" <ronan@rjp.ie>
To: "James Prestwood" <prestwoj@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: SAE password identifiers?
Date: Wed, 06 Dec 2023 02:16:28 +0000	[thread overview]
Message-ID: <9393bad9fd0f9aca758e65a0a998d39787277498@rjp.ie> (raw)
In-Reply-To: <a61d267d-774a-430e-adc6-5fb1f5075860@gmail.com>

Hey James,

December 5, 2023 at 8:48 AM, "James Prestwood" <prestwoj@gmail.com> wrote:

> I went ahead and added password identifier support (patches on the list).

Wow, that was quick! Awesome, thanks!

> I've tested this with hostapd directly but if you have an actual production device that supports password identifiers it would be nice to validate this actually works.

Unfortunately just my usual router with openwrt. I don't even think the luci interface supports it atm, but the hostapd version used certainly does.

Cheers,
Ronan

      parent reply	other threads:[~2023-12-06  2:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  9:56 SAE password identifiers? Ronan Pigott
2023-12-04 14:40 ` James Prestwood
2023-12-05 15:48   ` James Prestwood
2023-12-06  2:16   ` Ronan Pigott [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=9393bad9fd0f9aca758e65a0a998d39787277498@rjp.ie \
    --to=ronan@rjp.ie \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).