Would it be possible to add similar support for GPG keys?

I'm still super interested in this because I'd like to be able to more natively use 1password as the central hub to store keys used to sign published artifacts generated in CI. It'd be super-handy if I could easily generate a new signing subkey and revoke one which was compromised when a CI system's cloud provider gets hacked again, all without having to change a thing about the ci logic. Bonus points for also auto-publishing to one or more keyservers on-change. For one example. Right now I have to locally export a key, import that into 1password as a text field, then have automation fetch the armored key before importing it into a local agent, etc. It's kind of a convoluted process compared to something like telling a package signing process to just use a local key agent which can just speak to 1password connect -- for another example. :) Git commit signing is technically on the list, but more of a side effect to me personally.

IMO, GPG is a fairly complex standard that sees use in many many ways. Adding support for all of these myriad ways into 1Password maybe reinventing the wheel because GPG already has a large number of tools available. And these tools are quite modern in their implementation (but often not in their UI/UX). At the same time, I do want to be able to store my GPG keys in 1Password. After all, what I am paying for is having to remember just "one password".

I think they're hoping everyone storing PGP keys is using them for signing commits and as people discover it can be done with SSH, they'll give up asking for the feature. There are indeed those of us from the '90s still using S/MIME and encrypting blocks to others who want 1Password to be the one stop secret shop.

Big +1 SSH commit signing is fine until you need to rotate keys. Revoking a GPG key will continue to show commits in GitHub (unsure about GitLab) as "verified (expired)". The only way I've found to do the same with SSH keys is to remove the old key completely, but then commits show as "unverified" which defeats the point of supply chain integrity since it's not possible to distinguish a commit that was signed with an old key, or a commit that was not signed, or signed with another key that's not allowed. The alternative is to not rotate signing keys, but then you compromise supply chain integrity further by not ensuring keys are rotated in a timely fashion.

Just to throw my opinion into the mix: SSH keys cannot be substituted for PGP keys in all cases. A PGP key is closer to a digital certificate than it is to an SSH key; whereas an SSH key is really just a raw public key with a tiny amount of metadata attached, a PGP key can and generally does contain a wealth of additional metadata, and is also used for a much wider variety of purposes, like certifying other public keys or containing attached subkeys. In concrete terms, an SSH key cannot be substituted for a PGP key for many use cases, like E2E encrypted email, YubiKey, cryptocurrency wallets etc. If 1Password were to support a GnuPG authentication agent, it would make storing private keys in a centralized location easier and more secure, and the process of performing common PGP-related tasks more transparent. While GnuPG is pretty widely supported nowadays, and there is a wide variety of FOSS out there for managing keys, having my PGP keys stored in 1Password would make life a little easier. It's a small quality-of-life improvement, but not really a significant ask from me personally. I use 1Password because it has the best user experience and broadest compatibility of all of the password managers I've tried, and I intend to keep using it regardless of whether or not PGP keys are supported.

GPG support? (like SSH) | 1Password Community

81 Replies

ionos
Occasional Contributor
3 years ago
floris_1P

top of my head:

key servers for verification, web of trust (an SSH commit signature by itself means nothing, if I don't know the key)

existing workflows based on GPG

subkeys
floris_1P
1Password Team
3 years ago
What are the benefits you're seeing of using GPG over SSH for commit signing?
- jau
  New Contributor
  7 months ago
  GPG keys exist in a web of trust outside of the specific platform that I am using to host my code.
Former Member
3 years ago
I would love to see support for GPG!

As previously stated by some, I use GPG for signing commits with GIT (I also prefer it over SSH keys).
ionos
Occasional Contributor
3 years ago
I think it has all been mentioned before on this thread, but here it does:

File encryption (e.g. for archiving sensitive information)

Git comment signing (we prefer it over signing with SSH keys)

Email encryption/signing

Cheers,
-i
floris_1P
1Password Team
3 years ago
To all the +1'ers in this thread: it would be helpful if you could also describe what you're doing now that requires GPG.
- jau
  New Contributor
  7 months ago
  Signing code commits and releases is my primary use case.
doubleforte
Occasional Contributor
3 years ago
+1
Former Member
3 years ago
+1
Lucent
New Contributor
3 years ago
Seems like interest is dwindling because many were using GPG for commit signing and SSH can do that as well now. Many of us still use GPG for encrypted communication and file storage.
Former Member
3 years ago
I also would appriciate to see the gpg support
Jack_P_1P
1Password Team
3 years ago
Hi @aiguofer:

Thanks for sharing your feedback!

@v1k0d3n:

GitLab.com now supports SSH key commit signing as well: Sign commits with SSH keys | GitLab

With that said, I can definitely see how GPG key management would be helpful as well.

Jack

Forum Discussion

GPG support? (like SSH)

81 Replies

Recent discussions

Apple Watch CLI Authentication

macOS 26 beta browser extension very slow to open

Use op on headless system with glab?

Console flooded with errors when clicking links during 1Password passkey selection dialog

How to create an Address field type using the CLI?