Timeline for (Android) hacking server by a simple socket
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 10:46 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Jul 6, 2014 at 14:03 | comment | added | KDEx | If the question is concerned about RE to begin with i would say any stored secrets on the client would be less than optimal. Although you are right in that this will increase the effort and may discourage some bad users | |
| Jul 6, 2014 at 13:57 | comment | added | Mike Mackintosh | Yes. You will almost always need something on the client to validate the integrity, such as a pre-shared key, public/private key, client ssl cert, etc. At least the way described, it's hidden in the source and simple reverse engineering won't reveal it so easily. | |
| Jul 3, 2014 at 20:08 | comment | added | KDEx | In this case the secret is stored on the client correct? | |
| Jul 2, 2014 at 13:49 | history | answered | Mike Mackintosh | CC BY-SA 3.0 |