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 22:30:24 +0200 (MEST)
On Wed, 22 Jun 2005, Dave Ockwell-Jenner wrote:

!!  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".

not bad in first glance
But then the secure login page uses an insecure form action=
(by design or by accident or by phishing, doesn't matter)
well, most browsers will show an alert now, but are all non-technical no-web
developers aware what really happens?
In such a case (assuming that the user is not awrae what happens, which
is not uncommon) the padlock is a fake, exactly the oposite of what it
should be.

Again, I'd vote to teach the browser developers to undoubtly inform the
user what happens, in all cases. I've the feeling that these people are more
seruity-aware than most website developers ;-)

-- Achim

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