{"push_id":2324028420,"size":2,"distinct_size":2,"ref":"refs/heads/pr-rand-drbg-code-cleanup","head":"5877d1415ec09331deb0a089ca824002515e12ff","before":"615de24e7fbf740cfb4eba626c1966e84ab99c8c","commits":[{"sha":"dfa9f5909e49b524c51853de79c254b3fce14e2e","author":{"name":"Dr. Matthias St. Pierre","email":"69c197f30a5016bb63ab396735fc81a1a3d755c3@ncp-e.com"},"message":"fixup! DRBG: unify initialization and cleanup code\n\nUse secure heap only for the three global DRBGs","distinct":true,"url":"https://api.github.com/repos/mspncp/openssl/commits/dfa9f5909e49b524c51853de79c254b3fce14e2e"},{"sha":"5877d1415ec09331deb0a089ca824002515e12ff","author":{"name":"Dr. Matthias St. Pierre","email":"69c197f30a5016bb63ab396735fc81a1a3d755c3@ncp-e.com"},"message":"OPENSSL_cleanup: cleanup secure memory\n\nIf the global DRBGs are allocated on the secure heap, then calling\nCRYPTO_secure_malloc_done() inside main() will have no effect, unless\nOPENSSL_cleanup() has been called explicitely before that, because\notherwise the DRBGs will still be allocated. So it is better to cleanup\nthe secure heap automatically at the end of OPENSSL_cleanup().","distinct":true,"url":"https://api.github.com/repos/mspncp/openssl/commits/5877d1415ec09331deb0a089ca824002515e12ff"}]}
{"actor":{"display_login":"mspncp"}}