Skip to content

Commit

Permalink
Updates per issue 1165. Fixed lint of grammar
Browse files Browse the repository at this point in the history
  • Loading branch information
markgamache committed Jul 1, 2024
1 parent 87c8e9a commit 2d94e1b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion cheatsheets/Pinning_Cheat_Sheet.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ The three choices are explained below in more detail. You are encouraged to pin

#### Certificate

The certificate is easiest to pin. You can fetch the certificate out of band for the website, have the IT folks email your company certificate to you, use `openssl s_client` to retrieve the certificate etc. At runtime, you retrieve the website or server's certificate in the callback. Within the callback, you compare the retrieved certificate with the certificate embedded within the program. If the comparison fails, then fail the method or function, log it on the client-side and alert the end-user. If your threat model warrants pinning, understand that users will click past any warnings, so do not give the user an option to proceed and bypass the pin.
The certificate is easiest to pin. You can fetch the certificate out of band for the website, have the IT folks email your company certificate to you, use `openssl s_client` to retrieve the certificate etc. At runtime, you retrieve the website or server's certificate in the callback. Within the callback, you compare the retrieved certificate with the certificate embedded within the program. If the comparison fails, then fail the method or function, log it on the client-side and alert the end user. If your threat model warrants pinning, understand that users will click past any warnings, so do not give the user an option to proceed and bypass the pin.

**Benefits:**

Expand Down

0 comments on commit 2d94e1b

Please sign in to comment.