Sam Varshavchik writes:
Tomas Ericsson writes:That makes the difference between a server that can boot
For example when using Apache one get asked about the PEM-password when you are starting the server...
unattended (e.g. when UPS restores power) and one that
needs the guy to get there.
Password-locked certs ain't going to cut it. This is not an interactive environment. Do you really want to sit at the terminal, and keep reentering the password each time someone logs in via SSL?Perhaps asking the password to the log file is not user friendly...
Of course, you can always read the password from a file. But what would be the point of having the password in the first place, then?Would the password file be readable only by root?
A company could have a restrictive privacy policy, which does
not allow some maintenance staff to get the password, but still
allows them to read/write courier files. I'm not sure how much
sense this might have...
Ciao
Ale
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
