Skip to content

Update Commit Signing Doc#806

Draft
vgrassia wants to merge 2 commits into
mainfrom
vgrassia/dev
Draft

Update Commit Signing Doc#806
vgrassia wants to merge 2 commits into
mainfrom
vgrassia/dev

Conversation

@vgrassia

@vgrassia vgrassia commented May 6, 2026

Copy link
Copy Markdown
Member

🎟️ Tracking

📔 Objective

📸 Screenshots

# Conflicts:
#	docs/contributing/commit-signing.mdx
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 12, 2026

Copy link
Copy Markdown

Deploying contributing-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6d6383a
Status: ✅  Deploy successful!
Preview URL: https://0da7aa26.contributing-docs.pages.dev
Branch Preview URL: https://vgrassia-dev.contributing-docs.pages.dev

View logs

1. **[Hardware-backed SSH key](#hardware-backed-ssh-key)**: private key lives on a FIDO2 security
key (e.g., YubiKey 5+). Each commit requires a PIN and a physical touch. This is the most secure
option.
2. **[Standard SSH key](#standard-ssh-key)**: private key lives on disk, protected by a passphrase.

@quexten quexten Jun 15, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we recommending on-disk SSH keys over bitwarden ssh agent? On most systems, the standard SSH key has fewer protections (no memory-dump protection, possibly no passphrase, and also no access control), wheras the Bitwarden-stored SSH agent has all three (assuming you did not configure to never ask for approval)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants