Closed
Description
Currently SSH.NET only supports MD5, with the big-ish struggles right not being that FingerPrint
being just a bite array, so something we can't easily add new algorithm support to.
We're currently calculating our own fingerprint for SHA256 support, but ideally having the library support this out of the box would be best.
To prevent breaking backwards comparability we can:
- Make additional properties per algorithm (not the best, easy though, accessible, matches current "convention")
- Make a new property that allows us to look up by algorithm, all algorithms need to be checked up-front and stored, but we can add more
- Make a method that takes an algorithm that we'll return the thumbprint for, internal implementation may cache this
What probably makes the most sense? Or does everyone just roll their own and it's not really a big deal?