-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for adding passphrase and key expiry date #18
Comments
Are there any updates or information regarding this? I do see that passphrase is Unsupported |
Somehow I never saw this. Looking at this real quick, not sure the current libraries support these options. Since there's been a couple of votes, I'll take a closer look and see what's possible. |
any update on this? is it possible? |
Currently not possible with the current PGP libraries available. None of them support past phrases on the keys. |
Is it possible to replace the library with one that does support them?
…On Fri, 6 Oct 2023, 14:01 Erik Kristensen, ***@***.***> wrote:
Currently not possible with the current PGP libraries available. None of
them support past phrases on the keys.
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH7GYF2QP7E3WY6FGZPOWMTX576MPAVCNFSM6AAAAAAR5QNHWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGY2DGNRQG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I did some digging. It looks like I can get passphrase in, but still haven't found a solution for expiry. |
I found this solution for my setup https://registry.terraform.io/providers/Olivr/gpg/latest |
@bshibilov-sh glad you found something that works. I'll be adding passphrase support soon. Still trying to find a solution for expiry in the way that's been asked. |
@ekristen i am not hung up on the exact way of setting expiry eg days as long as an expiry can be set - it could be a date - it's just we have some suppliers who won't accept keys unless there is an expiry set to them |
I've got some time this week to dedicate, I've already got some of this implemented in dev, still working on figuring out the expiry, but will likely push the passphrase sooner than later. |
Loving this as it makes PGP generation in azure so much easier
There are two pieces of functionality that are missing that stop us from using it for all our use cases.
It would be good if we ha the ability to add these as optional requirements to the key generation
The text was updated successfully, but these errors were encountered: