-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
md5 mismatch Fail0verflow Fedora 23, just noticed, upgrading to F28 ? #2
Comments
also here |
and maybe here S.5....T. c /etc/printcap |
full rpm -Va rpm -Va (key) rpm -Va Code |
[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, [root@localhost /]# chroot /mnt/28 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... |
no this is in the binary directly, |
@masterzorag https://github.com/c4pt00/f28-PS4-linux-Fedora-4.14-KVM http://www.psdevwiki.com/ps4/Template:Kernel_hardening,_general_installation,_rpm_building |
@masterzorag |
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
The text was updated successfully, but these errors were encountered: