ssh host key fingerprints

Date: Wed, 3 Jun 2020 18:15:23 -0300
From: Kenny Lewis <ai369@chebucto.ns.ca>
To: userhelp@chebucto.ns.ca
User-Agent: Mutt/1.12.2 (2019-09-21)
Precedence: bulk
Return-Path: <userhelp-mml-owner@chebucto.ns.ca>
Original-Recipient: rfc822;"| (cd /csuite/info/lists/userhelp; /csuite/lib/arch2html)"

next message in archive
no next message in thread
previous message in archive
Index of Subjects

Hello Chebucto!

With smtp.chebucto.ns.ca's certificate expiring on the
weekend I was reminded to bug you that I can't find
Chebucto's ssh key fingerprints anywhere on your web site.
If they are posted somewhere, could you point me in the
right direction?

If not, would it be possible to have those posted somewhere
so people could confirm the host they are connecting to?

----

On a side note with ssh, when I tried to connect this
weekend my machines refused with:

    Unable to negotiate with 192.75.95.75 port 22: no
    matching key exchange method found. Their offer:
        diffie-hellman-group-exchange-sha1,
        diffie-hellman-group1-sha1

I guess they are following:

    https://tools.ietf.org/id/draft-ietf-curdle-ssh-kex-sha2-09.html

and considering them insecure.

I can always (and have to see the fingerprint presented and
not find it in any of my backed up .ssh/known_hosts files)
use the ssh KexAlgorithms option so this is just a side
issue I felt I should mention.

Again, I just thought I would mention this. If you have a
chance and it's not too much trouble the ssh key
fingerprints seems like the main thing.

Thanks for all your good work! 

Kenny

next message in archive
no next message in thread
previous message in archive
Index of Subjects