Re: PKI and S/MIME

Simon Josefsson <jas@extundo.com> Fri, 15 August 2003 00:09 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02342 for <smime-archive@lists.ietf.org>; Thu, 14 Aug 2003 20:09:10 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7ENfQqt025491 for <ietf-smime-bks@above.proper.com>; Thu, 14 Aug 2003 16:41:26 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h7ENfQUl025490 for ietf-smime-bks; Thu, 14 Aug 2003 16:41:26 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7ENfNqt025484 for <ietf-smime@imc.org>; Thu, 14 Aug 2003 16:41:25 -0700 (PDT) (envelope-from jas@extundo.com)
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h7ENfMdk021563 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 15 Aug 2003 01:41:22 +0200
To: Blake Ramsdell <blake@brutesquadlabs.com>
Cc: 'Steve Hole' <steve.hole@messagingdirect.com>, ietf-smime@imc.org
Subject: Re: PKI and S/MIME
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAHio9i3PBckO2Z8s7yH8ufgEAAAAA@brutesquadlabs.com>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030814:blake@brutesquadlabs.com:d3bfd22292ed378d
X-Hashcash: 0:030814:blake@brutesquadlabs.com:d3bfd22292ed378d
X-Payment: hashcash 1.2 0:030814:steve.hole@messagingdirect.com:2b39444c2479cd42
X-Hashcash: 0:030814:steve.hole@messagingdirect.com:2b39444c2479cd42
X-Payment: hashcash 1.2 0:030814:ietf-smime@imc.org:b1cca659819c8658
X-Hashcash: 0:030814:ietf-smime@imc.org:b1cca659819c8658
Date: Fri, 15 Aug 2003 01:41:22 +0200
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAHio9i3PBckO2Z8s7yH8ufgEAAAAA@brutesquadlabs.com> (Blake Ramsdell's message of "Thu, 14 Aug 2003 15:40:51 -0700")
Message-ID: <ilud6f7g63h.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>

"Blake Ramsdell" <blake@brutesquadlabs.com> writes:

> Well, I'm not sure I agree with you here.  End user SMTP/POP3/IMAP mail
> clients today don't implement lots of DNS operations -- they just say
> "all mail goes to this SMTP server" which is a simple gethostbyname
> style call.  Specifically, they don't deal with MX records.  It has
> actually been pointed out in other forums (and I've had experience with
> this myself) that Windows is particularly ornery to work with for
> arbitrary DNS record types that aren't supported through native APIs (I
> had to write my own DNS client code to handle MX records back in the
> day, and Peter Gutmann told me he got slapped around pretty good trying
> to work with SRV records).

Steve Hole <steve.hole@messagingdirect.com> writes:

>> Even here there is an advantage for DNS: mail clients already
>> implement DNS.  There is no need to open ports in firewalls etc for
>> LDAP or XKMS.  There is no need to implement new client code in the
>> mail client.
>
> That is, regrettably, not accurate.   Existing clients do very little but 
> hostname to address translation and service port location.   I would be 
> very surprised if they did anything but gethostbyname and getservbyname 
> calls (or the platform API equivalent).   It would be an addition to get 
> them to query and retrieve records directly.

It is clear that I have been spoiled by working with free software
mail clients in the Unix world, which often do implement this.  Even
when they don't, a res_query() is never far away.  Thanks for sharing
experiences from other environments.

Still, I believe part of my argument still holds.  Even if your mail
clients only use gethostbyname(), that still means the DNS
infrastructure is available on the client machine.  It hasn't been
blocked by firewalls etc.  This simplifies deployment.

But this isn't an important point, and I don't see anything that can
be seen as a _disadvantage_ for DNS compared to LDAP or XKMS here.
Perhaps this tangental issue only distract us from the big picture.

Regards,
Simon