-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2016/1/18 19:58, Ethan Heilman via bitcoin-dev wrote: > I believe libsecp256k1 just performs Elliptic Curve operations > required by Bitcoin. OpenSSL is used for all other crypto.
The exact answer, as I understand it, is a bit more nuanced. In particular, you referenced the PRNG. I believe libsecp256k1, as currently written, relies on an implementation of RFC 6979 instead of using a PRNG. I'm guessing this is done for portability reasons (no need to hook into the OS's RNG). Otherwise, yes, I believe this answer is basically correct. There are still some crypto functions not covered by libsecp256k1, at least at the API level. But, for consensus-critical functionality, I think 0.12 will be rid of OpenSSL. - -- - --- Douglas Roark Cryptocurrency, network security, travel, and art. https://onename.com/droark [email protected] PGP key ID: 26623924 -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWoEkTAAoJEEOBHRomYjkkoR0QAKmvgmoOdCw7SLP9cFURltXw Ro8mOfikjp04C6tsshtiKQ1+jq80wBhioVYIL7XiyNU7ZUNdAWSc/wGBCG+YkMeQ 6h02WJZQtTe0PvGVHIgUw6SiV4ZzXBuapXQX0BgEl0pInvQkRRqWtgrqDlWbqJVg NKzm8Kh+c8JUHEKbhnC45Jgh2JYHpyXcByLHSyGYsPOprjHmsupCPC6qydrRnuaO r7YHtObK2myOglJ1h6BXir//+XNbk6RiRNf5voONNAR9L+69BBV7hMVVO3eiDZ12 vrNaOIKhDjhDs1kmkFYi7ML/zKBQRXlb7iM8AEpfCUKl/zK9bSNeblP4ZBGPqjCm 9TGCqGjmKEbg7AYXjyMvmw+jZReediJMNYpCdxaSJi+XJZO6EC28pcKsb6pu/9gX NCLf1T/f2NoyXxc57aTuHNo0SnVaee1z0+IlGSh+5foxhZGbFmPhxOy3WNIubuou tm0guAXloCCERwVg0OhhQ3YyrlOWz7VnUrT8cteQC+yP353zdnxay7ZmQh9swcyR VX7yu4xLcxgbQmBIhMyKs9iQnycOrdNhZEfGx4vQ2ZKAj1CPVqrgKxbtY3KuPfvb YAzfs/iXaqBHH7FN9juLMRGqkzyVzJ9mIsFyLldADvSoc8RSa1IQiZtfPsIU1w1i UKEl9Qasje80EojNZNz0 =glL2 -----END PGP SIGNATURE----- _______________________________________________ bitcoin-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
