Actually, its "remote registry"-"network one"-"toronto".opensrs.net...
Back when we actually followed this convention we hosted on a number of
networks and anticipated a much greater degree of geographic diversity than
what we actually ended up with...
The big long URL was never supposed to see the light of day, but due to a
miscommunication in the early days, it was sent out to our resellers...oh
well...
-rwr
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Daminato
> Sent: Monday, March 12, 2001 9:41 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: OpenSRS Live Reseller Update 03/12/01: Web Certificates!
>
>
> rr-n1-tor stands for "root registry", "node 1", "toronto" - the naming
> convention was put in place when plans for the layout of OpenSRS (and its
> respective components) were different. The UserDir is a throwback from a
> legacy layout, but it's not necessary anymore - just setup for backwards
> compatability - using rr-n1-tor.opensrs.net/resellers works just as good
> :)
>
> Charles Daminato
> TUCOWS Product Manager (ccTLDs)
> [EMAIL PROTECTED]
>
> On Tue, 13 Mar 2001, [EMAIL PROTECTED] wrote:
>
> > WebWiz <[EMAIL PROTECTED]> said:
> >
> > > Alan's right...it's insecure all the way down to the "login" window.
> > > OpenSRS has, in the past, used pretty URLs with frames to
> make for easier
> > > access to hard-to-remember URLs (e.g.,
> http://resellers.opensrs.net instead
> > > of https://rr-n1-tor.opensrs.net/~vpop/resellers).
> > >
> > Always wondered about that. Why rr-n1-tor.opensrs.net? Why a
> UserDir (~vpop)?
> > Backwards compatibility is all well and good, but still...
> >
> > adam
> >
>
