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: Wed, 22 Jun 2005 07:05:09 -0400
From a purely non-technical viewpoint: it may be a good idea for the login page to be protected by SSL if for no other reason that having the browser show the "padlock" symbol. It's something that non-technical, non-web developer people can see and (somewhat) understand. Since they are typing their password on a page, that's what many associate with - "I'm not entering my password here, I don't see the padlock".

Amir Herzberg wrote:

There may be some argument even in this case (privacy, tendency of users to use same passwords, ...). But this was _not_ my intent. I may not have been clear, but I am interested in sensitive sites - financial, shopping, security (CA, DNS, SSO, Portals, etc.). As you can see in my `Hall of Shame` http://AmirHerzberg.com/shame.html, many of these don't use SSL to authenticate the login page, only to encrypt the password (when using a correct login page).

So, the real question I'm asking: should login pages to sensitive (e.g. financial) sites be protected by SSL?



--
Dave Ockwell-Jenner
Solar Nexus Solutions
http://www.solar-nexus.com/

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