Yes, if you muck about with cookies in the browser, it's detected as suspicious and logs you out. However if you manage to by chance guess the session ID, you can use it to sign in with zero problem. You can actually prove this yourself by looking at how the authentication page works, it's not black magic. You will see s= in the redirect page, and you can straight up copy and paste the URL, send it to another computer, and log in with it elsewhere.
This is literally how the client manages to login to the website if you're already logged in in game. If you look at the address bar the client loads before it takes you to the message center or forums or news or whatever, you'll see the s= value with all ~150 characters.
So ok, your point might be the same. It might be some vague security policy, but it's absolutely unrelated to the actual thing you're saying it's a security policy for, and there's no reason to believe Jagex are in need of a Captcha to protect people randomly guessing session IDs because there's no reason to believe Jagex have implemented them in any way that goes against industry standards, so the FUD is entirely unnecessary.
28-Aug-2020 20:25:30
- Last edited on
28-Aug-2020 20:35:29
by
Hmm