[cups.general] hostname resolution problem

[Michael Sweet]

On Aug 16, 2010, at 3:16 PM, alet at librelogiciel.com wrote:
> ...
> It seems it's like if CUPS' HostnameLookups directive is only applied to
> the IP address of incoming IPP requests (in the case of Samba it's
> localhost), but never applied to the job-originating-host-name attribute
> in the job's ticket.
> 
> Is this the expected behavior, and if so, what is the reason ?

Yes - you need to enable hostname resolution in Samba to get the resolved name from Samba jobs.

The reason is pretty simple: hostname resolution in CUPS is only provided for logging and access control of connections to cupsd.  Doing it with the string value from job-originating-host-name is problematic due to encoding and context issues that would prevent us from being able to do the lookups (UTF-8 names often need to be mapped, the default domain can be different, and link-local addresses need to know the original interface to have a hope of working, to name a few), not to mention the performance and complexity issues we'd run into - we already go out of our way to avoid blocking conditions.

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair