Subject: Re: lpd and filter programs
To: None <email@example.com>
From: Ian Dall <Ian.Dall@dsto.defence.gov.au>
Date: 07/27/1998 18:18:18
Lucio de Re <firstname.lastname@example.org> writes:
> According to Ian Dall:
>> OK, I take that point. More often I see it the other way around though.
>> The printer is connected to a stand alone print server or a host
>> I don't have administrative control over.
> I think a lot originally hinged on the assumption that either you would
> find a cooperative administrator, or you should not be tampering with a
> printer outside your administrative domain.
> What's changed is that administrators are no longer cooperative and/or
> sufficiently competent, but that does not mean that administrative
> domains should have a big hole punched into them.
> Do keep security in mind.
Ah, but running filters in the users context (via lpr) is *less* of a
security risk. It wouldn't let the user run anything they couldn't run
by hand anyway. Whereas running "advanced" filters which interprete
things like postscript has the potential to let users get at files