Posted by: Anonymous Coward
on September 29, 2005 01:53 AM
I don't see how using passwords over SSL subjects you to MITM attacks. Maybe that was not the intent of your writing, but that's how I read it.
If you only authenticate the server with certificates, then the client will know it is talking to the right server. Any SSL client worth its salt will check that the host name embedded in the server cert matches the actual host.
Now the question becomes how does the server authenticate the client. Passwords is one way. Assuming no hackers have ready access to a legitimate users passwords this is secure, and does NOT subject you to MITM attacks. Another way is to use client certificates, potentially in addition to passwords. This makes it slightly more inconvenient on the users part. The VPN admins need to issue each user a certificate, and users need to tell their VPN client to use that cert whenever connecting. If you carry your cert on a keyfob/smart card, it is pretty easy. Another way would be to copy the certificate around (less secure).
Learn about Linux
Download Linux
Get Linux help
FUD on MITM?
Posted by: Anonymous Coward on September 29, 2005 01:53 AMIf you only authenticate the server with certificates, then the client will know it is talking to the right server. Any SSL client worth its salt will check that the host name embedded in the server cert matches the actual host.
Now the question becomes how does the server authenticate the client. Passwords is one way. Assuming no hackers have ready access to a legitimate users passwords this is secure, and does NOT subject you to MITM attacks. Another way is to use client certificates, potentially in addition to passwords. This makes it slightly more inconvenient on the users part. The VPN admins need to issue each user a certificate, and users need to tell their VPN client to use that cert whenever connecting. If you carry your cert on a keyfob/smart card, it is pretty easy. Another way would be to copy the certificate around (less secure).
#