[cups-devel] 2.x: Server{Certificate, Key} in cups-files.conf not considered?

[Michael Sweet]

2.0 consolidated these into a single ServerKeychain directive that points to the directory containing the .crt and .key files.  The filenames need to match the common name, e.g., for "print.example.com" cupsd will look for "print.example.com.crt" and "print.example.com.key".  Similarly, when cupsd generates a self-signed certificate the files are placed in that directory (by default /etc/cups/ssl).


> On Dec 2, 2014, at 3:08 PM, Peter Mattern <matternp at arcor.de> wrote:
> 
> Hello.
> 
> As of 2.x ServerCertificate and ServerKey in cups-files.conf don't seem to be taken into account any more at all.
> 
> CUPS' web interface always delivers those self-signed certificates that are generated when the first TLS session is started, stating certificates / keys that don't exist doesn't cause any error message.
> 
> Seen on Arch Linux x86_64 with with 2.0.1 from the distro's package as well as compiled from the sources (cups.org) by simply running ./configure, make and make install.
> 
> Is this a bug or am I missing something?
> 
> Regards,
> 
> Peter Mattern
> _______________________________________________
> cups-devel mailing list
> cups-devel at cups.org
> https://www.cups.org/mailman/listinfo/cups-devel

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair