iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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: Tue, 25 Oct 2022 15:27:34 +0100	[thread overview]
Message-ID: <CACvgo50aJHxkC-3E7OHDfjkyH5Rrp+Za+F-ATTCs8w-oX=dhcA@mail.gmail.com> (raw)
In-Reply-To: <772f09aa-fe9e-708e-2ec2-a89f8784d391@gmail.com>

Hi Denis,

Sorry for the late reply - been busy with some non-computer stuff.

On Thu, 6 Oct 2022 at 15:34, Denis Kenzior <denkenz@gmail.com> wrote:
>
> Hi Emil,
>
> On 10/6/22 08:22, Emil Velikov wrote:
> > Greetings team,
> >
> > Recently we've noticed that IWD fails to connect to WPA2-PSK networks
> > whenever GCMP+CCMP cipher is used. Browsing through the IWD code-base
> > it appears that it lacks support for GCMP, GCMP-256 and CCMP-256
> > amongst others.
>
> We do not support or select GCMP. But I'm not sure why this would prevent a
> connection?  We would always select CCMP instead.  See wiphy_select_cipher().
>
> Hmm... maybe we reject GCMP at a lower layer...?  Try the attached patch?
>

Now that I've got the hardware at hand, it looks like iwd does not
list the network at all. I will try your patch and report shortly.

Details:
 - Nighthawk X10 running dd-wrt
 - WPA2 Personal (without SHA256)
 - CCMP-128(AES) + GCMP

> >
> > 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?

> >
> > Somewhat relatedly - is there a configuration knob that one can switch
> > and let IWD fall-back to the other supported ciphers? In the GCMP+CCMP
> > case, we can opt for CCMP for example.
> >
>
> This should already happen.
>
That was my assumption as well, yet empirically it does not.

Thanks again
Emil

  reply	other threads:[~2022-10-25 14:27 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 [this message]
2022-10-25 15:31     ` Denis Kenzior
2022-11-07 15:53       ` Emil Velikov

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='CACvgo50aJHxkC-3E7OHDfjkyH5Rrp+Za+F-ATTCs8w-oX=dhcA@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).