Bug 5819 - Add support for CUPS SSL encryption
Add support for CUPS SSL encryption
Status: RESOLVED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: Printing
3.0.32
x64 Linux
: P3 enhancement
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-08 14:51 UTC by Daniel Solano
Modified: 2009-04-20 03:45 UTC (History)
0 users

See Also:


Attachments
Patch to provide new 'cups encrypt' option. (6.59 KB, patch)
2008-10-08 14:51 UTC, Daniel Solano
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Solano 2008-10-08 14:51:00 UTC
Currently, Samba uses the httpConnect function to connect to a CUPS server.  This function simply calls httpConnectEncrypt with an encryption type of HTTP_ENCRYPT_IF_REQUESTED.  As a result, Samba only works with CUPS servers with no encryption or that us TLS encryption.

I have included a patch against 3.0.32 that creates a new configuration parameter called 'cups encrypt'.  This new parameter mirrors the existing 'cups server' option.

If it the new parameter is not set or set to 'Default', Samba will use CUPS's default method for encryption the way a null 'cups server' will use CUPS's default server.  Otherwise, a user may define an encryption type to override the default behaviour.

I have attempted to provide some documentation for the new feature by adding a new XML file.  However, I am not sure if any additional documentation is necessary.
Comment 1 Daniel Solano 2008-10-08 14:51:54 UTC
Created attachment 3672 [details]
Patch to provide new 'cups encrypt' option.
Comment 2 Jeremy Allison 2008-10-08 15:57:37 UTC
This looks good, but we need a configure test for it so we make sure it's available in whatever version of the cups API installed on a machine.
Jeremy.
Comment 3 Björn Jacke 2009-04-20 03:45:38 UTC
independent and slightly different cups encryption support was added with commits

4b184eaea1aca5b69a7e9509353e6c4d73cce2c1
5b33918947914f6d6805e6ac43436cac58388a59

As this is a new feature it will by policy only be upstream after the 3.4 release series. But you can patch up your build with cups encryption support if you like...