JEDI Comport » ((JEDI RolePlay Mod/RPMod)) » Bug Reports
-
Notifications ()
Notifications Settings
- You have no notifications
[CONFIRMED] Account login?
- Rash Loist
- Lost One
- Posts: 957
- Joined: Sun Apr 30, 2006 3:06 pm
- Location: Deceased
[CONFIRMED] Account login?
Tonight when I came back onto the server, I went to hit my login bind as usually and I got a message from Tel and him telling me that apparently he was logged into my account for a moment.
Clicky
Very odd, Tel wasn't doing anything with accounts either. This could be a major issue waiting to explode just thought i'd point it out.
Clicky
Very odd, Tel wasn't doing anything with accounts either. This could be a major issue waiting to explode just thought i'd point it out.
- Fane Ornn'ila
- Lost One
- Posts: 567
- Joined: Sun Jun 28, 2009 7:58 am
Wow. That's scary
As far as I can see after early investigations, this seems to only happen while/after spectating someone, as Maloush suggested. Rash, could you confirm you were following, or last followed Tel before logging in? (if you remember)
Basically, the problem is that the client number* is wrong under certain circumstances. This could impact a LOT of things, but by chance not much can happen while you are a spectator. At least there don't seem to be any consequence as far as accounts are concerned.
(* only the client number stored in ent->s.number is concerned here, there are other ways to get it - one of which is also unreliable, but already fixed long ago).
If this cause is confirmed, it should be relatively easy to fix, at least for messages. For the rest (1004 occurrences in the code), I'd have to investigate in detail to see what the consequences are. No client update would be necessary.
Oh, and because two out of two people responding to this thread encountered this potentially critical issue several times and said nothing, and because this is not the first time this happens...
As far as I can see after early investigations, this seems to only happen while/after spectating someone, as Maloush suggested. Rash, could you confirm you were following, or last followed Tel before logging in? (if you remember)
Basically, the problem is that the client number* is wrong under certain circumstances. This could impact a LOT of things, but by chance not much can happen while you are a spectator. At least there don't seem to be any consequence as far as accounts are concerned.
(* only the client number stored in ent->s.number is concerned here, there are other ways to get it - one of which is also unreliable, but already fixed long ago).
If this cause is confirmed, it should be relatively easy to fix, at least for messages. For the rest (1004 occurrences in the code), I'd have to investigate in detail to see what the consequences are. No client update would be necessary.
Oh, and because two out of two people responding to this thread encountered this potentially critical issue several times and said nothing, and because this is not the first time this happens...
IMPORTANT NOTICE
- PLEASE TAKE THE TIME TO REPORT BUGS -
- DO NOT IGNORE BUGS -
- DO NOT ASSUME I KNOW ALL OF THEM -
- I CAN'T FIX BUGS I DO NOT KNOW -
Thank you.
I can have Corinth make cookies for you if you want
-
- Posts: 218
- Joined: Thu Sep 03, 2009 11:55 am
- Location: Coruscant ::JEDI:: Temple