OK OK, I took flack for using a 'not really meant for public
consumption but I don't know what to use instead' Kerberos 5
function.
What happens when you use a 'unix socket' or 'named pipe' for a
client to server connection?
Ummm... that IS an interesting question. I will simply refer you
to the error message from the Kerberos support library:
2002-03-02-13:47:16.843 h110 [83535] RCVSEC t1: server_krb5_auth:
retval 1, error:
'on server server_krb5_auth failed -
krb5_rd_priv failed: Incorrect net address'
I suppose that this sort of thing needs to be special cased into
the lookup code... you will need to check the af_family field or
whatever in the struct sockaddr structure. I suppose that I will
have to add 'special casing' into the LPRng code to abort connections
using named pipes, etc. Perhaps when the solution is found it
could be added to the 'developers notes' that are supposed to be
in the distribution?
Glad it's not my problem this time...
Patrick ("Don't point a finger... there are 3 pointing right
back at yourself") Powell
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
