Timeline for security for android app in communicate with webservice
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 24, 2015 at 15:52 | comment | added | Leonar Aung | I know this method is not 100% secure enough but you should also know every approach is not 100% secure. This method is creating complex sentences, such variable from dynamic database, some from sum of clicks, some from date, all combining together and substring it again. As complex as your code is , there is a little chance to cross it over. We are not deciding to write down all of code in .java. Providing essential parts from database and getting from dynamic calculating. @ Martin Baker / / Thank you. | |
| Nov 24, 2015 at 12:54 | comment | added | Barkermn01 | Java Decompiling is bad but the worst thing to do for a secure app is using Cordova/Phonegap or something like that where all your communication source is left perfectly intact in the app to the point you can just change the extension of both IPA or APK to ZIP and obtain all your JavaScript code. so your "complex" sentences some one can just read the encryption code and reverse it... | |
| Nov 17, 2015 at 0:57 | comment | added | Reed | that is still merely security by obscurity, which is really not security at all. a determined individual could decode it just with time. | |
| Nov 16, 2015 at 15:56 | comment | added | Leonar Aung | Yes, it is just simple idea and how you think on it. Not good or not bad ? @PeeHaa | |
| Nov 16, 2015 at 15:45 | comment | added | PeeHaa | "Anyone, from the most clueless amateur to the best cryptographer, can create an algorithm that he himself can't break." | |
| Nov 16, 2015 at 15:25 | history | answered | Leonar Aung | CC BY-SA 3.0 |