>SHA256 hashes are different
SHA256 hashes are different
SHA256 hashes are different?
Luckily you checked before installing.
>tfw I never check SHA256 hashes and install anyway
... would you care to elaborate, based retard?
Think about it logically, even if they're the same there's still a possibility of collision, so you're never safe anyway.
No one has ever been able to intentionally produce a colision
it's matematically proven with all computers in the world it would take centuries
>not being an ignorant tool who is too stupid to worry about this (like me or him )
Wrong.
It is all probability. There is a chance that your executable will have hash which is easy to find. Unlikely but possible. Remeber size difference of binaries and hash space.
It's a virus, user
>file system breaks
>fsck it multiple times (read only mode)
>the error appears at a different location every time
>t. majored in Gender Studies
SHA256 probability of collision is less than 0.0000001 on any input with less than 4.8×10^29 elements
would you elaborate? what do you mean as a location? a pointer to a system space?
get a new psu
I tend to check during installation, to keep busy.
I don't quite remember, maybe it was block IDs, some identifier number and it was a different one each time. Ended up doing a copy-reformat-restore.
This is a rented server in a data center.
>data center
if thats a vps, that's ok as the space is ephemeral. If that's a dedicated server, then it's not a dedicated server but a vps really.
you CAN'T check if source matchs the compiled.
You should have used an animal reaction image, OP.
>dude science is just a point of view
>1 against 183682362817378 is just 50% 50% because there's two possible outcomes
mount the iso and try to find the trojan.