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

[Michael Sweet]

Peter,

> On Dec 4, 2014, at 3:16 PM, Peter Mattern <matternp at arcor.de> wrote:
> 
> 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?

Yes, that was an oversight and will be corrected in the next update.

> 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.

Do you mean that CUPS is rejecting a connection if you connect using a hostname different from ServerName, or ???

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair