>>>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.
>>>
>>>
>
>
>
>>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.
>>
>>
>
>As far as I can tell, this has, in fact, been resolved. Cups no longer requires
>HTTPS to change administrative settings on my machine, up-to-date as of
>2006-06-05. Note that this was previously not the case (about 3 weeks? ago,
>when this bug was originally filed).
>
>-Forest
>
>
>
Do you mean in Ubuntu/Dapper or the original source on www.cups.org?
Forest Bond wrote:
>>>Can you be more specific about "insisting"? If I open localhost: 631/admin, I can use everything without going over SSL.
>>>http://
>>>So, it doesn't force use of HTTS.
>>>
>>>
>
>
>
>>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.
>>
>>
>
>As far as I can tell, this has, in fact, been resolved. Cups no longer requires
>HTTPS to change administrative settings on my machine, up-to-date as of
>2006-06-05. Note that this was previously not the case (about 3 weeks? ago,
>when this bug was originally filed).
>
>-Forest
>
>
>
Do you mean in Ubuntu/Dapper or the original source on www.cups.org?