BugTraq
base64 Sep 22 2003 12:49PM
"Ilya Teterin" (alienhard mail ru) (5 replies)
Re: base64 Sep 26 2003 08:38PM
Earl Hood (earl earlhood com)
Re: base64 Sep 23 2003 04:50PM
Alexander Ogol (sanyok_nospam prophysoft org ua) (1 replies)
Re: base64 Sep 24 2003 07:09AM
Christian Vogel (chris obelix hedonism cx) (2 replies)
Re: base64 Sep 24 2003 07:01PM
David Wilson (David Wilson isode com)
Re: base64 Sep 24 2003 06:30PM
der Mouse (mouse Rodents Montreal QC CA)
Re: base64 Sep 23 2003 04:18PM
Birl (sbirl temple edu) (1 replies)
Re: base64 Sep 23 2003 06:10PM
Lothar Kimmeringer (bugtraq kimmeringer de) (2 replies)
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 (at) kimmeringer (dot) de [email concealed]
PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

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

[ reply ]
Re: base64 Sep 24 2003 06:24PM
David Wilson (David Wilson isode com) (2 replies)
Re: base64 Sep 25 2003 07:10AM
Christian Vogel (chris obelix hedonism cx)
Re: base64 Sep 25 2003 12:27AM
Earl Hood (earl earlhood com)
Re: base64 Sep 24 2003 05:01PM
Seth Breidbart (sethb panix com)
Re: base64 Sep 23 2003 06:44AM
Erwan David (Erwan David trusted-logic fr)
Re: base64 Sep 22 2003 04:59PM
Bennett Todd (bet rahul net)


 

Privacy Statement
Copyright 2010, SecurityFocus