Hi! People!
step 1 checks sha256 ? right ?
for persuasion , you need to additionally check with this command ? shasum -a 256 bitcoin-23.0-x86_64-apple-darwin.dmg to verify manually !
Yes, and compare it with the hashes listed in SHA256SUMS file.
Then verify "
SHA256SUM" file using "
SHA256SUM.asc" either at the start of after those steps.
Here's some images for reference (
it's for a different OS so the command is different):
Get the binary's SHA256sum
Open SHA256SUMS as text, then check if the binary's hash is the same as the result in the previous step
Both are the same:
52eefbaf8cfd292822e470a48a51e1eb51081d43a0a16db7441f34a017ff6097means 2 action "command GPG --server hkps://keys.for OpenPGP.org --reception-keys E777299FC265DD04793070EB944D35F9AC3DB76A" I add the key "Michael Ford" and then I drive the command "shasum -in 256 SHA256SUMS.asc" - it shows 3 action!
3 action shows 16 participants and including "Michael Ford" - a valid user signature.
1 questio - Why after -Why did a lot of participants appear in the keys after 3 actions if I added only 1 -Michael Ford?
https://a.radikal.host/2022/07/05/IMG_20220705_054716.jpg2 question - the shazam -256 SHA256SUMS.asc command what does it have to do with checking the "bitcoincore" installation file? I can 't get the gist of it .
the output of the command: a valid user signature gives additional confidence that the installation file "bitcoincore.dmg" is really good?
3 question -checking the sha256 installation file is not enough to make sure that the file is good?
Show Posts
