Newly Connected SSCV Zones

[L.C.]

Recently BlueT has attained two zones onto the SSCV network; their names are Realism Zone and Sector Eight.

 

SSCV Realism Zone uses specialized SVS settings that are based on a more literal application of the original ship descriptions featured in the old Subspace v1.34 client and the characteristics implied by the

.

 

SSCV Sector Eight utilizes a unique wormhole-basing concept, where flag rooms are protected by a wormhole and the only way to get past them is to use the appropriate ship (this is a small basing zone). Both zones are worth checking out! (Be sure to grab some friends to play with too.)

[Bak]

Are these on the directory server? I don't see them.

[L.C.]

All BlueT/SSCV zones broadcast to all the latest directory servers. I maintain that part of the server.ini. If it isn't showing up for you, well, I don't know what to say.

 

IP=sscentral.com,sscentral.sscuservers.net,ssdir.playsubspace.com,nanavati.net,ds1.krslynx.com,ds.hlrse.net,ds1.hlrse.net

[Dr Brain]

Your zones don't show up on sscentral.sscuservers.net. You probably have directory password problems.

[L.C.]

Your zones don't show up on sscentral.sscuservers.net. You probably have directory password problems.

Each zone on BlueT and SSCV uses a unique MD5 hash for its password.

[PoLiX]

he means for NamePassword... for all of them to properly show, they have to have the same password. It deals with the prefix, not the entire zone name.

[L.C.]

he means for NamePassword... for all of them to properly show, they have to have the same password. It deals with the prefix, not the entire zone name.

Then we have a conflict, no? Priit's directory server uses a different method of handling NamePassword's than does Snrrrub's or doc flabby's.

 

I believe that for Snrrrub's and doc flabby's, you have to have a unique password per zone.

And for Priit's, you have to have the same password for all zones under the same IP.

 

Am I incorrect?

[Dr Brain]

I refuse to believe that Snrrrub and Doc Flabby force you to use a different password for each zone.

 

Your choices are thus: use a single directory password like everyone else, or enjoy your completely secure and completely empty zones.

[PoLiX]

No, just the same password for any zone using the prefix. IP doesn't matter.

[L.C.]

and completely empty zones

I beg to differ on this -- rather the comment I have is that you fail at Subspace in missing the point of Subspace.

 

A more appropriate approach would have been to simply say that the tradeoff I would be facing is directory server inconsistencies due to using a more secure method.

 

No, just the same password for any zone using the prefix.

Alright. (Comment: That is still a stupid security method, because all it takes is knowing the password to hijack zone names.)

 

Lastly, it is untested as to how Snrrrub's and Doc's directory servers react when you use the inverse security method.

 

EDIT: Priit's directory servers should be abandoned as primary directory servers. For the poor SSC zones that are locked within it -- we can simply use clustering/leeching functions of other directory server software.

Edited March 15, 2010 by L.C.

[MikeTheNose]

How about hard coding those zones into DS's? With some method/function of grabbing population data? It's not like they are ever down (rarely).

[»doc flabby]

How about hard coding those zones into DS's? With some method/function of grabbing population data? It's not like they are ever down (rarely).

This is what i do with Central. All the main SSC zones are hardcoded.

 

Central uses passwords for individual zones only. I think they expiring after 24h i can check.

[L.C.]

How about hard coding those zones into DS's? With some method/function of grabbing population data? It's not like they are ever down (rarely).

This is what i do with Central. All the main SSC zones are hardcoded.

 

Central uses passwords for individual zones only. I think they expiring after 24h i can check.

Also, I realized that there should be no conflict in zones using the same password, because the security method of each zone having a unique password just means that's the highest degree of security level for zones.

 

Of feature requests for Sharvil's directory server, this would be awesome:

* Ability to manually add zones (regardless of NamePassword)

* Ability to manually add zones based on a fixed non-expiring NamePassword (can be used to "permanently" reserve names)

* Ability to block certain IPs from broadcasting to the directory server

* Ability to block certain IPs from retrieving listings

 

Hehe.

 

By the way, Sharvil's directory server accepts pings in case you want to find out if the server is still up. This way we can build an automated list instead of having to manually check and keep lists up-to-date. To ping any directories running Sharvil's server, just send a 4-byte packet to port 4991 (and if you get a response, it is still online). This feature has been around since v1.0.

[Dr Brain]

Your zones are still not showing on the directory server.

[PoLiX]

1 BlueT and 1 SSCV is. The 2 that SSCUServers 1st picked up, so their namepassword now must be set for all the BlueT and all the SSCV zones respectively for it to work.

 

BlueT Nintendo Basing

SSCV DragonBall Z

 

I'm not sure if you can disconnect them all and change the pass and reconnect with his dir server, but worth a shot.

[L.C.]

1 BlueT and 1 SSCV is. The 2 that SSCUServers 1st picked up, so their namepassword now must be set for all the BlueT and all the SSCV zones respectively for it to work.

 

BlueT Nintendo Basing

SSCV DragonBall Z

 

I'm not sure if you can disconnect them all and change the pass and reconnect with his dir server, but worth a shot.

Zones restarted (except for Nintendo Basing and Dragonball Z). It may take 24 to 48 hours for changes to settle in completely. I'm not sure how directory servers handle the changing of NamePassword's.

 

EDIT: ds1.hlrse.net and ds.hlrse.net restarted.

Edited March 16, 2010 by L.C.

[Samapico]

Or set all the zones to use the same name password as the ones that show up

[L.C.]

Or set all the zones to use the same name password as the ones that show up

That's what I did... using the information PoLiX provided.

[PoLiX]

All but BlueT Super Ships now show up on SSCUServers

[L.C.]

All but BlueT Super Ships now show up on SSCUServers

That's ASSS fault. *whistles*

 

EDIT: I think there is a NamePassword sort of thing for global.conf. I gotta look it up.

 

EDIT2: There is a "Password" -- so I added that and restarted the zone.

Edited March 16, 2010 by L.C.