Jump to content

Talk:MS-CHAP

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Untitled

[edit]

there should be a mention of MS-CHAPv2's fatal security flaws, namely the padding of the DES key with 16 bits of zeros which effectively makes brute forcing dictionary attacks faster by at least 5 orders of magnitude...this attack is discussed in the LEAP article so it should probably be mentioned here --Michael Lynn 00:00, 21 March 2007 (UTC)[reply]

I suggest we redirect 'MSCHAP' to this page. (I don't know how to do it). 132.206.197.155 21:03, 6 June 2007 (UTC)[reply]

MS-CHAP and home routers

[edit]

It would be nice if someone wrote an overview of how well do SOHO routers implement MS-CHAP authentication. Most vendors don't specify which authentication scheme is supported, which in reality can vary from PAP/CHAP to also supporting MS-CHAPv1 or even MS-CHAPv2. Implementation of the latter is the most rare in routers, I guess, but it isn't so rare on the provider side. 213.234.235.82 (talk) 13:19, 3 February 2009 (UTC)[reply]

PEAP

[edit]

"It is further used as the main authentication option of the Protected Extensible Authentication Protocol (PEAP)." It should be metioned, that it is only for PEAPv0 not PEAPv1. Microsoft refers to PEAPv0 as PEAP, because it is the only version they use. Source: https://wiki.riteme.site/wiki/Protected_Extensible_Authentication_Protocol#PEAPv0_with_EAP-MSCHAPv2 --KaffeeMitSpeck (talk) 16:14, 25 February 2022 (UTC)[reply]

MSCHAPv2 incompatible with Windows 11 22h2

[edit]

According to several articles, one should note that in Windows 11 22h2, with the default activation of Windows Defender Credential Guard, you can't authenticate with MSCHAPv2. 141.134.100.127 (talk) 13:48, 27 June 2023 (UTC)[reply]