Re: [Asrg] Introduction and another idea

Yakov Shafranovich <research@solidmatrix.com> Thu, 19 June 2003 19:28 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13806 for <asrg-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:28:41 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5JJSDc05117 for asrg-archive@odin.ietf.org; Thu, 19 Jun 2003 15:28:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T54v-0001KC-Bj for asrg-web-archive@optimus.ietf.org; Thu, 19 Jun 2003 15:28:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13791; Thu, 19 Jun 2003 15:28:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T52c-0002G6-00; Thu, 19 Jun 2003 15:25:51 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19T52c-0002G1-00; Thu, 19 Jun 2003 15:25:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T54j-0001G0-Me; Thu, 19 Jun 2003 15:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T53s-0001DL-1k for asrg@optimus.ietf.org; Thu, 19 Jun 2003 15:27:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13626 for <asrg@ietf.org>; Thu, 19 Jun 2003 15:27:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T51Z-0002DT-00 for asrg@ietf.org; Thu, 19 Jun 2003 15:24:45 -0400
Received: from 000-233-701.area5.spcsdns.net ([68.27.152.22] helo=68.27.152.22) by ietf-mx with smtp (Exim 4.12) id 19T51W-0002DD-00 for asrg@ietf.org; Thu, 19 Jun 2003 15:24:44 -0400
Message-Id: <5.2.0.9.2.20030619152636.00bd4580@solidmatrix.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Vernon Schryver <vjs@calcite.rhyolite.com>, asrg@ietf.org
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Re: [Asrg] Introduction and another idea
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Thu, 19 Jun 2003 15:26:37 -0400

At 12:41 PM 6/19/2003 -0600, Vernon Schryver wrote:
>[..]
>
> > Also, blocking base64 encoding would block email schemes where digital
> > signatures are used.
>
>That is entirely mistaken.  You might want to ensure that sender and
>recipient agree on whether to sign the encoded or plaintext versions
>of the message, but that's all.

In the scheme proposed by Art Pollard, a copy of the public key would be 
included with the signed message. Common format for public key certificates 
use base 64 encoded, outright ban of all base-64 email would be a problem 
for this. The point I was trying to make is that outright ban on ALL 
base-64 email is not a simple as it sounds. There are legit applications 
that use it and such banning approach would have to take them into account.

Yakov  


_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg