Re: username and Password sent as clear text strings

["arvind doraiswamy" <arvind.doraiswamy () gmail com>]

Hey John,
I think this is a very common problem and after reading through
everything on this thread there's just 2 things that come to mind:

1) What you said -- Usage of IPSec end to end. Wouldn't that mean that
everyone who accesses this application(read internal users) also have
to use IPsec? You might want to look at whether the internal
switches/backbone is good enough to take that load or at least mention
the same to the client.

2) A much much simpler solution is to implement a salted has scheme on
the client side which means "Javascript". So as soon as you enter your
username and password and hit OK the details go to the has function in
Javascript -- get "encrypted" and go out. NOw when it "goes out" it
hits Webscarab -- but since its already "encrypted" Webscarab though
it intercepts stuff just sees the "encrypted/hashed" traffic. This
hence greatly reduces the risk; even if someone managed to somehow
convince a user to send traffic out through some untrusted proxy.

The risk is there..specially in shared environments like cyber cafes
where you could well be sending data through who knows where if you're
not careful but really its low risk IMHO. Shd be reported -- but low
risk.

Cheers
Arvind

------------------------------------------------------------------------
This list is sponsored by: Cenzic

Top 5 Common Mistakes 
in Securing Web Applications  
Find out now! Get Webinar Recording and PPT Slides

www.cenzic.com/landing/securityfocus/hackinar
------------------------------------------------------------------------