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: GET and POST Methods Accepted

Subject: Re: GET and POST Methods Accepted
Date: Fri, 14 Oct 2005 08:29:35 +0200 (CEST)
Hi there,

Using GET on a login page for example: The authentication parameters
shall be logged on the server. Nice way to harvent account info if you
can get your hands on the logs.

design != runtime.

I totally agree on what you wrote. But the question was : "is there any
reason to check at runtime whether the data was sent over GET or POST".

Everyone agrees it is a design issue and you must be careful not using the
GET method in some cases, basically whenenever sensitive data is sent, but
it is totally useless checking *at runtime* that these choices were indeed
respected by the sending party, for example to detect an intrusion, as is
it so easy to provide your application with the (bad) data in the correct 
(chosen at design) means. 

JG


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