From 2e44620fc3a4cf9a8e52add62d2282545a46261a Mon Sep 17 00:00:00 2001 From: Marc G <91296549+Marc-Gee@users.noreply.github.com> Date: Mon, 30 Dec 2024 22:44:26 -0600 Subject: [PATCH 1/3] update version refrences to 0.8.x A few outdated 0.7.0 version references existed. The outdated references tripped up some users. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f28e6a8d4..97eb846a4 100644 --- a/README.md +++ b/README.md @@ -159,7 +159,7 @@ The result should confirm that 1 key was *either* imported or updated. *Ignore* 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.) ``` -gpg --verify seedsigner.0.7.*.sha256.txt.sig +gpg --verify seedsigner.0.8.*.sha256.txt.sig ``` When the verify command completes successfully, it should display output like this: @@ -229,7 +229,7 @@ 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.*.sha256.txt ``` **On Windows (inside Powershell):** Run this command @@ -241,9 +241,9 @@ On Windows, you must then manually compare the resulting file hash value to the 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.x.[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.x.[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. From 4b785057e491c661e75d10f5c21e135845085465 Mon Sep 17 00:00:00 2001 From: Marc G <91296549+Marc-Gee@users.noreply.github.com> Date: Wed, 22 Jan 2025 21:26:49 -0800 Subject: [PATCH 2/3] Modify GPG commands to use 0.8.5 Modify the GPG commands to match our specific (current) version 0.8.5, removing the wildcards. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 97eb846a4..beada3247 100644 --- a/README.md +++ b/README.md @@ -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: @@ -229,12 +229,12 @@ 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.8.*.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.
From 6bf30089324a4801e1a21dda6b47952a13bff734 Mon Sep 17 00:00:00 2001 From: Marc G <91296549+Marc-Gee@users.noreply.github.com> Date: Wed, 22 Jan 2025 21:34:17 -0800 Subject: [PATCH 3/3] Modify additional wildcard references to 0.8.5 Edit the wildcard references in the expected output from the Windows PowerShell command --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index beada3247..76703a337 100644 --- a/README.md +++ b/README.md @@ -241,9 +241,9 @@ On Windows, you must then manually compare the resulting file hash value to the Wait up to 30 seconds for the command to complete, and it should display: ``` -seedsigner_os.0.8.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.8.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.