📅 Original date posted:2014-03-02
📝 Original message:From BIP70:
If pki_type is "x509+sha256", then the Payment message is hashed using
the
SHA256 algorithm to produce the message digest that is signed. If
pki_type
is "x509+sha1", then the SHA1 algorithm is used.
A couple minor comments;
- I think it meant to say the field to be hashed is 'PaymentRequest' not
'Payment' message -- probably got renamed at some point and this is an old
reference calling it by its original name.
- Could be a bit more explicit about the hashing, e.g. 'copy the
PaymentRequest, set the signature field to the empty string, serialize to
a byte[] and hash.
- SHA1 is retiring, any particular reason to even have it in there at all?
- Should there any way for the end-user to see details like the pki_type
and the certificate chain, like browser do?
Thanks,
Jeremy
Jeremy Spilman [ARCHIVE] /
npub10e…jc727
2023-06-07 15:14:07
in reply to nevent1q…mm8k
Author Public Key
npub10etkvm8l0jr0jsgdx02dxnhnu5g989dnca90guj5rklwkaplnh3sgjc727Published at
2023-06-07 15:14:07Event JSON
{
"id": "47aaf7b969179d1229daaf4ba095e24624ca7d6107b92cebd9fa37d30ad1da36",
"pubkey": "7e57666cff7c86f9410d33d4d34ef3e5105395b3c74af472541dbeeb743f9de3",
"created_at": 1686150847,
"kind": 1,
"tags": [
[
"e",
"326b073faafb1dc7b240f45884d363e1128cddf34c4796140b14e99cd7a963c4",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2014-03-02\n📝 Original message:From BIP70:\n\n If pki_type is \"x509+sha256\", then the Payment message is hashed using \nthe\n SHA256 algorithm to produce the message digest that is signed. If \npki_type\n is \"x509+sha1\", then the SHA1 algorithm is used.\n\nA couple minor comments;\n\n - I think it meant to say the field to be hashed is 'PaymentRequest' not \n'Payment' message -- probably got renamed at some point and this is an old \nreference calling it by its original name.\n\n - Could be a bit more explicit about the hashing, e.g. 'copy the \nPaymentRequest, set the signature field to the empty string, serialize to \na byte[] and hash.\n\n - SHA1 is retiring, any particular reason to even have it in there at all?\n\n - Should there any way for the end-user to see details like the pki_type \nand the certificate chain, like browser do?\n\n\nThanks,\nJeremy",
"sig": "aa745a30c46a1887e52520e8dfb5948c9c84b7c2c48f6bad3feef88615f05a269aaaa15e0ac814abcd6a68a11cb0e057c389afe5d183f7fa86d9a419430ee03c"
}