security - Should I commit self-signed certificates to source control? -


let's generate self-signed certificate each of our customers. they're used in part of package/deploy pipeline , end on customer's local computers. they're used connect our web services.

should commit these certificates source control? repository private , accessible coworkers. should leave them out security reason (even if that's limiting access in case of accidental exposure, let alone malicious activity)?

if leave them out, should generate them part of package/deploy pipeline every time? or stick them in secure keystore , retrieve them?

this situation of trust , exposure. trust have access repository? bear in mind compromises come insiders.

my thinking this:

  • don't store deployed certificates @ all. generate them end systems. sign them root certificate.
  • configure produce trust connections made certificates signed root. way can revoke certificates in mass if root compromised or selectively revoke endpoint certificates necessary without revoking everything.
  • you can have product reference certificate system's certificate store using public identifiers don't store private key.
  • making private key available should final deployment step minimal visibility possible. make available 2 or 3 users , use platform's certificate management mechanisms tying public certificate private key.

Comments

Popular posts from this blog

javascript - Jquery show_hide, what to add in order to make the page scroll to the bottom of the hidden field once button is clicked -

javascript - Highcharts multi-color line -

javascript - Enter key does not work in search box -