📅 Original date posted:2016-01-21
📝 Original message:-----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
joroark at vt.edu
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-----
Douglas Roark [ARCHIVE] /
npub12v…dqa4q
2023-06-07 17:47:58
in reply to nevent1q…l4vt
Author Public Key
npub12vlytlltjj7g3s227u9jtx2g8qtsu7gscynnn99k808ydr4vygcqvdqa4qPublished at
2023-06-07 17:47:58Event JSON
{
"id": "dd19cb542bb65ae9947efa04f012138efcf92d9623024f211bef92a620ae180d",
"pubkey": "533e45ffeb94bc88c14af70b25994838170e7910c1273994b63bce468eac2230",
"created_at": 1686160078,
"kind": 1,
"tags": [
[
"e",
"ef5dde92725afdb85cf5de68b79bda90601206705e3d8da3230ef1a65f276d4a",
"",
"root"
],
[
"e",
"06862608fc88e6f868c29417c3bbccf1fad9daba26f80003e6f3f85ef27bbdc7",
"",
"reply"
],
[
"p",
"4760277fc06bd72dcdd8ef76810910d8852fb3f9d584f5b75a0bba7168ac81a0"
]
],
"content": "📅 Original date posted:2016-01-21\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nOn 2016/1/18 19:58, Ethan Heilman via bitcoin-dev wrote:\n\u003e I believe libsecp256k1 just performs Elliptic Curve operations \n\u003e required by Bitcoin. OpenSSL is used for all other crypto.\n\nThe exact answer, as I understand it, is a bit more nuanced. In\nparticular, you referenced the PRNG. I believe libsecp256k1, as\ncurrently written, relies on an implementation of RFC 6979 instead of\nusing a PRNG. I'm guessing this is done for portability reasons (no\nneed to hook into the OS's RNG).\n\nOtherwise, yes, I believe this answer is basically correct. There are\nstill some crypto functions not covered by libsecp256k1, at least at\nthe API level. But, for consensus-critical functionality, I think 0.12\nwill be rid of OpenSSL.\n\n- -- \n- ---\nDouglas Roark\nCryptocurrency, network security, travel, and art.\nhttps://onename.com/droark\njoroark at vt.edu\nPGP key ID: 26623924\n-----BEGIN PGP SIGNATURE-----\nComment: GPGTools - https://gpgtools.org\n\niQIcBAEBCgAGBQJWoEkTAAoJEEOBHRomYjkkoR0QAKmvgmoOdCw7SLP9cFURltXw\nRo8mOfikjp04C6tsshtiKQ1+jq80wBhioVYIL7XiyNU7ZUNdAWSc/wGBCG+YkMeQ\n6h02WJZQtTe0PvGVHIgUw6SiV4ZzXBuapXQX0BgEl0pInvQkRRqWtgrqDlWbqJVg\nNKzm8Kh+c8JUHEKbhnC45Jgh2JYHpyXcByLHSyGYsPOprjHmsupCPC6qydrRnuaO\nr7YHtObK2myOglJ1h6BXir//+XNbk6RiRNf5voONNAR9L+69BBV7hMVVO3eiDZ12\nvrNaOIKhDjhDs1kmkFYi7ML/zKBQRXlb7iM8AEpfCUKl/zK9bSNeblP4ZBGPqjCm\n9TGCqGjmKEbg7AYXjyMvmw+jZReediJMNYpCdxaSJi+XJZO6EC28pcKsb6pu/9gX\nNCLf1T/f2NoyXxc57aTuHNo0SnVaee1z0+IlGSh+5foxhZGbFmPhxOy3WNIubuou\ntm0guAXloCCERwVg0OhhQ3YyrlOWz7VnUrT8cteQC+yP353zdnxay7ZmQh9swcyR\nVX7yu4xLcxgbQmBIhMyKs9iQnycOrdNhZEfGx4vQ2ZKAj1CPVqrgKxbtY3KuPfvb\nYAzfs/iXaqBHH7FN9juLMRGqkzyVzJ9mIsFyLldADvSoc8RSa1IQiZtfPsIU1w1i\nUKEl9Qasje80EojNZNz0\n=glL2\n-----END PGP SIGNATURE-----",
"sig": "e8757e9212851b0a20f0888be1b13fa6fa565e7f3c9b308fead61049c63584b219fa4b59dc9d1592ae58928db74f8249dee335557ece68111fd256be8794e89b"
}