bugtraq - Re: base64

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <200309252346.h8PNkbU23630@gator.earlhood.com>
Date: Thu, 25 Sep 2003 18:46:36 -0500
From: Earl Hood <earl@...lhood.com>
To: bugtraq@...urityfocus.com
Cc: MightyE <trash@...htye.org>, Lawrence MacIntyre <lpz@...l.gov>
Subject: Re: base64


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