I'm very proud that we implemented server-side support for the keystroke timing obfuscation mechanism in golang.org/x/crypto/ssh already.<p>(I just clicked the Submit button! <a href="https://go.dev/cl/524775" rel="nofollow noreferrer">https://go.dev/cl/524775</a>)<p>It's a small change, but it's a signal that we're much more on top of x/crypto/ssh maintenance, compared to a year ago when we had to scramble to implement rsa-sha2-256/512 support just hours before GitHub (rightfully) dropped SHA-1 support, potentially breaking every x/crypto/ssh client.<p>The main reason is that thanks to the funding of my clients (<a href="https://words.filippo.io/full-time-maintainer/" rel="nofollow noreferrer">https://words.filippo.io/full-time-maintainer/</a>) I was able to hire Nicola Murino, the maintainer of SFTPGo, to pick up maintenance of x/crypto/ssh. This is benefiting both my clients and the whole ecosystem, and is a little step in growing the professional maintainer model.