I enabled a slightly more secure version of hmac-sha1, guess that didn't work.
It wasn't until this morning that I learned from a friend that there is a subtle distinction between EtM and non-EtM SHA1.
Try again, I've set sshd to allow the original hmac-sha1 now.
Thank you. I will try that as soon as a new issue is resolved. In my frustration to make a successful connection to SH this morning, I tried using v0.70 of PuTTY. Wow, PuTTY needs some help. In any case, not able to see what I was typing, evidently I typed the password wrong, twice. Before I could enter the password a third time, the connection dropped. I tried to connect again, but PuTTY displayed and continues to display the following error dialog:
PuTTY fatal error: "Software caused connection abort"
The PuTTY doc says this is not the fault of PuTTY. So I tried SecureCRT and now SecureCRT is almost immediately displaying "Connection closed". Logged into Bolt with SecureCRT and I can successfully connect to SH from Bolt. I don't know if I have accidentally banned myself using PuTTY or the server is refusing outside connections or what. :(