Network Title

Gravitron · February 3, 2010

Only reason people use SSC# is because of nostalgic purposes.

Ha, nope.

hint:

[Directory]
NamePassword=

[Directory]
IP=ssdir.vie.com
Description=
NamePassword=titanrebel
Port=4991

The only thing that does is provides a password to the directory server for it to match against its own password and acknowledge your zone as valid and include it in its listing it or otherwise reject it.

Unless Priit has changed that in his DirServ it has nothing to do at all with the zone's name. And I seem to recall non-SSC zones getting billing access (T3 is the obvious example).

So kindly explain what point were you driving to, because as it stands it makes no sense at all.

SSC is merely something born out of the council. There's a long history of network names that had no relevance to it at all.

IMHO, using "SS" in the server name/network name while the game itself is called SubSpace, is rather redundant (if not retarded).

If anything, I'd call it CS for Central Server or CSS for Central SubSpace Server. At least the naming scheme will be somewhat more straightforward and functional.

SubSpace Central could be as much replaced with SubSpaceHQ or SSN (which was used once before, I believe) - SubSpace Network, it's just a titular noun that'd fit sooner a website than a daemon / explain the function that it serves.

Infact as it stands history had plenty of servers/network names with nothing at all to do with SSC and yet hosted main (original VIE/original concept/popular) SubSpace zones.

VIE being the original Virgin servers, iNET - Sonera ISP via Baudchaser which took hold of the main biller, SSX - Exodus/C&W via Xalimar & Yarekim, RiSC - self owned via Nefocipher, T3 - whatever ISP Mecbot worked for, WLI/USD self owned via Gemini Dream and some more such as SFSS, so on and forth.

Heck, there was that whole thing when Alex (Ghost Ship) managed to entangle Verizon to host and they backed out after a month or few, which caused Pro League to have those odd initials infront of it.

Confess · February 3, 2010

Adding 'SSC' is moreso for the populations benefit. It helps some people realize that the zone is on SSC and thus it is 'secure' to connect. Plus, they can talk to their friends/etc.

MikeTheNose · February 4, 2010

SSC = SubSpace Central

The password function of the directory server allows a network to specify a password for a network and only that password will work. It prevents one from spoofing a network.

- A reply to "the" common stupidity of Gravitron.

Hakaku · February 4, 2010

Well, the name password used to communicate with the directory server still doesn't have anything to do with Jabjabjab's remark, which was that the prefix "SSC" in the Zone Name is used for nothing more than nostalgic purposes. There's no reason why a zone not using this prefix couldn't connect to the central billing server, with T3 The Gauntlet being the obvious example as Gravitron pointed out, other than the fact that the tag acts as a cheap method to signal to a player that the zone is connected to the SSC biller.

The problem with the 'spoofing a network' theory is that not all directory servers handle name passwords in the same way, if they handle them at all. And there's really no reason why they should specifically cater to the SSC prefix either. A zone could still be easily setup with the proper name password, but may not actually be connected to the SSC biller. In such, you've achieved no better security.

L.C. · February 4, 2010

The NamePassword function confuses me when Mike said it is supposed to be for whole networks there.

I might be wrong, but to my understanding, you are supposed to have a unique NamePassword for each zone to prevent hijacking of zone names in the directory server (or this is how Sharvil's directory server functions). And this makes sense to me as if it functioned similarly to SSL, locking domain names, and DNS TTLs.

If the zone were to go offline for maintenance or connectivity problems, a directory server might keep its name in the listing for 24 hours or however many specified by the directory operator until the zone of known host makes at least one signal. And while the zone would be offline, the only way to hijack its name in the list would be to use the same NamePassword.

Only way to find out might be to try and experiment (or ask doc_flabby and Sharvil about how theirs handle NamePassword). If it is supposed to prevent other hosts or people from using your network tag, then how do directory servers "properly" detect network titles in the technical sense? What about the zones without a network title, or hypothetically ones with a single-character network initial? Just some thoughts.

MikeTheNose · February 4, 2010

Ask Priit

It's his DS I refer to. The others are imitations. These guys probably never really knew about an "undocumented" feature. (Which is one of Priit's favorite things to do)

The NamePassword function confuses me when Mike said it is supposed to be for whole networks there.

