Bug 11901 - SSH host key on monitoring01.i.ipfire.org has changed
Summary: SSH host key on monitoring01.i.ipfire.org has changed
Status: CLOSED DEFERRED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Monitoring (show other bugs)
Version: unspecified
Hardware: all All
: - Unknown - Security
Assignee: Michael Tremer
QA Contact: Peter Müller
URL:
Keywords: 5MinuteJob, Security
Depends on:
Blocks:
 
Reported: 2018-10-11 19:28 UTC by Peter Müller
Modified: 2019-10-28 15:05 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2018-10-11 19:28:51 UTC 
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:1ozPjekp6zFA1v0G/6huI7ITb8yRPZ7SOIDQOEj+gaM.
Please contact your system administrator.
Update the SSHFP RR in DNS with the new host key to get rid of this message.
The authenticity of host 'monitoring01.i.ipfire.org (192.168.9.28)' can't be established.
ED25519 key fingerprint is SHA256:1ozPjekp6zFA1v0G/6huI7ITb8yRPZ7SOIDQOEj+gaM.
+--[ED25519 256]--+
|                 |
| .     . .       |
|o..o  o . o      |
|.++..o   + +     |
|. oo... Soo +    |
|E  .. ooooo= o   |
|       *o==oo .  |
|      o @+*o     |
|      .*oO=.     |
+----[SHA256]-----+
No matching host key fingerprint found in DNS.
Are you sure you want to continue connecting (yes/no)? ^C
Comment 1 Michael Tremer 2018-10-11 19:33:17 UTC 
What are you trying to say?
Comment 2 Peter Müller 2018-10-11 19:46:41 UTC 
That the SSH server host key on monitoring01.i.ipfire.org
has changed (and the change is not applied to its SSHFP records
as well) and I cannot determine whether this is legitimate or not.
Comment 3 Michael Tremer 2018-10-11 20:10:49 UTC 
For me the key hasn't changed and SSHFP records are up to date
Comment 4 Peter Müller 2018-10-15 18:35:45 UTC 
SSHFP record for ED25519 is missing in DNS.
Comment 5 Peter Müller 2019-10-28 15:05:30 UTC 
I guess this became obsolete by now...