📅 Original date posted:2013-11-03
📝 Original message:On Sat, Nov 02, 2013 at 02:14:22PM -0700, Johnathan Corgan wrote:
> On 11/01/2013 10:01 PM, bitcoingrant at gmx.com wrote:
>
> > Server provides a token for the client to sign.
>
> Anyone else concerned about signing an arbitrary string? Could be a
> hash of $EVIL_DOCUMENT, no? I'd want to XOR the string with my own
> randomly generated nonce, sign that, then pass the nonce and the
> signature back to the server for verification.
There were several replies like this, suggesting the client should
modify or add something to the token, or should give the token some
structure. But signing a token is not what the client should do in the
first place. At least not if the client's key is (EC)DSA. The standard
way is a challenge-response protocol in the form of the Diffie-Hellman
key exchange, which avoids producing any unintentional signatures.
Say the clients wants to prove he owns private key p, belonging to
public key P. P=p*G and G is the "base" of the (EC)DSA signature system.
The server generates a new keypair (a,A), a is private, A is public, and
sends A to the client as a challenge. The client computes and sends p*A
back. The server verifies whether p*A = a*P.
Only "public keys" are exchanged here, there's nothing that can be
mistaken for a (EC)DSA signature.
Timo
> --
> Johnathan Corgan, Corgan Labs
> SDR Training and Development Services
> http://corganlabs.com
> begin:vcard
> fn:Johnathan Corgan
> n:Corgan;Johnathan
> org:Corgan Enterprises LLC dba Corgan Labs
> adr:;;6081 Meridian Ave. Suite 70-111;San Jose;CA;95120;United States
> email;internet:johnathan at corganlabs.com
> title:Managing Partner
> tel;work:+1 408 463 6614
> x-mozilla-html:FALSE
> url:http://corganlabs.com
> version:2.1
> end:vcard
>
--
Timo Hanke
PGP 1EFF 69BC 6FB7 8744 14DB 631D 1BB5 D6E3 AB96 7DA8
Timo Hanke [ARCHIVE] /
npub1dd…pgp9a
2023-06-07 15:08:30
in reply to nevent1q…38ya
Author Public Key
npub1ddqaln8xsfmy6sxqplt9sz5ev99kh052sveqsh02q7hmc3a6n68shpgp9aPublished at
2023-06-07 15:08:30Event JSON
{
"id": "aba4bf9fdaa49eaad22cc8b1b1e83eaaabbb2f19db3a9afefb59625c62c721aa",
"pubkey": "6b41dfcce682764d40c00fd6580a99614b6bbe8a8332085dea07afbc47ba9e8f",
"created_at": 1686150510,
"kind": 1,
"tags": [
[
"e",
"724c6f13ca667850218ef24a7051f9062418fb5d7bd972070be69e4bf08accba",
"",
"root"
],
[
"e",
"7a7ef807f82f1559b6249c45f99ccc78811a10e2f37bdd1e1c5ed347e3e816af",
"",
"reply"
],
[
"p",
"3327325c47cd736ff7b6960a646e8e38456e62cb2aa3cee04ac2560680ca8a3c"
]
],
"content": "📅 Original date posted:2013-11-03\n📝 Original message:On Sat, Nov 02, 2013 at 02:14:22PM -0700, Johnathan Corgan wrote:\n\u003e On 11/01/2013 10:01 PM, bitcoingrant at gmx.com wrote:\n\u003e \n\u003e \u003e Server provides a token for the client to sign.\n\u003e \n\u003e Anyone else concerned about signing an arbitrary string? Could be a\n\u003e hash of $EVIL_DOCUMENT, no? I'd want to XOR the string with my own\n\u003e randomly generated nonce, sign that, then pass the nonce and the\n\u003e signature back to the server for verification.\n\nThere were several replies like this, suggesting the client should\nmodify or add something to the token, or should give the token some\nstructure. But signing a token is not what the client should do in the\nfirst place. At least not if the client's key is (EC)DSA. The standard\nway is a challenge-response protocol in the form of the Diffie-Hellman\nkey exchange, which avoids producing any unintentional signatures.\n\nSay the clients wants to prove he owns private key p, belonging to\npublic key P. P=p*G and G is the \"base\" of the (EC)DSA signature system.\nThe server generates a new keypair (a,A), a is private, A is public, and\nsends A to the client as a challenge. The client computes and sends p*A\nback. The server verifies whether p*A = a*P.\n\nOnly \"public keys\" are exchanged here, there's nothing that can be\nmistaken for a (EC)DSA signature.\n\nTimo\n\n\u003e -- \n\u003e Johnathan Corgan, Corgan Labs\n\u003e SDR Training and Development Services\n\u003e http://corganlabs.com\n\n\u003e begin:vcard\n\u003e fn:Johnathan Corgan\n\u003e n:Corgan;Johnathan\n\u003e org:Corgan Enterprises LLC dba Corgan Labs\n\u003e adr:;;6081 Meridian Ave. Suite 70-111;San Jose;CA;95120;United States\n\u003e email;internet:johnathan at corganlabs.com\n\u003e title:Managing Partner\n\u003e tel;work:+1 408 463 6614\n\u003e x-mozilla-html:FALSE\n\u003e url:http://corganlabs.com\n\u003e version:2.1\n\u003e end:vcard\n\u003e \n\n\n\n\n-- \nTimo Hanke\nPGP 1EFF 69BC 6FB7 8744 14DB 631D 1BB5 D6E3 AB96 7DA8",
"sig": "b4c6e7a34e9d212bc77d157122c1840bd333ac5dea6b9a3aefa487052334ddcd10c19033aca389dd5192888a2452403b4bcf1b6362f10cf96f21926ea2e6954c"
}