[31735] in bugtraq

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

Re: base64

daemon@ATHENA.MIT.EDU (Lothar Kimmeringer)
Wed Sep 24 12:35:37 2003

From: "Lothar Kimmeringer" <bugtraq@kimmeringer.de>
To: "BugTraq@securityfocus.com" <BugTraq@securityfocus.com>
Date: Tue, 23 Sep 2003 20:10:36 +0200
In-Reply-To: <Pine.GSO.4.58.0309231211460.16663@concept.ocis.temple.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <E1A1rcU-0003rc-00@mrelayng.kundenserver.de>

On Tue, 23 Sep 2003 12:18:31 -0400 (EDT), Birl wrote:

>Excuse my ignorance.  I tried to pook around some B64 attachements in my
>email files for an answer.
>
>
>Are you stating that an =
>
>1) should not appear in B64 at all
>2) should not appear in the middle of a line, but only at the EOLN
>3) should only appear at the end of a B64 file

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.

>Answering that question could help me better determine how to write a
>procmail filter for this.

/.*=[^=]/
(untested)


Regards, Lothar

-- 
Lothar Kimmeringer                E-Mail: mailbody@kimmeringer.de
               PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
                 questions!



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