From: Denis Kenzior <denkenz@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Eric Biggers <ebiggers@kernel.org>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
linux-cifs <linux-cifs@vger.kernel.org>,
Steve French <sfrench@samba.org>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org
Subject: Re: [PATCH 0/2] crypto: remove MD4 generic shash
Date: Wed, 18 Aug 2021 17:22:00 -0500 [thread overview]
Message-ID: <e2462d50-57e9-b7d7-bc07-0f365a01d215@gmail.com> (raw)
In-Reply-To: <CAMj1kXEO8PwLfT8uAYgeFF7T3TznWz4E=R1JArvCdKXk8qiAMQ@mail.gmail.com>
Hi Ard,
>> That is not something that iwd has any control over though? We have to support
>> it for as long as there are organizations using TTLS + MD5 or PEAPv0. There
Ah, my brain said MSCHAP but my fingers typed MD5.
>> are still surprisingly many today.
>>
>
> Does that code rely on MD4 as well?
>
But the answer is yes. Both PEAP and TTLS use MSCHAP or MSCHAPv2 in some form.
These are commonly used for Username/Password based WPA(2|3)-Enterprise
authentication. Think 'eduroam' for example.
MD4 is used to hash the plaintext password, but the hash is sent inside a TLS
tunnel, so there's really no immediate crypto weakness concern? At least
there's not a replacement on the horizon as far as I know. EAP-PWD has its own
problems and I doubt certificate based authentication will overtake
username/password any time soon.
Regards,
-Denis
next prev parent reply other threads:[~2021-08-18 22:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 14:46 [PATCH 0/2] crypto: remove MD4 generic shash Ard Biesheuvel
2021-08-18 14:46 ` [PATCH 1/2] fs/cifs: Incorporate obsolete MD4 crypto code Ard Biesheuvel
2021-08-18 14:46 ` [PATCH 2/2] crypto: md4 - Remove obsolete algorithm Ard Biesheuvel
2021-08-18 14:51 ` [PATCH 0/2] crypto: remove MD4 generic shash Denis Kenzior
2021-08-18 16:10 ` Ard Biesheuvel
2021-08-18 16:23 ` Denis Kenzior
2021-08-18 16:47 ` Steve French
2021-08-18 22:08 ` Jeremy Allison
2021-08-19 3:49 ` Andrew Bartlett
2021-08-19 5:18 ` Eric Biggers
2021-08-19 5:23 ` Andrew Bartlett
2021-08-18 21:11 ` ronnie sahlberg
2021-08-18 22:10 ` Ard Biesheuvel
2021-08-18 22:22 ` Denis Kenzior [this message]
2021-08-18 23:03 ` Steve French
2021-08-19 16:56 ` Denis Kenzior
2021-08-19 10:42 ` Jarkko Sakkinen
2021-08-19 17:10 ` Steve French
2021-08-19 20:54 ` ronnie sahlberg
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=e2462d50-57e9-b7d7-bc07-0f365a01d215@gmail.com \
--to=denkenz@gmail.com \
--cc=ardb@kernel.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
/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).