>> As far as I can tell, there have been no semantic changes... or even
>> code changes... ARAHHGGGHHH! AARRRHAGGGH!!! Sigh...
There's been at least one semantic change that has been bitten us.
We originally had these lines in our lpd.perms:
REJECT AUTHFROM=?* PRINTER=</var/spool/printer/queues.secure NOT
AUTHFROM=</var/spool/printer/hostkeys.allow
REJECT AUTHFROM=?* AUTHJOB NOT AUTHFROM=</var/spool/printer/hostkeys.allow
The intent of them was to only allow our print servers (with host
keys listed in hostkeys.allow) to forward jobs to other queues. Under
LPRng 3.6.1, AUTHFROM is set to the principal forwarding the job (in our
case, daemon/printserver.mit.edu, for example) but is empty for jobs
that have not been forwarded.
Under LPRng 3.6.13, this is no longer the case. AUTHFROM is set to
the authenticating principal for both forwarded and non-forwarded jobs.
I've managed to work around this by adding the FORWARD keyword to each
of the lines in question, but it seems like this change wasn't
intentional, so I thought I'd mention it.
We'll test the patches you provided and see if they fix the problems
we've been encountering.
Garry Zacheiss
Athena Server Operations
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
