[31870] in bugtraq
Re: base64
daemon@ATHENA.MIT.EDU (=?koi8-r?Q?=22?=Ilya Teterin=?koi8)
Sat Sep 27 12:22:54 2003
From: =?koi8-r?Q?=22?=Ilya Teterin=?koi8-r?Q?=22=20?= <alienhard@mail.ru>
To: bugtraq@securityfocus.com
Mime-Version: 1.0
Date: Sat, 27 Sep 2003 12:42:16 +0400
Reply-To: =?koi8-r?Q?=22?=Ilya Teterin=?koi8-r?Q?=22=20?= <alienhard@mail.ru>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Message-Id: <E1A3Aee-0007tu-00.alienhard-mail-ru@f21.mail.ru>
Bennett Todd:
> Outlaw people from receiving email on Windows, and we can
> do away with all this sludge
Heh. The base64 ambiguity isn't Windows MUAs issue ;-) Just tested MUAs for *nix:
1) kmail.
data truncated, warning
excellent!
2) pine. depending on input
* data truncated, warning reported
* decoding error reported
not too bad...
3) mutt depending on input
* decoding error reported
* input after padding is decoded
evil badness approaching!
4) emacs. similar to (3).
Also, tested perl MIME::Base64 - data truncated, no warnings (which is good for MUA but bad for filters), uudecode - input after padding is decoded, cryptopp (opensource crypto and enconding library) - paddings are ignored.
p.s. Windoze mustdie, *nix 4ever? ;-)
