Nim's status change of no longer affects ppp I think was just a mistake and rectified, but the rectification wasn't recorded in a new message.
This bug report no longer affects ppp >= 2.4.9, as it was fixed upstream and is the reason the corresponding Debian bug was closed. This SRU patch request is for Ubuntu 20.04 which is still using an older ppp. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1890814 Title: Handle PPP non-compliant success packets Status in ppp package in Ubuntu: Confirmed Status in ppp package in Debian: Fix Released Bug description: [Impact] According to RFC2759, the format of PPP success packets is : "S=<auth_string> M=<message>" Recently Windows Server 2019 has started producing non-complaint PPP success packets which have a space missing before the M= characters. PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting to an affected Windows Server 2019 VPN server will get the following error message during MS-CHAPv2 authentication : MS-CHAPv2 Success packet is badly formed If the following upstream ppp patch is applied, it will handle the non-compliant, missing-space before M= success packets : https://github.com/paulusmack/ppp/commit/3cd95baf3f1de1d5a9bc89be0f4c3215ceb5aefe.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1890814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
