Apparently their keyserver is broken. They don't have an ETA for uptime. If you use PGP authentication: Be warned. GK
According to the folks there, it's been down for quite some time (~a month). Glad they sent us notification. They asked that I swap PGP with CRYPT to facilitate modifications for the near future. -C At 03:15 PM 2/20/98 -0800, you wrote:
Apparently their keyserver is broken. They don't have an ETA for uptime. If you use PGP authentication: Be warned.
GK
At 06:49 PM 2/20/98 -0500, Christopher Caldwell wrote:
According to the folks there, it's been down for quite some time (~a month). Glad they sent us notification.
They asked that I swap PGP with CRYPT to facilitate modifications for the near future.
hmmm to make changes you have to PGP authenticate the request.... Catch22, no? Yes, I am being obnoxious. You can obviously call them and have them update all your (how many?) domains manually do eliminate the pgp requirement so that you can then change each one to CRYPT. [File away that first response that has your encrypted password. I am told you don't ever get it again.] It would be Much nicer if they would just fix it. GK
On Fri, 20 Feb 1998 16:08:50 -0800, gketell@cisco.com writes:
It would be Much nicer if they would just fix it.
I'm sorry, but fixing it will necessitate an additional $30/year/domain surcharge for infrastructure improvements. Please mail your check in as soon as possible... -Jon ----------------------------------------------------------------- * Jon Green * "Life's a dance * * jcgreen@netINS.net * you learn as you go" * * Finger for Geek Code/PGP * * * #include "std_disclaimer.h" * http://www.netins.net/showcase/jcgreen * -------------------------------------------------------------------------
On Fri, 20 Feb 1998, Greg Ketell wrote:
At 06:49 PM 2/20/98 -0500, Christopher Caldwell wrote:
According to the folks there, it's been down for quite some time (~a month). Glad they sent us notification.
They asked that I swap PGP with CRYPT to facilitate modifications for the near future.
hmmm to make changes you have to PGP authenticate the request.... Catch22, no?
Yes, I am being obnoxious. You can obviously call them and have them update all your (how many?) domains manually do eliminate the pgp requirement so that you can then change each one to CRYPT. [File away that first response that has your encrypted password. I am told you don't ever get it again.]
Actually a couple of weeks ago I was able to get domains via PGP. The weird thing was that they sent back two of them telling me they couldn't decode them (and right there is the return email they were fully decoded). The even stranger thing was when I resubmitted things they came back and told me that the domains already existed. So they actually added the domain for me and sent back the wrong message the first time.
It would be Much nicer if they would just fix it.
Well uh, yeah... bye, ken emery
Greg Ketell wrote:
Apparently their keyserver is broken. They don't have an ETA for uptime. If you use PGP authentication: Be warned.
Worse than that, it's been broken since before Thanksgiving and they sent no error messages or anything! I had been trying really hard to make changes during the holidays and no one there (even by telephone) would tell me why my authentication was failing. Another typical crock with this "service" provider. *sigh* (Yeah, it frosted me; I spent a *ton* of time trying to get those changes in!) -- Steve Hultquist, Chief Technology Officer HSAnet providing high-speed Internet access Boulder, Colorado mailto:ssh@HSAnet.net +1.303.581.0800 http://www.HSAnet.net/
participants (5)
-
Christopher Caldwell -
Greg Ketell -
Jon Green -
ken emery -
Steve Hultquist