Timeline for Issuing and managing large numbers of certificates for client authentication
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2015 at 20:50 | history | tweeted | twitter.com/StackSecurity/status/674330344070512641 | ||
| Dec 8, 2015 at 19:39 | vote | accept | AnodeCathode | ||
| Dec 8, 2015 at 19:08 | answer | added | Mike Ounsworth | timeline score: 5 | |
| Dec 8, 2015 at 19:08 | comment | added | AnodeCathode | The certs are issued at production time, but will be used to authenticate the client with the server for the life of the client (probably 3-5 years). I don't think they need to be verifiable by a 3rd party, as they will always used to communicate only with our servers, but that's what part 1 of my question was hoping to verify | |
| Dec 8, 2015 at 18:53 | comment | added | Mike Ounsworth | Are your certs only for use during the production-line (ex for grabbing firmware securely), or will they ship with the certs still on, and need the certs to be verifiable by any 3rd party? | |
| Dec 8, 2015 at 18:48 | review | First posts | |||
| Dec 8, 2015 at 19:01 | |||||
| Dec 8, 2015 at 18:46 | history | asked | AnodeCathode | CC BY-SA 3.0 |