I normally require originating port 0-1023 connections in order to be able to trust the user name in the control file (as only sysadmins have root in the workstations).
I do though have a wild network of laptops where I do not want to trust the user name, but I need to be able to have the real requesting hostname passed to scripts. Today I only get the control file hostname passed to scripts, which users on this wild laptop network can fake when submitting the job. I know I can use SAMEHOST to verify the control file hostname and the real reuqesting host in lpd.perms, but the problem is that users on their laptops use their own hostnames which are then put into their control file, and hence will not match with real requesting host when LPRng performs the SAMEHOST test. These users need to be able to print, so I need a way to rewrite the hostname in the control file with the real requesting hostname when LPRng accepts the job for queueing. Is there a way to do this that I have missed? ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
