0

Up to now, I have been using putty + pageant 0.66 to ssh from my Win 10 client to a couple of Linux servers, as in

   Comp A                         Comp B                    Comp C
Win 10, Msys2   ----------->   Ubuntu 18.04   ----------->   RHEL6
     |             Warning                     No warning      ^
     |                                                         |
     |---------------------------------------------------------|
                             No warning

As described here, I was getting a warning about using SHA-1 when connecting A to B.

To fix this, I started using putty + pageant 0.73. Now each ssh authentication from A to B takes about 27s. Before, it was immediate. This is usually not a serious issue. But once in a while it may become a significant inconvenience.

When authenticating from A to C, connection is still immediate.

I wonder whether this is expected, and if it can be mended some way.

Improve this question
3
  • Are you talking about connection from A to B, or about connections from B to C?
    – grawity_u1686
    Commented Apr 16, 2020 at 12:01
  • @user1686 - Good question... please see updated OP.
    – sancho.s ReinstateMonicaCellio
    Commented Apr 16, 2020 at 12:08
  • Your issue here, and on StackOverflow, appears to arise from using an insecure SHA1 based key, as no SSH server should currently support SHA1 because it's a security risk.
    – JW0914
    Commented Apr 16, 2020 at 14:15

1 Answer 1

Reset to default
0

Answering my own question... All processors were busy at 100% performing calculations by other users in server B. I tested SSHing to a couple of other servers and it worked immediately.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .