Future plans for piv-agent: ditching gpg #273
smlx
announced in
Announcements
Replies: 2 comments
-
|
Experimental age plugin support, and the start of GPG removal: #315 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
v1.0.0 failed to release due to a workflow issue, so v1.0.1 is available. It is functionally identical to 1.0.0. v2.0.0 is also available. This removes all GPG support (and several thousand lines of code). It also updates the docs. Please heed the warning in the README and in the docs FAQ: age support is experimental, the identity format is not set, and I'm not a cryptographer. Use with caution. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I no longer really need gpg support. It is poorly documented, annoying to develop against, breaks in minor version updates, and has all kinds of sharp edges as a user. Cryptographically it is considered anachronistic and bad news all round.
I currently use pass but would like to switch to passage. So my plan is to drop gpg support and instead implement an age plugin as described in #134.
I don't have a lot of free time at the moment so this is not going to happen anytime soon. However I wanted to announce this plan in case anyone was thinking of depending on piv-agent's gpg-agent support. Please don't, because it will be going away in future. 🙂
Beta Was this translation helpful? Give feedback.
All reactions