Control: forcemerge 891413 -1 On 25/02/18 21:22, Alexander Elbs wrote: > On Sun, Feb 25, 2018 at 08:17:54PM +0000, Chris Boot wrote: >> On 25/02/18 14:19, Alexander Elbs wrote: >>> On Sun, Feb 25, 2018 at 12:17:28AM +0000, Chris Boot wrote: >>>> >>>> sstp-client isn't in Debian so there's a limit to how much I can help, >>>> but did you try rebuilding the sstp-client packages against the latest >>>> ppp-dev? >>> >>> Yes, no luck. When I upgrade just the ppp package to my custom version >>> without >>> the patch it works again. >>> Can I help to narrow it down what is going wrong? Log files? >> >> Hi Alexander, >> >> Yes, pppd logs would be very helpful, especially if you can enable the >> 'debug' option in the peer file or NetworkManager's options (but still >> helpful if you can't). >> >> Given I have a similar report with PPTP now (Bug#891413 and Chris Dow's >> comment here) I suspect this is a larger issue with my patch so I need >> to try to reproduce this. > > Hi, > > I attach two logs: one working.log (rebuild ppp with just the patch removed) > and > non-working.log (ppp 2.4.7-2+1). [snip]
Hi Alexander, Thank you very much for the detailed logs and configuration files, they were very helpful. You are using MS-CHAP (v2) which uses MD4 internally, and it turns out the MD4 code in pppd was somewhat strange in ways I missed. I'll merge this bug into the other bug about MS-CHAP authentication with PPTP now. I will upload a version with a fix either later today or tomorrow. Cheers, Chris -- Chris Boot bo...@debian.org
signature.asc
Description: OpenPGP digital signature
