Re: Retiring lpr and lpd

On Fri, Feb 20, 2026 at 09:51:32PM +0100, Dag-Erling Smørgrav wrote:

> Slawa Olhovchenkov <[email protected]> writes:
> > Dag-Erling Smørgrav <[email protected]> writes:
> > > 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.
> > I am regulary using this.
> > What is problem?
> > Don't fix what isn't broken
> 
> The lp* family of printing utilities have received practically no
> maintenance in two decades and are showing their age.  What's worse,

I am stil use it for print to network printer w/o any additional work
from my FreeBSD workstation.

> most of them are setugid, and lpd(8) is a network-facing daemon with
> IP-based authentication and little to no input validation.
> Furthermore,

Just change default for lpd to start w/ -s key.

> 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.

lpd enought to start printing to any network based printers in office.