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

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

Message-ID: <200309241701.h8OH1Lt15303@panix5.panix.com>
Date: Wed, 24 Sep 2003 13:01:21 -0400 (EDT)
From: Seth Breidbart <sethb@...ix.com>
To: BugTraq@...urityfocus.com
Subject: Re: base64

> See the corresponding RFC. The number of characters in a base64-coded
> text must be a multiply of 4. So ='s are used if there aren't enough
> characters and are added at the end of the text.
>
> = is not a valid character inside Base64 and an encoder should stop
> with an error or stops decoding.

That depends on the purpose of the decoder.

If your anti-virus decoder stops there, but a virus writer knows that
the decoder used by some popular mail client keeps going, then your
program isn't going to detect his virus.

If you're looking for something that might be hidden, then you need to
decode in _every_ way that _any_ mail client (that you support) does,
lest you have false negatives.

Seth