Anchor server is saving all generated certificates

[Michael Xin]

In current implementation, Anchor server is storing all generated certificates under certs/ directory. This is at the risk of information leakage:

For example,
2015-09-01 11:08:38,863 DEBUG [anchor.certificate_ops][2139/MainThread] _run_validator: success: <key_usage>
2015-09-01 11:08:38,880 INFO [anchor.certificate_ops][2139/MainThread] Signing certificate for </CN=anchor-test.example.com> with serial <837574872541516398>
2015-09-01 11:08:38,911 INFO [anchor.certificate_ops][2139/MainThread] Saving certificate to: certs/B30F0F5B5F096D2DC860C43A4E275CFCA1DF64986957194E8F51FEAB520F44F8.crt
2015-09-01 11:08:38,919 INFO [wsgi][2139/MainThread] 127.0.0.1 - - [01/Sep/2015:11:08:36 -0700] "POST /sign HTTP/1.1" 200 1351 "-" "curl/7.30.0"

[Tim Kelsey (tim-kelsey)]

this is old behaviour, the latest version will only save certificates if an explicit output path is given. While there seems to be no valid situation (other than debugging) to save the certs locally, im going to leave this code incase I'm missing something.

[Stanislaw Pitucha (stanislaw-pitucha)]

Is there anything wrong with actually saving all the certs? I did that intentionally to leave the audit history.

Otherwise you may end up with someone finding a bug, getting a cert for *.com and the only thing you're left with is what's in the logs (which is probably not enough).

What we could definitely do is protect the certificates with umask that makes them 0400.