On Thu, Dec 05, 2002 at 04:14:35PM +1300, Jason Haar wrote:
> Pretty hard to steal the cert then - but it can and has been done before...
The certificate is public information. It is the key that you are worried
about being stolen.
---
This sf.
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?
I'm thinking on the way how Apache handles it. I just need to enter the
password once, when I sta
Sam Varshavchik writes:
Tomas Ericsson writes:
For example when using Apache one get asked about the PEM-password when
you are starting the server...
That makes the difference between a server that can boot
unattended (e.g. when UPS restores power) and one that
needs the guy to get there.
P
On Wed, Dec 04, 2002 at 06:16:16PM -0500, Sam Varshavchik wrote:
> 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?
>
> Of course, you can alwa
Tomas Ericsson writes:
Hi,
I scary feeling comes up... can Courier-IMAP handle password locked
SSL-certs? Do I _need_ non-password locked SSL-cert to be able to use
them with Courier-IMAP?
For example when using Apache one get asked about the PEM-password when
you are starting the server...
