| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <200307230526.h6N5QOqj005026@turing-police.cc.vt.edu> From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu) Subject: logically stopping xss On Tue, 22 Jul 2003 23:55:24 EDT, KF <dotslash@...soft.com> said: > SecFilter "<(.|\n)+>" > the JavaScript language can be used on the client side, which should > replace the prohibited characters with special tags, e.g. < > > " etc. What's wrong with this picture? :) The basic problem here (going all theoretical) is that there's a very messy intermixing of executable code (javascript) and data (html) going on, forming what's often known as a Von Neuman architecture. If we had a Harvard architecture (where code is code and data is data and never the twain shall meet), we'd have a lot less trouble.... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 226 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030723/c31718c4/attachment.bin
Powered by blists - more mailing lists