bugtraq - Re[2]: 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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Fri, 26 Sep 2003 22:02:56 +0400
From: 3APA3A <3APA3A@...URITY.NNOV.RU>
To: Earl Hood <earl@...lhood.com>
Cc: bugtraq@...urityfocus.com, Bennett Todd <bet@...ul.net>,
	MightyE <trash@...htye.org>, Lawrence MacIntyre <lpz@...l.gov>
Subject: Re[2]: base64

Dear Earl Hood,

Signature  is applied to decoded message. If encoding is broken there is
no  need  to  try to keep signature. Reassembling message is really best
solution.  But  there  are  another ways to bypass message reassembling.
Some of them can be found in

http://www.security.nnov.ru/advisories/content.asp

--Friday, September 26, 2003, 3:46:36 AM, you wrote to bugtraq@...urityfocus.com:

>> limits. Recode base64. Recode uuencoded chunks. Regularize
>> non-standard MIME.

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

EH> --ewh

-- 
~/ZARAZA
Ибо факты есть факты, и изложены они лишь для того, чтобы их поняли и в них поверили. (Твен)