Re: MIME boundary strings

Marc Mutz <mutz@kde.org> Thu, 22 August 2002 12:46 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7MCkcv17862 for ietf-822-bks; Thu, 22 Aug 2002 05:46:38 -0700 (PDT)
Received: from mail.epost.de (web.epost.de [193.28.100.164] (may be forged)) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7MCka217858 for <ietf-822@imc.org>; Thu, 22 Aug 2002 05:46:37 -0700 (PDT)
Received: from dirichlet.mathematik.uni-bielefeld.de (129.70.125.234) by mail.epost.de (5.5.056) (authenticated as Marc.Mutz@epost.de) id 3D59336300098C47; Thu, 22 Aug 2002 14:46:16 +0200
From: Marc Mutz <mutz@kde.org>
Organization: KDE
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, Jacob Palme <jpalme@dsv.su.se>
Subject: Re: MIME boundary strings
Date: Thu, 22 Aug 2002 14:46:10 +0200
User-Agent: KMail/1.4.6
Cc: ietf-822@imc.org
References: <p0510033db98a5c7c98f8@[192.168.100.100]> <p0510034cb98a750b5df8@[192.168.100.100]> <AhNFVsj9hZKsigvgZmJFog.md5@melkebalanse.gulbrandsen.priv.no>
In-Reply-To: <AhNFVsj9hZKsigvgZmJFog.md5@melkebalanse.gulbrandsen.priv.no>
X-PGP-Key: 0xBDBFE838
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Description: clearsigned data
Content-Disposition: inline
Message-Id: <200208221446.11780@sendmail.mutz.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id g7MCkb217859
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 22 August 2002 13:20, Arnt Gulbrandsen wrote:
> That's one possible strategy. There are three that I know of:
>
> a) if using quoted-printable, quote something.
> b) if using format=flowed, rewrap differently
> c) if nothing else helps, use base64 for that body-part
>
> Basically, the boundary strings should be treated like "From " or
> ".". A good MUA avoids those strings at the beginnings of lines. IMO,
> avoiding n strings isn't harder than avoiding 2.
<snip>

n strings? Just include '-' in the "From ", "." list.

But base64 and qp encoded body parts are no problem, since you just need 
to include "=_" in the boundary string, which cannot be part of a qp or 
b64 encoded stream (from rfc2046 ;-)

For 7bit or 8bit, you need to actually do something, though, if you want 
to make it perfect. But IMO,
  "=_" + base64encode( time(0) rand() rand() ) 
(ie. a time_t followed by a 64bit random number) is reasonable enough.

Marc

- -- 
Mutig warf sich die kleine Überwachungskamera zwischen Täter und Opfer!
                                        --Rena Tangens / FoeBuD e.V.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ZN0T3oWD+L2/6DgRAlKQAJ9e07Dr9zqSnZ9KSKcaKrORXYdXLgCgjL5d
bLe5JsBa+PKou2UQ98uIIjE=
=v/r7
-----END PGP SIGNATURE-----