Hey,
ich habe da noch mal eine Frage:
Ich habe gerade mit "freebsd-update IDS" mein System kontrolliert und bekam als Ergebnis angezeigt, dass verschieden Verzeichnisse und Ordner falsche SHA265-Werte haben.
Muss ich mir Sorgen machen? Besteht Handlungsbedarf?
$ sudo freebsd-update IDS
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
/etc/group has SHA256 hash d77e0ebea13e4654f38b239e66b7cd169c09a6ab1f5f5a0216d2bb03aea281d6, but should have SHA256 hash 5fa1fbb2156e689928671fdf44bd9229a9a3e97ffc35c83b059527143490e256.
/etc/hosts has SHA256 hash 941aa7d9c7a80e2243594d9a5d957498fd1a0390c8f489924e4e57812c3507e9, but should have SHA256 hash 10c5d5e434664d5b9370e1e41836e219be91219b801130c2abf90b110059c682.
/etc/master.passwd has SHA256 hash a95cd1eb8d3f7b8db38a3dec549c76767e4290a1d304337be44f562d44605f93, but should have SHA256 hash ce34dd16a4945a9470519b9f0fe552d05a29222d62b9469d486c23c8850dc44c.
/etc/motd has SHA256 hash 42121d5822570627b6ace007eaf92ae42fa341f91fb69702491021bee8743dbf, but should have SHA256 hash c76d9a02e764e77686f9bf4a9192311b6a0387a088cc414dd312ef6ba069ad7e.
/etc/ntp.conf has SHA256 hash 45a65434e0968f12ba58b74792344e4caf3f83c9c921b33a6aed3b0e673e2a4d, but should have SHA256 hash 58543db1da0f10ac6ac45686ab7b27426ffa268eb996b8bfddb424f1fcdd417c.
/etc/passwd has SHA256 hash 7b70c7da24824f2922665ae453f7a1505d95f7aecb36ebaf8688ceca48f70f06, but should have SHA256 hash ef23388b5c3538a4c21a7f2138175a47eb3a5571971e2b4bb4e7215667bef7c8.
/etc/pwd.db has SHA256 hash e14ab6af95666dd50f57808c44fffa6ef69615dce39a5ead1167e70d6b3b0e7c, but should have SHA256 hash 1b481658b7b6aa8126fef82f745a37e3b6e896d247364eb797e2cb434f370354.
/etc/shells has SHA256 hash 7f069b1cd5623907c65acbbd02ed5403855a9760fa6049c0b4407157db980c08, but should have SHA256 hash 824549f1144679e07f258afb95c1632d56a198717da20ae76a80dfc30ce80e75.
/etc/spwd.db has SHA256 hash ef857cc19bd5a8a2aee5b309768720f0d8abbef8f40cd79c830893f03e9a33fe, but should have SHA256 hash 5f4a19eafc5edd3a903a32c835cb3f71181f3e89c9bf2fbbf7ecc14fae69cf5b.
/etc/ssh is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/moduli is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/ssh_config is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/sshd_config is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/sshd_config has SHA256 hash dbff44bb85e8b7e2f18545092821c157ed49b198c101c852b22d8fb9b0825dff, but should have SHA256 hash 26748c51687fe4f09ac6c8ace864d0c545f1fc0aa059bb9bffd80f80c0d62d85.
/etc/ssl/openssl.cnf has SHA256 hash 70dba331fcecf33b472d57403092874ac41e0299d5567d61b828de18409c273b, but should have SHA256 hash c15a0c40e33dc38fb8f17b136ae41c9a2512c06044d327363333440cb5ee1773.
ich habe da noch mal eine Frage:
Ich habe gerade mit "freebsd-update IDS" mein System kontrolliert und bekam als Ergebnis angezeigt, dass verschieden Verzeichnisse und Ordner falsche SHA265-Werte haben.
Muss ich mir Sorgen machen? Besteht Handlungsbedarf?
$ sudo freebsd-update IDS
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
/etc/group has SHA256 hash d77e0ebea13e4654f38b239e66b7cd169c09a6ab1f5f5a0216d2bb03aea281d6, but should have SHA256 hash 5fa1fbb2156e689928671fdf44bd9229a9a3e97ffc35c83b059527143490e256.
/etc/hosts has SHA256 hash 941aa7d9c7a80e2243594d9a5d957498fd1a0390c8f489924e4e57812c3507e9, but should have SHA256 hash 10c5d5e434664d5b9370e1e41836e219be91219b801130c2abf90b110059c682.
/etc/master.passwd has SHA256 hash a95cd1eb8d3f7b8db38a3dec549c76767e4290a1d304337be44f562d44605f93, but should have SHA256 hash ce34dd16a4945a9470519b9f0fe552d05a29222d62b9469d486c23c8850dc44c.
/etc/motd has SHA256 hash 42121d5822570627b6ace007eaf92ae42fa341f91fb69702491021bee8743dbf, but should have SHA256 hash c76d9a02e764e77686f9bf4a9192311b6a0387a088cc414dd312ef6ba069ad7e.
/etc/ntp.conf has SHA256 hash 45a65434e0968f12ba58b74792344e4caf3f83c9c921b33a6aed3b0e673e2a4d, but should have SHA256 hash 58543db1da0f10ac6ac45686ab7b27426ffa268eb996b8bfddb424f1fcdd417c.
/etc/passwd has SHA256 hash 7b70c7da24824f2922665ae453f7a1505d95f7aecb36ebaf8688ceca48f70f06, but should have SHA256 hash ef23388b5c3538a4c21a7f2138175a47eb3a5571971e2b4bb4e7215667bef7c8.
/etc/pwd.db has SHA256 hash e14ab6af95666dd50f57808c44fffa6ef69615dce39a5ead1167e70d6b3b0e7c, but should have SHA256 hash 1b481658b7b6aa8126fef82f745a37e3b6e896d247364eb797e2cb434f370354.
/etc/shells has SHA256 hash 7f069b1cd5623907c65acbbd02ed5403855a9760fa6049c0b4407157db980c08, but should have SHA256 hash 824549f1144679e07f258afb95c1632d56a198717da20ae76a80dfc30ce80e75.
/etc/spwd.db has SHA256 hash ef857cc19bd5a8a2aee5b309768720f0d8abbef8f40cd79c830893f03e9a33fe, but should have SHA256 hash 5f4a19eafc5edd3a903a32c835cb3f71181f3e89c9bf2fbbf7ecc14fae69cf5b.
/etc/ssh is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/moduli is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/ssh_config is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/sshd_config is owned by user id 1001, but should be owned by user id 0.
/etc/ssh/sshd_config has SHA256 hash dbff44bb85e8b7e2f18545092821c157ed49b198c101c852b22d8fb9b0825dff, but should have SHA256 hash 26748c51687fe4f09ac6c8ace864d0c545f1fc0aa059bb9bffd80f80c0d62d85.
/etc/ssl/openssl.cnf has SHA256 hash 70dba331fcecf33b472d57403092874ac41e0299d5567d61b828de18409c273b, but should have SHA256 hash c15a0c40e33dc38fb8f17b136ae41c9a2512c06044d327363333440cb5ee1773.
