Keypair verifies

[michaeldjeffrey]

Adds a section to helium-config-service-cli env info
If a keypair is provided, it will sign and verify a message.

With an untouched keypair.

❯ helium-config-service-cli env info --keypair good.key
{
  "arguments": {
    // ...
    "key_type_from_keypair": "ed25519",
    "keypair": "good.key",
    "keypair_verifies_own_sig": "verified",
    "public_key_from_keypair": "13AixikqhmTeknAJYmi27iBs14gqS4kiCnZXge47jMCkSMeMKrs"
  },
  //...
}

With a keypair made, then opened in vscode and saved with no cursor movement.

❯ helium-config-service-cli env info --keypair bad.key 
{
  "arguments": {
    // ...
    "key_type_from_keypair": "ed25519",
    "keypair": "bad.key",
    "keypair_verifies_own_sig": "failed to verify: keypair corrupted: ed25519 error\n\nCaused by:\n    Invalid public key",
    "public_key_from_keypair": "14mLF4c2dZ3rxNeTMPm3Q4DYuZRJJcEC9vREHi7kWG4wiiQs6tj"
  },
  // ...
}

[jeffgrunewald]

i'm not sure what this is verifying. just that the keypair signing a message can verify the signature on the message? since all the code doing the signing and verifying is self-contained in this repo it seems a little circular to me that this performs a validation that provides any level of independent verification unless we're somehow seeing scenarios where folks are signing with invalid keys but then unable to verify with the same keypair. something with ecc_compact keys?

[michaeldjeffrey]

There's always a chance if you open a key file in a text editor that it's not left entirely alone.
The pubkey will be pulled out the same, but it can never sign anything.
This has happened to me a few times with test keys and vscode.
The config service doesn't give out much information about Auth errors, as it shouldn't, and a good first step is being able to verify the key can sign anything at all before starting a debug session through all the layers that can be causing problems.