IETF Logo Mail Archive

Re: [ietf-smtp] Public Key Look Up

Dave Crocker <dhc@dcrocker.net> Wed, 12 May 2021 18:46 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFB3D3A0C38 for <ietf-smtp@ietfa.amsl.com>; Wed, 12 May 2021 11:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CzKqMMfIsa7p for <ietf-smtp@ietfa.amsl.com>; Wed, 12 May 2021 11:46:41 -0700 (PDT)
Received: from olivedrab.birch.relay.mailchannels.net (olivedrab.birch.relay.mailchannels.net [23.83.209.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A92573A0C36 for <ietf-smtp@ietf.org>; Wed, 12 May 2021 11:46:40 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 57AE636339C; Wed, 12 May 2021 18:46:38 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (100-96-17-237.trex.outbound.svc.cluster.local [100.96.17.237]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 19BD4363382; Wed, 12 May 2021 18:46:36 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout2.hostinger.io ([UNAVAILABLE]. [145.14.159.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.96.17.237 (trex/6.2.1); Wed, 12 May 2021 18:46:38 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Troubled-Illustrious: 6108a4736889a258_1620845198063_441503794
X-MC-Loop-Signature: 1620845198063:1393730312
X-MC-Ingress-Time: 1620845198063
Received: from [192.168.0.111] (c-24-130-56-204.hsd1.ca.comcast.net [24.130.56.204]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout2.hostinger.io (smtp.hostinger.com) with ESMTPSA id 8A4613135075; Wed, 12 May 2021 18:46:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1620845195; bh=xnBKGvwJLUoRxuNKBuXa5yEkeADFkqi7cOoWO+Z+a7I=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=SvJQjPU7k/+dHYHx2s64nCweiUFKAXnWgiNebC2i7FAeSQRq2OnJwtnew05Q3/Ozi A01GRJwQFgnKtj1DZketUdtDQaZ23canTPqmIP0QQjRNrKUnODPxuSb0PDhKX+HYjM nRvF99LlNPnIIzp//A7rETG4ZX1kYEsguxgM5O/CiBwVNv4ZnQ3owpXx1DWRrU8734 TvNfhChgQnpzhaJWp2IBnCOEqyck5pOJhM5c59zlg3QT8bdqfuZPVaetqedKX9Jk79 SGxq3gcIKpdPmG37euoQU/HAIAFfvESteHiU0p9Mga2ri2Hd0Ll10mYmiyqPmvpubo pT9/VRpvP1Lwg==
Reply-To: dcrocker@bbiw.net
To: Alessandro Vesely <vesely@tana.it>, John R Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Cc: John C Klensin <john-ietf@jck.com>
References: <20210511185543.C751179052B@ary.qy> <D7EABCF7E8976BE735927C69@PSB> <65ed77dd-78fb-3f1a-7c21-63977620a510@taugh.com> <85e92b39-4dac-a26e-e85f-8edd1a383b83@tana.it>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <e5a017b2-1874-2bb1-c9a0-22a0101de2c6@dcrocker.net>
Date: Wed, 12 May 2021 11:46:30 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <85e92b39-4dac-a26e-e85f-8edd1a383b83@tana.it>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/EVIis3NrSpRjnP31pFv6BwIV27E>
Subject: Re: [ietf-smtp] Public Key Look Up
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2021 18:46:46 -0000

On 5/12/2021 10:04 AM, Alessandro Vesely wrote:
>> Indeed.  But if the keys include signatures, it doesn't matter where 
>> they come from, so we're back to asking why nobody seems to use the 
>> key servers that already exist.
> 
> Some people has been using those key servers.  However, they're 
> vulnerable to pgp-poisoning attacks[*].

The 'nobody' terminology is apt, in terms of operational statistics. 
The number of users is statistically insignificant, especially over a 
period of decades.

"Too few to matter" would be the alternative wording.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email