I might be wrong, but to my understanding, you are supposed to have a unique NamePassword for each zone to prevent hijacking of zone names in the directory server (or this is how Sharvil's directory server functions). And this makes sense to me as if it functioned similarly to SSL, locking domain names, and DNS TTLs.

Just the prefix.

**Samapico** · February 4, 2010

I thought this all made sense, until I realized anyone could make his own directory server...

Gravitron · February 5, 2010

SSC = SubSpace Central

The password function of the directory server allows a network to specify a password for a network and only that password will work. It prevents one from spoofing a network.

- A reply to "the" common stupidity of Gravitron.

Bottom line is that the "SSC" in the zone name is just A PART OF THE ZONE NAME and, unless Priit has changed that, means JACK SHIT to being able to join the central biller and you need to have "SSC" in your zone's name like you'd need sulfuric acid in the air to be able to draw breath.

This has been my point, it has not changed. Your inane drivel has neither changed nor countered it. And your attempt to associate it to the directory server is yet "the" common stupidity of big fat nose guy who is on the council in the first place just because he rubbed someone else the right way and is otherwise lacking any proper functionality within SubSpace to answer the early requirements of being on the council or to be a BillingOp at that.

At least BDVine was Sonera's liason once Baudchaser ceased activity so you could excuse that inane propaganda drivel spreading hobgoblin's presence.

I've been watching you two post utter reality-and-fact-removed bullshit since the SSHQ days on the Matt Wright free forum script.

Edited February 5, 2010 by Ori Klein

»Xog · February 5, 2010

Jerry, Jerry, Jerry

»Lynx · February 5, 2010

Wow. Seriously?

whalz · February 5, 2010

hah awesome, your right anyway ori, as long as i can remember SSC has really just been a title that you plop in your zone name, then put the password in for the 'ssc' network and your in!... but thats ok.. right? or else everyone on all zones cud talk to each other and authentic SSC zones would lose some population!

all seems pretty frivilous to me :\

however im not sure what this topic was trying to prove, as we already knew 'council' was fairly retarded, and pointless... and we also knew SSC was just an elite club everyone tried to join..

Confess · February 5, 2010

Unless something has changed, the directory server stores the Namepassword making it impossible for anyone to use the same Prefix (IE, SST,BlueT, etc) without the same NamePassword. Try it, host a zone called "SSB SubspacePwnz" and a zone with a different name password, "SSB 123" - one will not load (although, there might be a 24 wait for the name password to be stored, i havnt checked...). I have had issues with this in the past, and so I know for a fact that is how it works. Now, since sscuservers.net has been down, and others have taken over, this might necessarily be the case anymore...Since, it is up to the directory server - not the directory client.

»Lynx · February 5, 2010

If it were a few months ago, I'd agree with you that the council is pointless. Now though, I disagree. All I can see is improvement. I think instead of riding the bandwagon so much - it's time to see why you're complaining; and see if your complaints are still valid. Currently, it seems, SSC will accept any zone that's hosted - no more population controls, you'll only have a hard time if you've had a record of malicious intent. That's a fair enough rule for me.

SSC prefix is not (or no longer, whatever... I can make an SSC# zone if I like) controlled by the central biller, as the trust is placed in the 'are you sure you want to play this zone' message. AFAIK only two people have broken that messages encryption (without editing the client). Also, I'd like to mention that every SSC zone has had SSC in it's zone title. Yes, even T3G did.

Edited February 5, 2010 by Lynx

whalz · February 6, 2010

hah its just with the SSCA, and SSCU and whatever the fawk... why cant it all be just SSC then? should just be a rule, the extra letter is kinda annoying

MikeTheNose · February 6, 2010

hah its just with the SSCA, and SSCU and whatever the fawk... why cant it all be just SSC then? should just be a rule, the extra letter is kinda annoying

Identifies a network.

L.C. · February 6, 2010

hah its just with the SSCA, and SSCU and whatever the fawk... why cant it all be just SSC then? should just be a rule, the extra letter is kinda annoying

Identifies a network.

But isn't this what that non-SSC warning pop-up in Subspace and Continuum clients are for?

»Lynx · February 6, 2010

I like being able to identify them when I am browsing the directory servers, too.

MikeTheNose · February 6, 2010

hah its just with the SSCA, and SSCU and whatever the fawk... why cant it all be just SSC then? should just be a rule, the extra letter is kinda annoying

Identifies a network.
But isn't this what that non-SSC warning pop-up in Subspace and Continuum clients are for?

That is a separate Priit peice of shit. It's basically notifying you the the encryption is different for a non-ssc hosted zone and could cause you to loose your account if you use the same password as you have on SSC. It's a matter of security.

»Maverick · February 17, 2010

Sign In

Network Title

Recommended Posts

Gravitron

Confess

MikeTheNose

Hakaku

L.C.

MikeTheNose

Samapico

Gravitron

»Xog

»Lynx

whalz

Confess

»Lynx

whalz

MikeTheNose

L.C.

»Lynx

MikeTheNose

»Maverick

Gravitron

»Maverick

L.C.

Hakaku

L.C.

PoLiX

Join the conversation

Browse

Activity