Skip to content
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.

Sign up for GitHub

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

update version refrences to 0.8.x #652

Merged
merged 4 commits into from
Feb 5, 2025
Merged

update version refrences to 0.8.x #652

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2e44620
update version refrences to 0.8.x
Marc-Gee Dec 31, 2024
4b78505
Modify GPG commands to use 0.8.5
Marc-Gee Jan 23, 2025
6bf3008
Modify additional wildcard references to 0.8.5
Marc-Gee Jan 23, 2025
4204aef
Merge branch 'dev' into Version-bump-in-verification-instructions
newtonick Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,9 +157,9 @@ The result should confirm that 1 key was *either* imported or updated. *Ignore*

![SS - Fetchkeys-Keybase PubKey import with Fingerprint shown (New import or update of the key)v3-100pct](https://user-images.githubusercontent.com/91296549/221334414-adc3616c-462e-490e-8492-3dfee367d13a.jpg)

Next, you will run the *verify* command on the signature (.sig) file. (*Verify* must be run from inside the same folder that you downloaded the files into earlier. The `*`'s in this command will auto-fill the version from your current folder, so it should be copied and pasted as-is.)
Next, you will run the *verify* command on the signature (.sig) file. (*Verify* must be run from inside the same folder that you downloaded the files into earlier.)
```
gpg --verify seedsigner.0.8.*.sha256.txt.sig
gpg --verify seedsigner.0.8.5.sha256.txt.sig
```

When the verify command completes successfully, it should display output like this:
Expand Down Expand Up @@ -229,21 +229,21 @@ Now that you have confirmed that you do have the real SeedSigner Project's Publi

**On Linux or OSX:** Run this command
```
shasum -a 256 --ignore-missing --check seedsigner.0.7.*.sha256.txt
shasum -a 256 --ignore-missing --check seedsigner.0.8.5.sha256.txt
```

**On Windows (inside Powershell):** Run this command
```
CertUtil -hashfile seedsigner_os.0.8.0.Insert_Your_Pi_Models_binary_here_For_Example_pi02w.img SHA256
CertUtil -hashfile seedsigner_os.0.8.5.Insert_Your_Pi_Models_binary_here_For_Example_pi02w.img SHA256
```
On Windows, you must then manually compare the resulting file hash value to the corresponding hash value shown inside the .SHA256 cleartext file.
<BR>

Wait up to 30 seconds for the command to complete, and it should display:
```
seedsigner_os.0.7.x.[Your_Pi_Model_For_Example:pi02w].img: OK
seedsigner_os.0.8.5.[Your_Pi_Model_For_Example:pi02w].img: OK
```
**If you receive the "OK" message** for your **seedsigner_os.0.7.x.[Your_Pi_Model_For_Example:pi02w].img file**, as shown above, then your verification is fully complete!
**If you receive the "OK" message** for your **seedsigner_os.0.8.5.[Your_Pi_Model_For_Example:pi02w].img file**, as shown above, then your verification is fully complete!
**All of your downloaded files have now been confirmed as both authentic and unaltered!** You can proceed to create/write your MicroSD card😄😄 !!

If your file result shows "FAILED", then you must stop here immediately. Do not continue. Contact us for assistance at the Telegram group address above.
Expand Down