1995-10-25 - Re: What is needed for S/MIME remailer ?

Header Data

From: Jeff Weinstein <jsw@netscape.com>
To: cypherpunks@toad.com
Message Hash: 6d1ad65687d73da83822f4fd7aa1847f28943356796be948f1575d74e6af238a
Message ID: <308D8019.648F@netscape.com>
Reply To: <9509248145.AA814556043@snail.rsa.com>
UTC Datetime: 1995-10-25 00:13:22 UTC
Raw Date: Tue, 24 Oct 95 17:13:22 PDT

Raw message

From: Jeff Weinstein <jsw@netscape.com>
Date: Tue, 24 Oct 95 17:13:22 PDT
To: cypherpunks@toad.com
Subject: Re: What is needed for S/MIME remailer ?
In-Reply-To: <9509248145.AA814556043@snail.rsa.com>
Message-ID: <308D8019.648F@netscape.com>
MIME-Version: 1.0
Content-Type: text/plain


baldwin , Robert W. Baldwin wrote:
> 
>         The other day I was wondering what it would take to make an
> anonymous remailer for an S/MIME client.  Implementing S/MIME from
> scratch is a lot of work given the lack of a public domain
> implementation, but it seems that a remailer could be built on top
> of a commercial email product that supported S/MIME.  The question
> is: What features should a commercial S/MIME email product have to
> make it easy to support a remailer?  Are there a small set of
> command line options that would greatly simplify a remailer
> implementation?

  S/MIME is mostly PKCS#7.  Eric Young is doing an implementation
of PKCS#7 for his SSLEAY package.  It seems like a good place
to start...

	--Jeff

-- 
Jeff Weinstein - Electronic Munitions Specialist
Netscape Communication Corporation
jsw@netscape.com - http://home.netscape.com/people/jsw
Any opinions expressed above are mine.





Thread