ssh-signing: include key in verification result

[Defelo]

Checklist

If applicable:

• I have updated CHANGELOG.md
• I have updated the documentation (README.md, docs/, demos/)
• I have updated the config schema (cli/src/config-schema.json)
• I have added/updated tests to cover my changes

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[yuja]

I'm not pretty sure if the output format is stable, but the change looks good.

@julienvincent can you take another look?

[Defelo]

Hey @yuja, thanks for the review! Regarding the output format stability, perhaps a better approach could be to use the ssh_key crate to parse the signature and extract the public key directly (see ssh_key::SshSig) instead of trying to parse the ssh-keygen output. Please let me know what you think.

[yuja]

Regarding the output format stability, perhaps a better approach could be to use the ssh_key crate to parse the signature and extract the public key directly (see ssh_key::SshSig) instead of trying to parse the ssh-keygen output. Please let me know what you think.

I don't have expertise, but I think it's better for us to rely on a single backend program or library.

[Defelo]

@yuja Is there anything I can do to get this merged? I have already been invited to the contributors team, so according to the contributing guide I should be able to merge this myself now, however since you explicitly asked julienvincent to take another look in your approval two weeks ago, I thought I better ask first.

[yuja]

No. Feel free to merge the approved change if you addressed all review comments.