I'm writing my own stripped-down lpr and I was wondering if there
is any documentation which details the "conversation" between lpr and
LPRng's LPD implementation of the kerberos authentication.
In particular, in the howto, I've found
\008printer C user_id authtype size\n - for print jobs (lpr)
I guess that's a start. I'm assuming that following the \n, an
octet of 0 bits is returned to the client on success... and then the
client sends back a kerberos5 ticket in some form, perhaps terminated with
a 0x00 byte.
Is this correct? What happens next? How does the kerberos ticket
info get "formatted"? (this is my first experience using the krb5_* api).
Now, according to RFC1179, lpr connections are only kept open for
the duration of a single "major" command. I can only assume that the AUTH
command is different, and that it is followed by another command.
/* Sam */
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------