> Hello William,
>
[snip]
>>This is a problem.
> Can you explain that in more detail ?  I see, that this is "not nice"
> but I`m interested why this is a real
> problem when running stunnel.
>
> regards
> Roland

The client certificate not having a passphrase is what makes me nervous. 
As an example:

"Well, I've got this new tunnel set up that I have to have this
certificate to use, so having a VNC password of "123" isn't an issue,
right.  Or better yet, I'll just disable the password.  It's set to only
accept connections from localhost, right?"  Then boom, you leave your
laptop alone and it gets stolen.  Or worse yet, someone you know decides
that it will be fun to see what happens when he posts your key to the
Internet.

Having a (good, long, hard to guess) passphrase makes these things less of
an issue (even though having a good VNC password is still important). 
Chances are with a good passphrase you will either a) get a chance to
change the keys before anyone can use that stolen laptop or b) prevent the
key from being used even if you don't realize it has been compromised.

--
William Hooper
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to