R
Randall Parker
1) What sorts of scenarios make the possibility of sniffing out a password a higher risk?
2) Do packets travel unencrypted over 802.11 wireless? Is it easy to sniff such
packets and catch a submit of a logon web page using http? Wireless strikes me as the
greatest risk.
3) Have you used http or https for Logon.aspx pages and why?
4) Anyone know if IIS on Windows Server 2003 has https built in? Easy or hard to
configure?
5) If one uses https does one have to do any different code in the CodeBehind for the
web page? Or is that all handled in the IIS configuration and Web.config?
6) How does one redirect from an https logon back to the http page the user logged in
on? Does the http part show up in the RETURNURL argument?
2) Do packets travel unencrypted over 802.11 wireless? Is it easy to sniff such
packets and catch a submit of a logon web page using http? Wireless strikes me as the
greatest risk.
3) Have you used http or https for Logon.aspx pages and why?
4) Anyone know if IIS on Windows Server 2003 has https built in? Easy or hard to
configure?
5) If one uses https does one have to do any different code in the CodeBehind for the
web page? Or is that all handled in the IIS configuration and Web.config?
6) How does one redirect from an https logon back to the http page the user logged in
on? Does the http part show up in the RETURNURL argument?