From: Emil Velikov <emil.l.velikov@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: GCMP and other unknown ciphers
Date: Mon, 7 Nov 2022 15:53:55 +0000 [thread overview]
Message-ID: <CACvgo53gsrbynh0e-YXL9nV+HJF=xiRuR2Cj38pYCeApbRRm4w@mail.gmail.com> (raw)
In-Reply-To: <afb76858-3db4-11c9-5d6b-d3cf6d451052@gmail.com>
On Tue, 25 Oct 2022 at 16:32, Denis Kenzior <denkenz@gmail.com> wrote:
>
> Hi Emil,
>
>
> >>>
> >>> Was my analysis correct - is GCMP supported? Are there any plans on doing so?
> >>
> >> No real plans, patches are always welcome.
> >>
> > Do you have a rough estimate of how much work that might be - are we
> > talking about weeks or months? How does one get access to the 802.11
> > spec these days?
> >
>
> There is a patchset on the mailing list that implements all ciphers listed in
> 802.11, including GCMP. Only tested in a synthetic environment since none of my
> commercial APs seem to support anything besides TKIP/CCMP.
>
I've tested it against a Netgear Nighthawk X10 with the following combinations:
WPA2 Personal (without SHA256)
- CCMP-128 (AES) + GCMP
- CCMP-256 only
- GCMP-256 only
All of the above are working like a charm. I haven't tried any
Enterprise combinations due to some unrelated hiccups on my test rig.
Huge thanks for the amazing help
Emil
prev parent reply other threads:[~2022-11-07 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:22 GCMP and other unknown ciphers Emil Velikov
2022-10-06 14:34 ` Denis Kenzior
2022-10-25 14:27 ` Emil Velikov
2022-10-25 15:31 ` Denis Kenzior
2022-11-07 15:53 ` Emil Velikov [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='CACvgo53gsrbynh0e-YXL9nV+HJF=xiRuR2Cj38pYCeApbRRm4w@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=denkenz@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;
as well as URLs for NNTP newsgroup(s).