Your message dated Sun, 25 Feb 2018 23:25:03 +0000 with message-id <[email protected]> and subject line Bug#891413: fixed in ppp 2.4.7-2+2 has caused the Debian Bug report #891413, regarding ppp: MS-CHAP authentication broken to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 891413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891413 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: network-manager-pptp Version: 1.2.4-5+b1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I did a normal apt upgrade which updated network-manager-pptp, network-manager, ppp, and pptp-linux to the latest testing versions as of 24Feb2018. This caused my PPTP vpn connection to fail to connect because of authentication issues with the MSCHAP and MSCHAPv2 protocals. Feb 25 02:10:11 localhost pppd[31955]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Feb 25 02:10:11 localhost NetworkManager[16904]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Feb 25 02:10:11 localhost pppd[31955]: pppd 2.4.7 started by root, uid 0 Feb 25 02:10:11 localhost systemd-udevd[31959]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Feb 25 02:10:11 localhost NetworkManager[16904]: <info> [1519553411.5971] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/6) Feb 25 02:10:11 localhost pppd[31955]: Using interface ppp0 Feb 25 02:10:11 localhost NetworkManager[16904]: Using interface ppp0 Feb 25 02:10:11 localhost NetworkManager[16904]: Connect: ppp0 <--> /dev/pts/7 Feb 25 02:10:11 localhost pppd[31955]: Connect: ppp0 <--> /dev/pts/7 Feb 25 02:10:11 localhost pptp[31960]: nm-pptp-service-31951 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Feb 25 02:10:11 localhost NetworkManager[16904]: Error: either "to" is duplicate, or "uid" is a garbage. Feb 25 02:10:11 localhost NetworkManager[16904]: <info> [1519553411.6134] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Feb 25 02:10:11 localhost NetworkManager[16904]: <info> [1519553411.6134] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Feb 25 02:10:11 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request' Feb 25 02:10:11 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Feb 25 02:10:11 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Feb 25 02:10:12 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request' Feb 25 02:10:12 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Feb 25 02:10:12 localhost pptp[32023]: nm-pptp-service-31951 log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 62435, peer's call ID 51712). Feb 25 02:10:13 localhost pppd[31955]: MS-CHAP authentication failed: Feb 25 02:10:13 localhost NetworkManager[16904]: MS-CHAP authentication failed: Feb 25 02:10:13 localhost NetworkManager[16904]: CHAP authentication failed Feb 25 02:10:13 localhost pppd[31955]: CHAP authentication failed Feb 25 02:10:13 localhost pppd[31955]: Connection terminated. Feb 25 02:10:13 localhost NetworkManager[16904]: Connection terminated. Feb 25 02:10:13 localhost charon-nm[31069]: 13[KNL] interface ppp0 deleted * What exactly did you do (or not do) that was effective (or ineffective)? Downgrading just pptp-linux was not effective so I also downgraded the following packages as well to get ppp to version 2.7.4-1+4: gir1.2-nma-1.0 libnma0 network-manager network-manager-gnome network-manager-pptp network-manager-pptp-gnome ppp pptp-linux pptpd * What was the outcome of this action? After downgrading the packages, The PPTP base vpn connection is working. * What outcome did you expect instead? I would have expected that the upgrade would not have broken MSCHAP and MSCHAPv2 authenthication. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-pptp depends on: ii libc6 2.26-6 ii libglib2.0-0 2.54.3-2 ii libnm0 1.10.4-1+b1 ii network-manager 1.10.4-1 ii ppp 2.4.7-2+1 ii pptp-linux 1.9.0+ds-2 network-manager-pptp recommends no packages. network-manager-pptp suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: ppp Source-Version: 2.4.7-2+2 We believe that the bug you reported is fixed in the latest version of ppp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Boot <[email protected]> (supplier of updated ppp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 25 Feb 2018 22:28:25 +0000 Source: ppp Binary: ppp ppp-udeb ppp-dev Architecture: source Version: 2.4.7-2+2 Distribution: unstable Urgency: medium Maintainer: Chris Boot <[email protected]> Changed-By: Chris Boot <[email protected]> Description: ppp - Point-to-Point Protocol (PPP) - daemon ppp-dev - Point-to-Point Protocol (PPP) - development files ppp-udeb - Point-to-Point Protocol (PPP) - package for Debian Installer (udeb) Closes: 891413 Changes: ppp (2.4.7-2+2) unstable; urgency=medium . * Correct a bug in MS-CHAP authentication introduced in 2.4.7-2+1~exp1 which prevented such authentication from working altogether. (Closes: #891413) Checksums-Sha1: 9455a40c46cc65cb2713e5a98ff6eb4c6a9ef1c8 2245 ppp_2.4.7-2+2.dsc 6c61365253a201a831c5ade7bb45a800c5268a85 129100 ppp_2.4.7-2+2.debian.tar.xz Checksums-Sha256: baaa51f3f2d328a8727f3fb22fa6273154e3337054ac9e78bec3bb6a3941bd7e 2245 ppp_2.4.7-2+2.dsc cc7238166c2fcad35c7ee824db3c41028e143b98aed9a636926abcffb916dabe 129100 ppp_2.4.7-2+2.debian.tar.xz Files: 890a3b89ad3b46ac3256c8bc5de2e5a9 2245 admin optional ppp_2.4.7-2+2.dsc 583cc220b3754a4634e19ae5f0f40e4b 129100 admin optional ppp_2.4.7-2+2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEakxNgo23DDPFqbsY1o29Dt2gqWQFAlqTOT1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZB NEM0RDgyOERCNzBDMzNDNUE5QkIxOEQ2OERCRDBFRERBMEE5NjQRHGJvb3RjQGRl Ymlhbi5vcmcACgkQ1o29Dt2gqWRoyQ//d9aw5KDbu9jJ1r+/w+sOIzuDOIaGQVQf Ll5miz7jjASoADQVO0sAJKrK85Vg8zB8x3Ct0/4O7Hv9VdhCMd3ZHs3tJWXyxlWz 3SSL+lcXTOXZOA7IDXLw9S+UK3QQxjCR/fD548fCcuxZIT+RQwlUCZYC45a0W+8k RkfgdQQN12LECbfvmVm3oF5WHjabpYEAaKpym1seK2pH7QsUoR3Dvso/SUCrQuGE wXkybOPsgiBApYUy7c/PHLm9n0qhRo8e1hjfMwtltzqqg4JEbyHHdWAxMI6cT/4Y bpR3UALQtM7hWV3iXijGhY3yfc6mNmqXSe3wIkBJKuQEemznn2IqreiG8kNPQCKP Rb1UM2unyoX/ef0C1LYnhGnD/DRubHitEMFGcZPmOi7X0Q2u1MkAgGAG5T6FbufG 2jMi7p44em4cqhPt3cOVx8/b6lW5mANj6LWj/vLnnNu/ur9fwZYWcvJZTm8dZuEF RNhd4hZ+GOoif6ulH8PBYVo9fuC3DZG+FaEa/lHA40KTQVCOUOjhxTpVtUmLBqzx C44ZVZXnM6kAlCS3QvjS0Y3viU9NLWaEnB16EbCsjBtZloXFu97n0GUGWCLT82Xf AoRdAkRblvGzqO98mo0niy4JUTydcM6pnoQ8z7gPXl2DPVB13tIosz79zPgbpfyb w72JEt9BTiw= =9cyM -----END PGP SIGNATURE-----
--- End Message ---
