Timeline for Will digital signature prevent tempering, or at least harden the cracking, of my Windows applications?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2016 at 4:17 | vote | accept | Vlastimil Burián | ||
| Sep 9, 2016 at 16:15 | answer | added | Philipp | timeline score: 2 | |
| Sep 9, 2016 at 15:42 | answer | added | mzhaase | timeline score: 6 | |
| Sep 9, 2016 at 15:37 | comment | added | Yorick de Wid | You can also encrypt some .code segments. Be aware of virusscanners though. This falls in the category 'suspicious behaviour'. Like Aria said, signatures can only verify that you created the program, it doesn't protect its contents (neither should it). | |
| Sep 9, 2016 at 15:22 | comment | added | Aria | Obfuscating is usually good approach. You can use built-in obfuscator or try to obfuscate the most sensitive parts and keep changing it from version to version so it's not trivial to decompile it (like .net). | |
| Sep 9, 2016 at 15:19 | comment | added | Aria | Signing is not encrypting. It helps users to verify authenticity of the EXE. If users do not have mechanisms to do it, or the OS is not enforcing it (like Windows 10 doesn't by default except drivers, and not on all instances now), there's no real benefit really. And no protection against cracking at all. | |
| Sep 9, 2016 at 15:11 | history | asked | Vlastimil Burián | CC BY-SA 3.0 |