ppp (2.5.5-1+1~exp1) experimental; urgency=medium pppd no longer supports being run as an unprivileged user (with membership of the dip group). This should have no effect on the vast majority of users; users should be using pppd via some kind of process or networking supervisor (for example NetworkManager or systemd), or should invoke pon/poff via sudo. If you rely on being able to start/stop pppd as an unprivileged user, please refer to /usr/share/doc/ppp/README.Debian.gz for instructions on how to restore this functionality. This release also includes upstream changes from ppp 2.5.3 and 2.5.4 that may affect existing configurations: - pppd now refuses to use secrets files (such as /etc/ppp/chap-secrets) that are readable by group or other; previously it only warned. Scripts run as root (such as /etc/ppp/ip-up), privileged options files and secrets files must be owned by root, and so must every directory in their path, and none may be writable by group or other. Check the permissions of any of these files you have modified. - The defaultroute option now always adds a default route, without first checking whether one already exists; use the new defaultroute-metric option to control its priority. The replacedefaultroute option no longer has any effect, and pppd logs an error if it is used. - EAP-TLS users: MPPE keys generated with 'max-tls-version 1.3' are now compatible with Windows clients but not with older versions of pppd. OpenSSL engine support has been disabled, and EAP-SRP support has been removed. See /usr/share/doc/ppp/README.gz for the full upstream release notes. -- Chris Boot Thu, 05 Nov 2026 17:00:33 +0000 ppp (2.5.2-1+1~exp1) experimental; urgency=medium Many old and unmaintained example scripts, as well as the passprompt pppd plugin, have been removed. If you were using passprompt you should investigate using passwordfd instead: see /usr/share/doc/ppp/README.pwfd for more information and an example program. -- Chris Boot Sun, 26 Jan 2025 16:31:17 +0000 ppp (2.4.8-1+1~exp1) experimental; urgency=medium The pppd-dns init script and systemd unit have been removed. These were intended to restore /etc/resolv.conf to how it was before pppd modified it, for example when booting a system after a crash while pppd was running while using the 'usepeerdns' option without resolvconf. This functionality has not worked in a stable release since Debian Squeeze, released in July 2014. If you use 'usepeerdns' I strongly recommend using it with resolvconf, or managing pppd with a tool such as NetworkManager instead. The usepeerdns functionality has *not* been removed, only the fallback mechanism during boot which restores resolv.conf. -- Chris Boot Mon, 03 Feb 2020 12:05:07 +0100