Skip to content

Commit 3652098

Browse files
authored
docs: restore hardware key callout to top-level SSH signing tip (#805)
On #672 we moved the sk-backed key recommendation out of the main tip and into a nested step. Add it back at the top level so hardware keys remain visibly ranked as the highest-security option.
1 parent 97d02e8 commit 3652098

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/contributing/commit-signing.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,9 @@ GitHub supports [commit signing][github-verification] with SSH, GPG, and S/MIME.
2727

2828
If you're unsure what to use, <strong>we recommend you create a commit signing key using SSH per
2929
latest security best practices </strong> (see the
30-
[PGP problem](https://www.latacora.com/blog/2019/07/16/the-pgp-problem/) for more details).
30+
[PGP problem](https://www.latacora.com/blog/2019/07/16/the-pgp-problem/) for more details). For
31+
maximum security, consider using a [hardware-backed SSH key](#hardware-backed-ssh-key-configuration)
32+
(YubiKey or other FIDO2 device) as your signing key.
3133

3234
:::
3335

0 commit comments

Comments
 (0)