| commit | 7f57b627800baba4bc030d9c3748ead9ac53397d | |
| author | Luca Olivetti <luca@wetron.es> | |
| Tue, 4 May 2010 22:07:57 +0000 (4 15:07 -0700) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Wed, 5 May 2010 07:52:44 +0000 (5 09:52 +0200) | ||
| tree | f22f73680972694bbc6162121673163f23f5803f | treesnapshot (tar.gz zip) |
| parent | 0fc2424ee2f5082a74dad45a03226b457b6b00a8 | commitdiff |
Fix bug #7263 - Unable to print using Samba 3.5.1 and cups-1.1.23-40.46 on SLES10.
Fix cups encryption setting
I had the same problem and it's due to the fact that samba doesn't respect the
"cups encryption" setting since lp_cups_encrypt changes the value: if you set
"cups encryption=no", the first call will change it to HTTP_ENCRYPT_NEVER,
since that is 1 (i.e. true), the next call will change it to
HTTP_ENCRYPT_ALWAYS and after that it'll remain set as HTTP_ENCRYPT_ALWAYS.
This patch fixes this problem.
Don't mix up the HTTP_ENCRYPT_XXX constants up with the
enumeration constants (True, False, Auto) used in the
loadparm code.
(cherry picked from commit a9e008ee36c8fd9ca79b3bdfdc78111939c3e539)
Fix cups encryption setting
I had the same problem and it's due to the fact that samba doesn't respect the
"cups encryption" setting since lp_cups_encrypt changes the value: if you set
"cups encryption=no", the first call will change it to HTTP_ENCRYPT_NEVER,
since that is 1 (i.e. true), the next call will change it to
HTTP_ENCRYPT_ALWAYS and after that it'll remain set as HTTP_ENCRYPT_ALWAYS.
This patch fixes this problem.
Don't mix up the HTTP_ENCRYPT_XXX constants up with the
enumeration constants (True, False, Auto) used in the
loadparm code.
(cherry picked from commit a9e008ee36c8fd9ca79b3bdfdc78111939c3e539)
| source3/param/loadparm.c | diffblobblamehistory |