-
Notifications
You must be signed in to change notification settings - Fork 103
Conversation
Here's a preview of the new visibility this will offer to folks..
|
I like the new structure along with all the information it provides to me 👍 But I'm a bit confused about the fingerprint encoding. The SHA-256 hash is the only one in base64. I would go with consistency and print the SHA-256 hash also in hex (or the other two also in base64 instead; not important for me but consistency would be great). |
@exploide I'm using sshkey library to do all this work, I'm not exactly sure about the reasoning for the base64 encoding, but it seems to be the default there. I could of course provided multiple formats for the sha256 as usually more information is less harmful and less information. If you look at their readme, you'll see it in the fingerprint section here: |
Ok, if it is the default there, it's probably reasonable do follow their scheme. |
I think I'm just going to release 0.0.39 today with this included, so people can start playing around with it and find any new bugs I introduced. It will likely break some expectations if people are surfing the JSON to get the details, but hopefully they will be more happy about the added clarity. |
Great, I will try it :) What I expect instead of bugs is that people become confused when they only see an RSA key enumerated but the server actually also offers ECDSA and ED25519. But that's maybe an other issue. |
I think that issue has been present for a while, I consider it a feature add rather than a bug. |
This attempts to refactor the key handling (formerly fingerprints only) to make it more useful per recent feedback on #476. It's not quite done, and I had to break a few things to get it to work, but it does work at least on the bench. Needs a few more tweaks and should be ready for a pre-release to try out.