Timeline for Mitigating SSL bypassing on iOS
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2015 at 6:47 | history | edited | Mohsin Khan | CC BY-SA 3.0 |
I have further expanded my options for the security of my application and wrote under the 'Edit' tag
|
| Sep 16, 2015 at 6:02 | comment | added | Mohsin Khan | So in the end we are again at the basics of information security, We can make it hard for an attacker to break in but can not guarantee foolproof security. | |
| Sep 15, 2015 at 22:59 | comment | added | Criticizing Israel not allowed | If you do that, then if your app is important enough, someone will bypass your SSL bypass mitigation. And then you'll add SSL bypass mitigation bypass mitigation. And then they'll bypass your SSL bypass mitigation bypass mitigation. And so on. The user has full control over the device - if they really wanted to, they could just make the device skip over your mitigation code. | |
| Sep 15, 2015 at 12:11 | history | tweeted | twitter.com/#!/StackSecurity/status/643759081619083264 | ||
| Sep 15, 2015 at 11:04 | answer | added | Steffen Ullrich | timeline score: 17 | |
| Sep 15, 2015 at 10:48 | answer | added | StackzOfZtuff | timeline score: 6 | |
| Sep 15, 2015 at 10:39 | history | edited | StackzOfZtuff | CC BY-SA 3.0 |
+links
|
| Sep 15, 2015 at 10:33 | review | First posts | |||
| Sep 15, 2015 at 11:13 | |||||
| Sep 15, 2015 at 10:30 | history | edited | user45139 | CC BY-SA 3.0 |
deleted 22 characters in body
|
| Sep 15, 2015 at 10:29 | history | asked | Mohsin Khan | CC BY-SA 3.0 |