[43648] in North American Network Operators' Group
Re: NetSol's PGP auth ... and the road not taken
daemon@ATHENA.MIT.EDU (Peter Galbavy)
Mon Oct 22 08:22:27 2001
Message-ID: <01f001c15af4$093a99c0$6000a8c0@interhouse.redbus.com>
From: "Peter Galbavy" <peter.galbavy@knowtion.net>
To: "Joe Rhett" <jrhett@isite.net>, <beldridg@best.com>
Cc: <nanog@merit.edu>
Date: Mon, 22 Oct 2001 13:21:02 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Or move to another registrar. I can strongly recommend Tucows/openSRS with no
other relationship that being a very happy reseller.
rgds,
--
Peter Galbavy
Knowtion Ltd.
----- Original Message -----
From: "Joe Rhett" <jrhett@isite.net>
To: <beldridg@best.com>
Cc: <nanog@merit.edu>
Sent: Monday, October 22, 2001 8:24 AM
Subject: NetSol's PGP auth ... and the road not taken
>
> > i've been trying to add a pgp key to the verisign/netsol database for the
> > past two weeks. i've sent four messages, opened three web help requests,
> > and spent three hours on the phone with their helpdesk. they know less
> > than their customers about their own procedures and web documentation for
> > adding keys for PGP guardian auth.
>
> Don't waste your time. We had PGP auth working for the last 6 years. It
> will slow down any change you want to make by 3-5 days. Around 30% will get
> rejected for no reason whatsoever, and much more fun stuff.
>
> They're probably ignoring new submissions because they never finished an
> automated infrastructure to support it, which means they do it all by hand,
> painfully for them and their customers.
>
> If you do insist on going that route, get used to sending the mail, then
> calling up and waiting on hold for 1-2 hours, then pushing to get someone
> who knows what PGP is to process the message. Otherwise it make take 5 days
> before you get a response, and it will be a confused rejection.
>
> --
> Joe Rhett Chief Geek
> JRhett@ISite.Net ISite Services, Inc.
>
