Re: Retiring lpr and lpd
Tomek CEDRO <[email protected]> Sat, 21 Feb 2026 03:42:41 +0100
| Newsgroups | gmane.os.freebsd.architechture |
|---|---|
| Message-ID | <CAFYkXjmcceo21qdfbSsSkwKGjzUxMVRv+SBEX9QL9jQik0nnxQ@mail.gmail.com> |
On Fri, Feb 20, 2026 at 7:41 PM Dag-Erling Smørgrav wrote: > Hi, > The lp* family of printing utilities have received practically no > maintenance in two decades and are showing their age. What's worse, > most of them are setugid, and lpd(8) is a network-facing daemon with > IP-based authentication and little to no input validation. Furthermore, > better-maintained alternatives are available from ports: print/lprng is > a drop-in replacement derived from the same code base, while print/cups > provides far more functionality and a compatible command-line interface. > > Unless someone steps up and does a credible job of modernizing these > utilities, we have no other choice than to retire lp(1), lpc(8), lpd(8), > lpq(1), lpr(1), lprm(1), lptest(1), and pac(8) from base. > > In the next few days, I will commit patches to add deprecation notices > to all relevant manual pages (D55381) and switch the LPR build option > from default-on to default-off (D55380). The code will remain in the > tree, and remain buildable, but unless the situation changes, it will be > removed from the tree no later than shortly before stable/16 is branched > in the fall of 2027. Would it be possible to move them to ports? Anyone using them would still use but from ports :-) Or some working alternatives (plp seems dead) maybe in ports already? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info