1  |   Order by index

Dec 24, 2004, 1:09am

I would very much like a Unique Login ID (4 byte long or perhaps an __int64)
to be assigned to each user when they log in and that is only used once (ie:
incremented each time).

This would allow bots to syncronise the avatars that they see by logs for
example:

aw-12345 would be the same to one bot as aw-12345 would be to another bot.

Very very handy for security purposes.

- MR

Dec 24, 2004, 2:24am

Could've replied in your original post about the same thing. ;)

[View Quote]

Dec 24, 2004, 2:32am

I already made one about this?? Pah.

Thats what happens when you delete the newsgroup and post at 4am in the
morning >_<

- Mark R

[View Quote]

Dec 24, 2004, 6:20am

A few points.

1. An __int64 would be silly when working in a 32bit processing
environment. I doubt even 2% of AW users have 64bit processors. Why
the need for extra cycles? 4 numerical bytes would be sufficient for
your purpose.

2. Session number. I submit this to you: If every bot can only enter
one world, then every instance of that bot in the world would have
navigated through the login, and received its own session number. So,
each bot, regardless of the naming similarities, would have a different
session number. This number is about as unique as you're going to get,
and the world server used it as a unique point of reference for a while.
Currently, you have more luck of bleeding jello from your eyes than
finding a session number collision. If this happens, save some for me,
watermelon flavor is my favorite. Session number counter is reset when
uniserver server is restarted, happens a lot now though ;) ; but quite
necessary from time to time as we don't want to exhaust the session
number pool (or it could just return to its default value when it gets
out of bounds, don't know, or care).

3. As for logging, logging the session number, time frame of the login,
name, sip, anything else would be sufficient. You could even hash these
things together into a crazy long unreadable number! Bot A will see Bot
B just the same as Bot C sees Bot B, both A and C will get the same
session number returned to them when Bot B joins their vision.

4. As for AW secutiry purposes... BAHAHAHAH... I mean, whats the point?

Hugs!
-Joe

[View Quote]

Dec 24, 2004, 8:45am

[View Quote] Right, 4 bytes probably would be enough.

> 2. Session number. I submit this to you: If every bot can only enter one
> world, then every instance of that bot in the world would have navigated
> through the login, and received its own session number. So, each bot,
> regardless of the naming similarities, would have a different session
> number. This number is about as unique as you're going to get, and the
> world server used it as a unique point of reference for a while.
> Currently, you have more luck of bleeding jello from your eyes than
> finding a session number collision. If this happens, save some for me,
> watermelon flavor is my favorite. Session number counter is reset when
> uniserver server is restarted, happens a lot now though ;) ; but quite
> necessary from time to time as we don't want to exhaust the session number
> pool (or it could just return to its default value when it gets out of
> bounds, don't know, or care).

Session # is reset as soon as it his 16 bit integer limit, hence why I
wanted something a little more fixed.

> 3. As for logging, logging the session number, time frame of the login,
> name, sip, anything else would be sufficient. You could even hash these
> things together into a crazy long unreadable number! Bot A will see Bot B
> just the same as Bot C sees Bot B, both A and C will get the same session
> number returned to them when Bot B joins their vision.

Thats what I am doing at the moment, however crazy long unreadable numbers
are not liked by my DBMS.

> 4. As for AW secutiry purposes... BAHAHAHAH... I mean, whats the point?

Because all your base are belong to us.

> Hugs!

Hugs 2 you too Joe!

> -Joe

- Mark

>
[View Quote]

1  |   Order by index