Skip to content

Commit 8f325e9

Browse files
committed
minor fixes
1 parent cff6da4 commit 8f325e9

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/security/verify-installers.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Our Windows installers are signed using a code signing certificate. You can veri
3232

3333
1. Open Terminal or PowerShell (found in Windows Start menu).
3434
2. Run either of the following commands to check the signature of the corresponding file:
35-
```powershell
35+
```pwsh
3636
Get-AuthenticodeSignature -FilePath "~\Downloads\Cryptomator-*.msi"
3737
Get-AuthenticodeSignature -FilePath "~\Downloads\Cryptomator-*.exe"
3838
```
@@ -44,7 +44,7 @@ Our Windows installers are signed using a code signing certificate. You can veri
4444
*for older releases, see [below](#windows-all-versions).
4545

4646
If the installer is properly signed, you should see output similar to:
47-
```
47+
```text
4848
SignerCertificate Status StatusMessage Path
4949
----------------- ------ ------------- ----
5050
BB0E... Valid Signature verified. Cryptomator-1.19.1-x64.msi
@@ -62,6 +62,7 @@ You can also inspect the certificate manually:
6262
### Certificate thumbprints for all Cryptomator versions {#windows-all-versions}
6363

6464
Every Cryptomator installer is signed with a certificate. A certificate is identified by its thumbprint. The signing certificate changed over time and the following table shows for each version the certificate thumbprint:
65+
6566
| Version(s) | Certificate Thumbprint |
6667
|---------------------|--------------------------------------------|
6768
| 1.19.2 | `20F30D7C5B1AB3ACAFA4AB27874ACBC4B47B0697`<!-- AUTOMATION MARKER FOR WORKFLOW --> |

0 commit comments

Comments
 (0)