Timeline for How to handle self-made certificates for Windows executables?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2016 at 9:10 | comment | added | Julian Knight | To trust a self-signed certificate, you need to create your own CA. It isn't difficult but you are taking on the secure distribution & installation of the CA cert to all clients that need to trust your certs. This can be a significant overhead. Using certs signed by an existing trusted root takes away this overhead. | |
| Nov 14, 2016 at 0:11 | comment | added | kubanczyk | @MaxR. This is about trusted certificates. Trusted certificates should always be self-signed as a matter of policy and that's totally OK. It only makes sense to go to CA to sign a certificate if you are not going to trust that certificate (by definition of not trusting, you will then proceed to verify the certificate's signature). | |
| Sep 15, 2016 at 19:51 | comment | added | Julian Knight | Well locking down a kiosk type system is perhaps a different question. But in terms of your code, having ways to be able to easily reinstall the code might be the best approach though obviously you need to take care of any local data. | |
| Sep 15, 2016 at 10:30 | comment | added | Max R. | Thanks you. Yes, you are right, but I don't just want my customers to be safe, I also want my system to be safe, so the customer can't install any stupid software and is angry two days later because the system does not work as it should, this is the most important thing for me. | |
| Sep 14, 2016 at 22:32 | history | answered | Julian Knight | CC BY-SA 3.0 |