| 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: <20030925153009.GA5716@rahul.net>
Date: Thu, 25 Sep 2003 11:30:09 -0400
From: Bennett Todd <bet@...ul.net>
To: MightyE <trash@...htye.org>
Cc: Lawrence MacIntyre <lpz@...l.gov>, bugtraq@...urityfocus.com
Subject: Re: base64
2003-09-25T09:06:58 MightyE:
> There are two methods which you can use in the writing of your
> email virus scanner; you can either decode it every known way that
> any client does so, [...] Alternatively you can accept it only if
> it is properly encoded, [...]
There's a third method, which I think is rather better than either
of those.
You can re-code everything into a canonical form. Some email client
drop some punctuation characters in filenames? Delete all such
characters from filenames. Different tools handle various i18n
encoded filenames differently? Map to US-ASCII. Enforce length
limits. Recode base64. Recode uuencoded chunks. Regularize
non-standard MIME.
Do all this canonicalization before the message hits your
attachment type policy enforcement and malware scanner, so they only
have to deal with the common forms that everybody handles the same.
-Bennett
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists