GitHub PushEvent at 2014-09-12 13:29:18
Repository: bitcoin-secp256k1-rs
Actor: apoelstra
Payload: {"shas":[["98890907849326a0e265d0ee12d3caa232b19602","510b48a683d671f79b4b3983c748588464f8f5d4@wpsoftware.net","Overhaul interface to use zero-on-free SecretKeys\n\nUsing the `secretdata` library, we can store SecretKeys in such a way\nthat they cannot be moved or copied, and their memory is zeroed out on\ndrop. This gives us some assurance that in the case of memory unsafety,\nthere is not secret key data lying around anywhere that we don't expect.\n\nUnfortunately, it means that we cannot construct secret keys and then\nreturn them, which forces the interface to change a fair bit. I removed\nthe `generate_keypair` function from Secp256k1, then `generate_nonce`\nfor symmetry, then dropped the `Secp256k1` struct entirely because it\nturned out that none of the remaining functions used the `self` param.\n\nSo here we are. I bumped the version number. Sorry about this.","Andrew Poelstra",true],["9cab4e023d90a283f1a38811f92b1ed616632db0","510b48a683d671f79b4b3983c748588464f8f5d4@wpsoftware.net","Revert \"Overhaul interface to use zero-on-free SecretKeys\"\n\nThis reverts commit 98890907849326a0e265d0ee12d3caa232b19602.\n\nThis is not ready for primetime -- the move prevention also prevents\nreborrowing, which makes secret keys nearly unusable.","Andrew Poelstra",true]],"size":2,"ref":"refs/heads/master","head":"9cab4e023d90a283f1a38811f92b1ed616632db0"}