Re: [users@httpd] How to enable 443 on apache2 using provided key files

It turns out the approach I described did in fact work. The password was requested from the administrator and the site behaved well. The only deviation I had to make was that the SSLCACertificateFile parameter interpreted a space in the filename as delimiting a second invalid parameter. The

Re: [users@httpd] How to enable 443 on apache2 using provided key files

On 2/2/2017 at 1:27 PM, "Erik Dobák" wrote: > >well i am still unsure abut the full encryption. i don't like >that. if >there is a problem the overheads grow to analyze the situation. >what about >just signing the messages? i mean if you have messages for all why >do

Re: [users@httpd] How to enable 443 on apache2 using provided key files

well i am still unsure abut the full encryption. i don't like that. if there is a problem the overheads grow to analyze the situation. what about just signing the messages? i mean if you have messages for all why do you want to hide them? E On 2 February 2017 at 17:54,

[users@httpd] How to enable 443 on apache2 using provided key files

Hello, There is a freshly installed (from Ubuntu 16.04 package) apache server running in a large institution that needs to have port 443 traffic enabled. I am helping a friend of mine configure this server and, at the same time, writing a document for reproducing the installation procedure