Hi all, I've previously been including the kerberos_id value in both the server and client printcap information, e.g.
client: auth=kerberos5:[EMAIL PROTECTED] server: [EMAIL PROTECTED]:kerberos_keytab=/etc/lpd.keytab I don't like having to include the host-specific information here, for local reasons which it's probably not worth going into. So, I've been experimenting with taking the kerberos_id value out so I just have: client: auth=kerberos5 server: kerberos_keytab=/etc/lpd.keytab ... and this seems to work OK - the server gets the service principal name from the keytab file and everything works nicely kerberised. So, I suppose my question is, is there any reason why this is a bad idea? Cheers Toby ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
