moin,
beim login auf den srv01 passierte heute
# ssh srv01
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 RSA key sent by the remote host is
SHA256:LX0xpviTs3pSYWtibqspcjoqDDxrkzA1kw0F+4ZmXps.
Please contact your system administrator.
was ist hier los?
The authenticity of host 'srv01.ffnw.de (37.120.176.207)' can't be
established.
RSA key fingerprint is SHA256:LX0xpviTs3pSYWtibqspcjoqDDxrkzA1kw0F+4ZmXps.
RSA key fingerprint is MD5:97:7f:f3:b0:7f:57:04:d1:96:15:7f:eb:bc:de:17:6e.
es macht sinn das man weiss das man sich auf den richtigen srv verbindet,
wieso hat sich was am key geändert?
wo stehen die fingerprints zum vergleichen?
--
Freifunk Gruß
pic
Www: https://fr32k.de
Xmpp: picard(a)fr32k.de & picard(a)ffnw.de
Keybase: https://keybase.io/picard
--
Gruß
pic
Xmpp: picard(a)ffnw.de & picard(a)fr32k.de
@ME https://wiki.nordwest.freifunk.net/picard
Moin,
können wir den Resolver mal in eine normale VM stecken?
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Watchdog timeout
(limit 10s)!
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Killing process
1186457 (kresd) with signal SIGABRT.
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Main process
exited, code=killed, status=6/ABRT
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Failed with result
'watchdog'.
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Consumed 3.361s
CPU time.
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Service
RestartSec=100ms expired, scheduling restart.
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Scheduled restart
job, restart counter is at 1709.
Nov 10 11:00:26 resolv01 systemd[1]: Stopped Knot Resolver daemon.
Nov 10 11:00:26 resolv01 systemd[1]: kresd(a)1.service: Consumed 3.361s
CPU time.
Nov 10 11:00:26 resolv01 systemd[1]: Starting Knot Resolver daemon...
Nov 10 11:00:26 resolv01 systemd[1]: Started Knot Resolver daemon.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Watchdog timeout
(limit 10s)!
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Killing process
1186469 (kresd) with signal SIGABRT.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Main process
exited, code=killed, status=6/ABRT
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Failed with result
'watchdog'.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Consumed 3.378s
CPU time.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Service
RestartSec=100ms expired, scheduling restart.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Scheduled restart
job, restart counter is at 1710.
Nov 10 11:00:49 resolv01 systemd[1]: Stopped Knot Resolver daemon.
Nov 10 11:00:49 resolv01 systemd[1]: kresd(a)1.service: Consumed 3.378s
CPU time.
Nov 10 11:00:49 resolv01 systemd[1]: Starting Knot Resolver daemon...
Nov 10 11:00:49 resolv01 systemd[1]: Started Knot Resolver daemon.
Das ist doch nicht normal. Ich nutze selbst kresd und der hat nie solche
Probleme.
VG
bjo
