Email and Cyber Security · #72

Online SSH Public Key Fingerprint and Inventory

Decodes SSH public keys in the browser and produces the same SHA256 fingerprint as ssh-keygen -lf.

  • Data is processed in your browser and not sent to a server
  • Export: CSV

Tool

One key per line. Do not paste private keys.

What does this tool do?

authorized_keys files on servers accumulate traces of former staff, old automation and copied keys. Knowing who accesses with which key requires each key's type, length and fingerprint. The tool decodes the lines, flags weak (DSA, RSA below 2048 bits) and duplicate keys and exports the inventory as CSV.

How to use it

  1. Paste the content of ~/.ssh/authorized_keys or .pub files; options (from=, command=) are supported.
  2. Press Run; download the inventory as CSV.

Fields

Public keys
One key per line. Do not paste private keys.

Worked example

InputValue
Public keys
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICOnYLw2t0DtxiGqz2BdwPvBu2tYCdjnlZUIpWEJEO3D ayse@laptop
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCkTYDb39ypX/ICIbfw//1s6IfBGb+yYDvf2W65blHDU6DCVJDsbeDKakQEy2qsYETGYE5R9IrRQT+poBHKnl5cyykpu695Zbcehp3JJGcMX6deQUfcKONXqmMQlrXei9TT1kVpALhWR3H2GJEM8klhWvY+4wqw1oi4W6ctKTQXjx3TboUlR+H43H0VhqzuKmmrRsVddA8ixYbGYEs9M/5AQ7jJizPWNR7w4UkbNy/w3xNMyJY/QW6jvlNmPJ/Ok7NvO5Uq8y5qMyF5YGir/XFmjL1BesPTfeh3Gk6y7bo9IJH4ow++kmZLJm49jPEToKuGv16uMTrOcF4P81/WYv7it8BhKhGgwwDw2mPupTocBwOWgVqMA62jcONHm7sLszE3mTMsEt+I4OdXycBOChki1xkk3C6i6rWFwxM58blnuYcDI9eUjqRaFG7d2c4Hu62InCEQfM3LcdALfCU57pxMvu9Nzn84Kyn1hKkaxbfLRkVpwTNoqZyi9aI0S7gEhQs= backup@srv01
from="10.0.0.0/8",no-port-forwarding ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDIXXzqvt4fuG3XypWENtpztebPzOean7SeQmaix+3DMtvs7BvrKTwAyNKULupbMNYjmVH9s4n3POAlFWwmQ1iXNE35aMWfviBseTlQQfmTGNC35bQZ0ZmE+nFiWJHDrakaQonRIwerNIBw3bb9OvMk1k8sG7D7334AxXvlzSex+OZc0NlbRAKvivxMT59ASZ4fyIruPZawTEVoTdSeL2sYBDx0fWFHe/D7ycCT9lTU3cs0k+jxuh4lcdupwqCkcql4uIa0PjhYuN6Lp5Wa8EbbuNziBHLs+n99phbkeJiNV7yZeOcrPNnEMejgK5/Cy5omCRagXNXUZujBF3Q8sKML deploy@ci
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDIvSy51qsD45veHE/9MDHnnFrfsOIXnY0ocxUSIKOg8WwqW9FvabYHBJpTVzRsgbuBFW0S3C3buo7SBtcUvCQM4pwOmdOtbK3Ok5Xzi9iK1T2GCmDjuFM+jv8MaY+dWB/7kn92EVylvAwGNK57+5a+/2Syb0BdkJI4GFDtqz/dCw==

Expected result: 4 keys: ayse@laptop ed25519; backup@srv01 RSA 3072; deploy@ci RSA 2048 (restricted with from=); an uncommented RSA 1024 key in red.

If the owner of the uncommented 1024-bit key cannot be identified, remove it. The RSA 2048 key is acceptable for now, but move to ed25519 at renewal. Compare fingerprints with ssh-keygen -lf authorized_keys on the server.

Second scenario

InputValue
Public keys
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICOnYLw2t0DtxiGqz2BdwPvBu2tYCdjnlZUIpWEJEO3D ayse@laptop
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICOnYLw2t0DtxiGqz2BdwPvBu2tYCdjnlZUIpWEJEO3D ayse@desktop

Expected result: The same ed25519 key was added twice with two different comments: duplicate warning.

Method and assumptions

The key type and Base64 blob are read; the type name inside the blob must match the line. RSA length comes from the modulus (n), ECDSA from the curve, ed25519 is a fixed 256 bits.

Fingerprint: SHA256: + Base64(SHA-256(blob)) without padding (OpenSSH format).

Using the result and troubleshooting

Remove unknown and weak keys, add from= and command= restrictions for service accounts. Tie the inventory to your leaver process.

Limits and common mistakes

  • Legacy MD5 fingerprints are not calculated. Signature and validity of certificate key types (-cert-v01) are not decoded.

Frequently asked questions

Why is the fingerprint the same as ssh-keygen?

Both use the same definition: SHA-256 of the key blob, unpadded Base64. If they differ, the line was probably damaged when copying.

Related tools and service

Related service: Privileged Access Management

Cybersecurity online tools · See all online tools