[31831] in bugtraq

home help back first fref pref prev next nref lref last post

Re: base64

daemon@ATHENA.MIT.EDU (Earl Hood)
Fri Sep 26 13:57:33 2003

Message-Id: <200309252346.h8PNkbU23630@gator.earlhood.com>
To: bugtraq@securityfocus.com
Cc: Bennett Todd <bet@rahul.net>
Cc: MightyE <trash@mightye.org>, Lawrence MacIntyre <lpz@ornl.gov>
From: Earl Hood <earl@earlhood.com>
Reply-To: Earl Hood <earl@earlhood.com>
In-reply-to: <20030925153009.GA5716@rahul.net> 
Date: Thu, 25 Sep 2003 18:46:36 -0500

On September 25, 2003 at 11:30, Bennett Todd wrote:

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

You cannot do this for signed messages, therefore, you still
need to either decode in all possible ways or drop the message
(or the offending entity).

--ewh

home help back first fref pref prev next nref lref last post