md5 mismatch Fail0verflow Fedora 23, just noticed, upgrading to F28 ?
opened this issue · comments
noticed this mismatch in a md5 checksum on Fail0verflow's packaged user "D-Decks"?
Fedora 23 for the PS4
using rpm -Va
used "dd clone" to clone PS4Linux_0.1.1.img to the thumb drive for PS4 Fedora 23,
noticed this, I dont usually check md5s, decided I would, someone else told me that md5s changed
based on text files or source code which makes sense,
not sure why a binary would change md5s unless this particular binary was patched a certain way
to enable functionality on the PS4 with Fedora 23
S.5...... /usr/bin/nm-connection-editor
S.5...... /usr/bin/firewall-offline-cmd
S.5...... /usr/bin/firewall-cmd
S.5...... /usr/sbin/firewalld
trying to update to Fedora 28
also here
S.5...... /usr/share/bash-completion/completions/firewall-cmd
and maybe here
..5....T. /var/lib/selinux/targeted/active/commit_num
S.5....T. c /etc/printcap
full rpm -Va
https://0bin.net/paste/YY7BPkvQXNRq1PMV#g25X7btKVK7gP4M8xjDlOBB3ETfnwurXjY6Ubb488fe
rpm -Va (key)
rpm -Va
Code
Meaning
S
File size differs.
M
File mode differs.
5
The MD5 checksum differs.
D
The major and minor version numbers differ on a device file.
L
A mismatch occurs in a link.
U
The file ownership differs.
G
The file group owner differs.
T
The file time (mtime) differs.
[MIRROR] xorg-x11-drv-ati-18.0.1-1.fc28.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 2dbc768fbd33c4b3d08c7fa785236087c4b8ed6c2c9137af81b8ed4aae7682f7(sha256) Expected: f4b751ad63674ec4caae179bee6497cc5c72c9ce3d8e72a28e2208038c579faf(sha256)
?
in comparison a fedora 28 netinstall,
running
rpm -Va
[root@localhost /]# chroot /mnt/28
[root@localhost /]# rpm -Va
missing /run/netreport
missing /var/run/vpnc
.M....... c /etc/audit/rules.d/audit.rules
.M....... /var/log/audit
missing /run/screen
missing /var/run/xl2tpd
S.5....T. c /var/lib/unbound/root.key
missing /var/run/pluto
missing /run/httpd
missing /run/httpd/htcacheclean
missing /usr/lib/systemd/system-preset/85-display-manager.preset
.M....... g /usr/lib/variant
.M....... g /var/lib/dnf
.M....... g /var/lib/dnf/groups.json
.M....... g /var/lib/dnf/history
.M....... g /var/lib/dnf/yumdb
.M....... g /var/log/dnf.librepo.log
.M....... g /var/log/dnf.rpm.log
.M....... g /var/log/hawkey.log
.M....... c /etc/machine-id
missing c /etc/systemd/system/dbus-org.freedesktop.network1.service
missing c /etc/systemd/system/dbus-org.freedesktop.resolve1.service
.M....... g /var/log/btmp
.M....G.. g /var/log/journal
.M....... g /etc/pki/ca-trust/extracted/java/cacerts
.M....... g /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
.M....... g /etc/pki/ca-trust/extracted/pem/email-ca-bundle.pem
.M....... g /etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem
.M....... g /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
.M....... g /boot/System.map-4.16.16-300.fc28.x86_64
.M....... g /boot/initramfs-4.16.16-300.fc28.x86_64.img
missing /var/run/plymouth
.M....... g /var/cache/dnf/packages.db
missing /var/run/BackupPC
missing /var/run/console
missing /var/run/faillock
missing /var/run/sepermit
missing /run/openvpn-client
missing /run/openvpn-server
.M....... d /usr/share/info/dir.old
.M....G.. g /var/log/lastlog
.M....... g /etc/udev/hwdb.bin
.M....... g /var/lib/systemd/random-seed
.M....G.. g /var/log/lastlog
[root@localhost /]# ps ax | grep firewalld
3087 ? Ssl 0:01 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid
28060 ? S+ 0:00 grep --color=auto firewalld
https://0bin.net/paste/p6KlY3k55I101ZKH#7ENGEV7RxRrq6nJav9zrIHOfhCnPetK+wEqcghzV7pK
For what I can see, all /var/log, /run, /var/run etc can be just updated config/log files by your first boot on different machine...
Seems harmless
no this is in the binary directly,
config files change from time to time, sometimes logs change due to different changes or modifications in the system, so each time a conf or text file changes the md5 changes,
binaries don't change unless directly updated, even then it has a stamped md5 to verify it,
@masterzorag
do you have Fedora 28 running on the PS4?
I was trying to experiment earlier with a custom PS4 kernel, with some different options,
you can see the files here
https://drive.google.com/drive/u/0/folders/1L2oykE70DgQqHPf0F-6-NSgiTkOhCZfP
I have a problem loading initramfs.cpio.gz even after repacking it the initramfs.img generated from the kernel install, unless its a slight misconfiguration in the make menuconfig, a conflict in an option, I will attempt to rebuild another kernel maybe in the next few days or so,
https://github.com/c4pt00/f28-PS4-linux-Fedora-4.14-KVM
http://www.psdevwiki.com/ps4/Template:Kernel_hardening,_general_installation,_rpm_building
@masterzorag
how did you rebase these RPMs for the Xorg , mesa and ATI/AMD patches?