Re: [ietf-dkim] A more fundamental SSP axiom

Damon <deepvoice@gmail.com> Fri, 04 August 2006 23:40 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G99H1-0004WS-FB for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 19:40:11 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G99H0-0008Rn-2n for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 19:40:11 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74NZNbU007684; Fri, 4 Aug 2006 16:35:23 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74NZHAA007646 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 16:35:18 -0700
Received: by nf-out-0910.google.com with SMTP id g2so598395nfe for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 16:34:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=axkP/9WhUL8bU1q657cXIRki9MJGMngxTdmxor4ltbM5U5ELzv3Y4VHZ9FfP4JPfylXT7Qk8pyR5XRRLqFAXs+SJ0KZNn5V96R6p/YbrWjilBcDGxQWEGYPwkTYPbWcIodztZxfBhStig2tl+U60Mg7/8r9Z0bshMWHRhOQxiJw=
Received: by 10.78.170.17 with SMTP id s17mr1615779hue; Fri, 04 Aug 2006 16:34:48 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 16:34:35 -0700 (PDT)
Message-ID: <62146370608041634t38baf99eu351e0c7373d811d4@mail.gmail.com>
Date: Fri, 04 Aug 2006 19:34:35 -0400
From: Damon <deepvoice@gmail.com>
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <20060804231526.71834.qmail@snake.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060804173538.54245.qmail@simone.iecc.com> <44D3C0BB.9000405@mtcc.com> <20060804174955.N15734@simone.iecc.com> <44D3C8DB.4070101@mtcc.com> <20060804184321.L23892@simone.iecc.com> <20060804231526.71834.qmail@snake.corp.yahoo.com>
X-Songbird: Clean, Clean
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

On 8/4/06, Mark Delany <MarkD+dkim@yahoo-inc.com> wrote:
> On Fri, Aug 04, 2006 at 06:44:34PM -0400, John L allegedly wrote:
> > >I cannot see how SSP can do anything but make false positives more
> > >likely. The real question is whether the gain in eliminating harmful
> > >mail is worth the occassional false positive.
>
> I guess I'm a little confused about the false policy concern.
>
> If a signer wants to take that risk, isn't that for them to decide?

Yes but.. I don't think that everyone is going to be aware of the risk
or ignore it thinking it can't happen to them. I still haven't stopped
smoking even though the Surgeon General puts all that scary warning
stuff on my smokes. It can't happen to me...

>
> Also, if the usual strategy of a verifier is to bounce (or be
> encouraged to bounce) the offending email, a "I sign all" sender will
> almost always know about delivery failures of originally signed
> traffic and be able to act accordingly.


I like the bounce idea too, but then we get into the whole attack
thing. Some poor schmuck with a little sparc2 trying to handle all the
verifier bounce traffic from ohh. let's say... Yahoo ;)


Damon
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html