[29653] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: PGP kerserver infrastructure

daemon@ATHENA.MIT.EDU (Roeland M.J. Meyer)
Sat Jul 1 17:52:09 2000

Reply-To: <rmeyer@mhsc.com>
From: "Roeland M.J. Meyer" <rmeyer@mhsc.com>
To: "'L. Sassaman'" <rabbi@quickie.net>
Cc: "'Michael Helm'" <helm@fionn.es.net>, <nanog@merit.edu>,
	<pgp-keyserver-folk@flame.org>
Date: Sat, 1 Jul 2000 14:47:59 -0700
Message-ID: <000001bfe3a6$066ebc60$eaaf6cc7@PEREGRIN>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.21.QNWS_2.0007011419350.16277-100000@thetis.deor.org>
Errors-To: owner-nanog-outgoing@merit.edu


> L. Sassaman : Saturday, July 01, 2000 2:22 PM

> On Sat, 1 Jul 2000, Roeland M.J. Meyer wrote:
>
> > > L. Sassaman
> > > Sent: Saturday, July 01, 2000 2:58 AM
> > >
> > > On Fri, 30 Jun 2000, Michael Helm wrote:
> > >
> > > > "L. Sassaman" writes:
> > > > > X.509 is a much older and cruftier standard. PGP is
> >
> > > > I think is up to customers to decide.
> > >
> > > I think customers *have* decided. Where is PEM now?
> >
> > PEM is being used on every ecommerce site site now, to
implement
>
> Privacy Enhanced Mail != Secure Socket Layer. And this
discussion is
> becoming absurd... I regret getting baited into a flame war,
> and will not
> continue down this line of discussion.

I am talking about PEM formatted keys and certs (*.pem files), as
formatted by OpenSSL. I don't recogise your definition of the
acronym.

Me may have a case of operator over-loading here. I'm also sorry
that you feel that this has become a flame-war. Maybe it is good
that we terminate it.



home help back first fref pref prev next nref lref last post