1996-03-26 - Re: MUSE (Mail Ubiquitous Security Extensions) discussion starting

Header Data

From: Ned Freed <NED@INNOSOFT.COM>
To: John Gilmore <gnu@toad.com>
Message Hash: e4e10d7c34d687bb21b44562205f11a914e4e334ac24eca15a7070f931db38ed
Message ID: <01I2S0UBDAI0A8CRXS@INNOSOFT.COM>
Reply To: <9603260842.AA07183@toad.com>
UTC Datetime: 1996-03-26 19:30:06 UTC
Raw Date: Wed, 27 Mar 1996 03:30:06 +0800

Raw message

From: Ned Freed <NED@INNOSOFT.COM>
Date: Wed, 27 Mar 1996 03:30:06 +0800
To: John Gilmore <gnu@toad.com>
Subject: Re: MUSE (Mail Ubiquitous Security Extensions) discussion starting
In-Reply-To: <9603260842.AA07183@toad.com>
Message-ID: <01I2S0UBDAI0A8CRXS@INNOSOFT.COM>
MIME-Version: 1.0
Content-Type: text/plain


> One initial technical question I have about MUSE is why to bother
> encapsulating email messages while in transit in more layers of MIME
> glop?  Why not just run IP Security between the sendmail daemons
> involved, and have the receiving sendmail daemon note in the Received
> header that the message arrived over an authenticated connection?

Because this gives you a point-to-point solution. MUSE is still end-to-end; the
only difference is that the ends have moved slightly away from the user in the
interests of deployment expediency.

> IPSEC provides your choice of authentication and/or encryption, and
> already uses the keys from the Domain Name System.  IPSEC solves many
> other problems as well as the particular secure/private email delivery
> problem.  And deploying a Real Application (sendmail) that uses IPSEC
> would shake it out and get it widely used.

IPSEC does indeed solve many problems. Unfortunatly secure email end-to-end
email isn't one of them.

				Ned





Thread