On Wed, 26 Jan 2011 21:43:28 PST, Michal Zalewski said: > The real problem is that when mhtml: is used to fetch the container > over an underlying protocol, it does not honor Content-Type and > related headers (or even "nosniff").
Geez. It's 2011, and people are *still* doing that same basic error? /me tries to remember the first "ignore the Content-Type header and handle it based on guessing based on filename/extension" bug. CA-2001-36 seems to qualify, but I think there were ones before that. Anybody able to remember that far back?
pgpnBGsesZFSh.pgp
Description: PGP signature
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
