>Can you be more specific about "insisting"? If I open
>http://localhost:631/admin, I can use everything without going over SSL.
>So, it doesn't force use of HTTS.
>
>But, if I use https://localhost:631, CUPS doesn't respond. Logs show:
>
>Unable to create server key file "/etc/cups/ssl/server.key" - No such
>file or directory
>
>OK. Solution is to create /etc/cups/ssl directory with cupsys:lp as
>owner:group.
>
>** Changed in: cupsys (Ubuntu)
> Status: Unconfirmed => Confirmed
>
>
>
Even when one starts at localhost:631 and attempts to add a printer
the final step insists that one access :443 port. After adding /etc/cups/ssl
one still doesn't get a lot of success as key generation seems to take
forever. To the point that I just used command line openssl command
to generate a key. I do recall that in a previous test I waited a few
hours and it eventually appeared, however, this is clearly unsatisfactory
behaviour.
Ante Karamatić wrote:
>Can you be more specific about "insisting"? If I open localhost: 631/admin, I can use everything without going over SSL. /localhost: 631, CUPS doesn't respond. Logs show: ssl/server. key" - No such
>http://
>So, it doesn't force use of HTTS.
>
>But, if I use https:/
>
>Unable to create server key file "/etc/cups/
>file or directory
>
>OK. Solution is to create /etc/cups/ssl directory with cupsys:lp as
>owner:group.
>
>** Changed in: cupsys (Ubuntu)
> Status: Unconfirmed => Confirmed
>
>
>
Even when one starts at localhost:631 and attempts to add a printer
the final step insists that one access :443 port. After adding /etc/cups/ssl
one still doesn't get a lot of success as key generation seems to take
forever. To the point that I just used command line openssl command
to generate a key. I do recall that in a previous test I waited a few
hours and it eventually appeared, however, this is clearly unsatisfactory
behaviour.