Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
I'm not planning to make this, although it is an interesting idea. I'm wondering if anyone made the following:
- decompile PlayerIO (this is illegal if shared)
- make the client object serializable
- package it back up
- serialize the client object
- transfer the client object somewhere else over the internet
- un-serialize it on the other end
- ta da, you just transferred your account to someone else without using a password
- to permanently deactivate it, logout the client from your end
Offline
Atilla made a temporary login token thing previously. But I doubt it works anymore.
Offline
Offline
You keep asking about things you commented on.
http://forums.everybodyedits.com/viewtopic.php?id=11511 :p
Offline
You keep asking about things you commented on.
http://forums.everybodyedits.com/viewtopic.php?id=11511
I saw that, but it's not exactly what I'm looking for. I'm looking for the ability to transfer your entire EE session to someone else, and have them place blocks and such, without a password. EEAuth is nice as you can prove that someone owns an account, but it can't transfer Client objects to my knowledge.
Offline
I AM NOT ATILLA Q_Q
I saw that, but it's not exactly what I'm looking for. I'm looking for the ability to transfer your entire EE session to someone else, and have them place blocks and such, without a password. EEAuth is nice as you can prove that someone owns an account, but it can't transfer Client objects to my knowledge.
EE sessions are actually something dangerous to play with. I know a few vulnerabilities in them that prevents me from publishing anything like this. You will end up compromising more security as people get to discover these issues.
I'm not trying to hold you off this, I'm just saying you won't get what you want to archive.
I have never thought of programming for reputation and honor. What I have in my heart must come out. That is the reason why I code.
Offline
I'm not trying to hold you off this, I'm just saying you won't get what you want to [achieve].
What I want to achieve is to give a bot your serialized session thing, then that way they can never transmit your password to someone else. When you're done with the bot, just call logout() on the session token and it's useless. However, as you said, there probably are vulnerabilities that I'm not considering that would make this not work or be very insecure. I don't want to make it though.
Offline
[ Started around 1732485456.5491 - Generated in 0.051 seconds, 12 queries executed - Memory usage: 1.49 MiB (Peak: 1.64 MiB) ]