Skip to content

Commit

Permalink
Fix Spelling, grammar and shasum command
Browse files Browse the repository at this point in the history
Spelling, grammar edits were made, -  as suggested by the reviewers comments. 

Additionally: 1) the Windows certutil (aka shasum) command for windows was clarified. 
2) the shasum command on osX and Linux now includes the ignore-missing flag for compatibility with the expected new 0.5.2 shasum file format. The 0.5.2 shasum file will include hashes for multiple binaries now , but the user will likely only be checking one single binary. hence we tell shasum command to skip any missing files and to not report "missing files" error.
  • Loading branch information
Marc-Gee authored Jan 30, 2023
1 parent b04383d commit a136a86
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Download these files to your computer:
3. seedsigner_0_5_x.img.zip.sha256.sig

**Note:** The version numbers of the latest files will be higher than this example, but the naming format will be the same.
Once the files have all finished downloading, follow the steps below to verify them, and then to write the software onto a MicroSD card. Insert the MicroSD into your assembled hardware and turn on the USB power. Allow about 45 seconds for our logo to appear, and then you can begin using your Seedsigner!
Once the files have all finished downloading, follow the steps below to verify the download before continuing on to write the software onto a MicroSD card. Next, insert the MicroSD into your assembled hardware and connect the USB power. Allow about 45 seconds for our logo to appear, and then you can begin using your Seedsigner!



Expand Down Expand Up @@ -179,20 +179,21 @@ If the two ID's do *not* match, then you must stop here immediately. Do not cont

<br>

### 2. Verifying that the *software images/binaries* are genuine
### Step 2. Verifying that the *software images/binaries* are genuine

Now that you have confirmed that you do have the real Seedsigner Project's Public Key (ie the 16 characters match) - you can return to your terminal window. Running the the *shasum* command, is the final verification step and will confirm (via file hashing) that the software code/image files (ie the binary files inside the zip file), were also not altered since publication, or even during your download process.

**On Linux or OSX:** Run this command
```
shasum -a 256 -c seedsigner_0_*_*.img.zip.sha256
shasum -a 256 --ignore-missing -check seedsigner_0_*_*.img.zip.sha256
```

**On Windows (inside Powershell):** Run this command
```
CertUtil -hashfile seedsigner_0_*_*.img.zip SHA256 | findstr /v "hash"
```
<BR>
On Windows, you must manually compare the above resulting hash value to the corresponding hash value shown inside the .SHA256 cleartext file.
<BR>

Wait about 30 seconds for the command to complete, and it should display:
```
Expand Down

0 comments on commit a136a86

Please sign in to comment.