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

[Peter Mattern]

All right. The way CUPS creates and chooses certificates and keys as of 
2.0 is clear now. Thanks.
But wouldn't it be good to replace Server{Certificate,Key} with 
ServerKeychain in cups-files.conf's template as provided by the sources?

One additional note about something I stumbled upon looking into that 
TLS thing:
If a host's FQDN is stated by ServerName in cupsd.conf, CUPS won't 
accept connections using that FQDN any more but throw "Bad Request" 
instead. I couldn't see any real downside as all FQDNs I needed were 
accepted without stating them in ServerName anyway.
But I thought I'd mention it quickly as it seemed a bit odd to me.

Regards