Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: Should login pages be protected by SSL?

Subject: Re: Should login pages be protected by SSL?
Date: Mon, 20 Jun 2005 20:42:34 -0400
Amir Herzberg wrote:

Here is a simple question: should web login forms be always protected by SSL?

IMO, If you have a logon page on a site, there is almost by definition "something" of value that needs protection. The value of that asset determines the expense of protecting it. If the value is over that price of a server side cert, then its a no brainier. Yes Logins should be protected by TLS. SSL 2.0 is weak, and was replaced by SSL 3.0. SSL 3.0 was replaced by TLS in 1999. You should NOT be using SSL. Unfortunately, Microsoft ships all of their OS/Browsers with SSL 3.0 turned ON and TLS turned OFF. That is a bug that they need to fix. So if your customer base uses M$ & I.E. and is too ummm.. backward to switch their security settings, you still must enable SSL 3.0 on your server to allow those users to access your server. But you should disable SSL 1, SSL 2 on your server to disallow folks try to negotiate down (Oakley) to the lowest common denominator SSL.

Andy Bentley CISSP


<Prev in Thread] Current Thread [Next in Thread>