Re^2: Encrypting User/Pass sent by WWW::Mechanize

in reply to Re: Encrypting User/Pass sent by WWW::Mechanize
in thread Encrypting User/Pass sent by WWW::Mechanize

Not quite true. If the website is using Digest authentication, then your password is never transmitted in the clear. However most websites won't accept that, so you have to send your password in the clear.

If this distresses people, it is no worse than typing name/password into a normal web form. (Perhaps this distresses you even more...)

Comment on Re^2: Encrypting User/Pass sent by WWW::Mechanize

Replies are listed 'Best First'.
Re^3: Encrypting User/Pass sent by WWW::Mechanize by CountZero (Bishop) on Sep 19, 2005 at 16:43 UTC
Well, I said "such as `https`" and I count Digest authentication as some form of secure connection (at least as far as username/password is concerned and that was the scope of the question). I should have made that more clear perhaps. CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply] [d/l]

In Section Seekers of Perl Wisdom