Securing the PS3 is not a major issue, The only systems which can be rooted are the ones already rooted by their owners, and PSN periodically updates itself to prevent folks with hacked consoles participating in PSN, so their authentication will typically take care of that. In any event there is a dearth of 3rd party malware that does anything to a PS3 rooted or otherwise.Quote:
Originally Posted by KisaiTenshi
-
10-13-2013, 07:04 AMKosmos992k
-
10-13-2013, 07:26 AMAnnahhe did. That's why he posted it here. The thing is, the DEVs and GMs do not even read those reports...the DEV here even said they didn't last week.Quote:
Originally Posted by Soukyuu
-
10-13-2013, 07:27 PMSoukyuuYou're several pages late, someone told me he did already. Also the devs don't post here, only community reps. And what they said is that they don't provide replies, not that they don't read the reports.Quote:
Originally Posted by Annah
-
10-13-2013, 09:24 PMClaire_Farron
In this thread people who can't potato.
-
10-14-2013, 05:35 AMJess72
What I don't understand is this part..
I was able to give only an old, supposed to be expired, session ID to a friend and they were able to log into my account and characters from an entirely different location in the world. I did not provide an account name, password, or one time password.
How exactly did his friend log into the account without account name and password? -
10-14-2013, 05:54 AMTicktickthe session id is tied to the account, so if you have the session ID, it thinks you're the other person.Quote:
Originally Posted by Jess72
-
10-14-2013, 05:58 AMCiennaUsing the session ID & the command line, you login without the launcher, thus no password, account name or token needed- just the session ID.Quote:
Originally Posted by Jess72
http://forum.square-enix.com/ffxiv/t...=1#post1390622
Quote:
That is where the session ID comes into play. The launcher invokes the game client by executing ffxiv.exe with extra command line parameters. It appends DEV.TestSID=xxxx, where xxx is the session ID, to the launch command. Here is the issue with that. That session ID is now plainly visible with any basic process inspector such as Microsoft's Process Explorer. This means it is incredibly easy for any virus that is on the computer to obtain the information. This also means it is possible to bypass the launcher to load the game client by just repeating the same command at the command line.
-
10-16-2013, 08:29 PMSoukyuu
An interesting thing I noticed since the latest patch is that now I am getting a 90k error followed by "authentification failed" one, forcing me to close the client. I seem to not be the only one, see discussion thread here.
The reason why I'm posting here is, does anyone think they might have implemented a session ID timeout but it's not working as intended? The timespan between those kicks seems to be around 4 hours for me. Maybe the session expires despite having a valid connection? -
11-30-2013, 12:25 PMillriginalized
SE you need to fix this. This is a freaking security hole.
-
12-16-2021, 04:06 AMDevourn
Yeah, good luck with getting an official support response. All I ever see are Forum Moderators apologizing for their ineptitude.
-
12-16-2021, 04:08 AMValkyrie_LennethThis is 8 years old.Quote:
Originally Posted by Devourn
-
12-16-2021, 05:06 AMHiragawaOh... oh that brings me great amusement when bumping a thread from 2013. Thanks for the chuckle.Quote:
Originally Posted by Devourn