📅 Original date posted:2013-04-14
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/14/2013 02:25 AM, Peter Todd wrote:
> On Sun, Apr 14, 2013 at 01:21:21AM -0400, Alan Reiner wrote:
>> If we're going to extend/expand message signing, can we please add a
>> proper ASCII-armored format for it? Really, anything that encodes the
>> signed message next to the signature, so that there's no ambiguities
>> about what was signed. You can keep the "bare signatures" as an option
>> for backwards compatiblity, but offer this as the primary one.
>>
>> What we really want is to have the user copy an ASCII-armored block of
>> text into the client (or we could have a URI-extension for this), and
>> the app pops up with a window that says "The following message has a
>> valid signature from address 1XKjf32kJbf...: <message>".
>
> I already looked into ASCII-armoring PGP style for a different project.
> (timestamping) Basically you'd want to follow RFC2440, section 7
> "Cleartext signature framework":
>
> -----BEGIN BTC SIGNED MESSAGE-----
>
> Hello world!
> -----BEGIN BTC SIGNATURE-----
> IKBeCbxXHvD1TJh8ZlMySo26w5z6YZQD1xqKgbhsvlhEgcFD+kvKx4LzUz1yxg/8
> IdYdBnzez77VDq3odHrVftg=
> -----END BTC SIGNATURE-----
>
> Pretty simple really and doesn't need to be done prior to other
> signmessage changes. There may be an issue passing \r's through the RPC
> interface; the RFC specifies CRLF line endings.
>
Perfect. That was the spec I was looking for but too lazy to find it.
I guess I'll lead by example and just do it in Armory. I'll let users
pressure the other devs to follow :)
- -Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlFq9GIACgkQYdHIW5RKKv1A2gCeMfdttPylmPqPqemo0Q2uACEt
eAcAn21a7sYy+TNIinRR3SlVgm4VbJPh
=qGlo
-----END PGP SIGNATURE-----
Alan Reiner [ARCHIVE] /
npub1sm…mnq7h
2023-06-07 11:46:33
in reply to nevent1q…g88n
Author Public Key
npub1sm6zhjmk5scuz294jmpkw99wwwjzetjgwp4fu4gn6utqgdz87hkqamnq7hPublished at
2023-06-07 11:46:33Event JSON
{
"id": "8247ffc9a2f35bfac19123e6710e21f88224bf4e3a53607373c440abf6953e85",
"pubkey": "86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec",
"created_at": 1686138393,
"kind": 1,
"tags": [
[
"e",
"9720ad9bd7e43696cd6d2555906617a4ea649c8903d6d52e997b38fa8148ba1b",
"",
"root"
],
[
"e",
"0f5e953eba6baaa032fbec4d72ba4a8f74b7eb051d12f7d64be5dd66aed22e2d",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2013-04-14\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nOn 04/14/2013 02:25 AM, Peter Todd wrote:\n\u003e On Sun, Apr 14, 2013 at 01:21:21AM -0400, Alan Reiner wrote:\n\u003e\u003e If we're going to extend/expand message signing, can we please add a\n\u003e\u003e proper ASCII-armored format for it? Really, anything that encodes the\n\u003e\u003e signed message next to the signature, so that there's no ambiguities\n\u003e\u003e about what was signed. You can keep the \"bare signatures\" as an option\n\u003e\u003e for backwards compatiblity, but offer this as the primary one.\n\u003e\u003e\n\u003e\u003e What we really want is to have the user copy an ASCII-armored block of\n\u003e\u003e text into the client (or we could have a URI-extension for this), and\n\u003e\u003e the app pops up with a window that says \"The following message has a\n\u003e\u003e valid signature from address 1XKjf32kJbf...: \u003cmessage\u003e\". \n\u003e\n\u003e I already looked into ASCII-armoring PGP style for a different project.\n\u003e (timestamping) Basically you'd want to follow RFC2440, section 7\n\u003e \"Cleartext signature framework\":\n\u003e\n\u003e -----BEGIN BTC SIGNED MESSAGE-----\n\u003e\n\u003e Hello world!\n\u003e -----BEGIN BTC SIGNATURE-----\n\u003e IKBeCbxXHvD1TJh8ZlMySo26w5z6YZQD1xqKgbhsvlhEgcFD+kvKx4LzUz1yxg/8\n\u003e IdYdBnzez77VDq3odHrVftg=\n\u003e -----END BTC SIGNATURE-----\n\u003e\n\u003e Pretty simple really and doesn't need to be done prior to other\n\u003e signmessage changes. There may be an issue passing \\r's through the RPC\n\u003e interface; the RFC specifies CRLF line endings.\n\u003e\nPerfect. That was the spec I was looking for but too lazy to find it. \nI guess I'll lead by example and just do it in Armory. I'll let users\npressure the other devs to follow :)\n\n- -Alan\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.11 (GNU/Linux)\nComment: Using GnuPG with Thunderbird - http://www.enigmail.net/\n\niEYEARECAAYFAlFq9GIACgkQYdHIW5RKKv1A2gCeMfdttPylmPqPqemo0Q2uACEt\neAcAn21a7sYy+TNIinRR3SlVgm4VbJPh\n=qGlo\n-----END PGP SIGNATURE-----",
"sig": "05950961a745f40004bed0244380336d02d4ccd6e260c21ca47d3f4e5252566efe71f7d31760a7c719bf0ff55c4292546fc6a45613b6afd7656b221c6d3b5463"
}