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

| Subject: | Re: Ajax Security discussion for the OWASP Guide |
|---|---|
| Date: | Sat, 24 Sep 2005 18:04:01 +0100 (BST) |
On Fri, 23 Sep 2005, John Manko wrote:
From: John Manko <jmanko@johnmanko.com> Subject: Re: Ajax Security discussion for the OWASP Guide Now, as a user, it would be nice to know if a page is communicating to a remote server. Perhaps browsers should consider allowing more detailed javascript enable/disable features, apply different rules to different sites, and notifications to user if certain restrictions are violated.
How do I know as an end-user that web apps I connect to are not sending information back to the server? How can I block or disable such interactions now? Kind Regards - Keith Roberts
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Ajax Security discussion for the OWASP Guide, John Manko |
|---|---|
| Next by Date: | PacSec05, Dragos Ruiu |
| Previous by Thread: | Re: Ajax Security discussion for the OWASP Guide, John Manko |
| Next by Thread: | PacSec05, Dragos Ruiu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |