search

dgolja / golja-gnupg

Puppet module for managing GnuPG package and public keys
Apache License 2.0
13 stars 46 forks source link

Batch import secret keys to avoid interactive prompt with GnuPG 2.1+ #26

Closed mattock closed 3 years ago

mattock commented 7 years ago

GnuPG 2.1 and later prompts for secret key passphrase if --import is not coupled with --batch. The rationale for the changed behavior is described in https://dev.gnupg.org/T2313. This problem affects at least Debian 9 ("stretch") which is bundled with GnuPG 2.1.18.

With this change all --import calls include --batch, so that private keys get imported without user interaction. This did not seem to have any ill effects on older GnuPG versions, such as 1.4.18, which comes in Debian 7 ("wheezy").

mattock commented 7 years ago

@dgolja It's not obvious how the Travis CI build error is related to my PR, if it is at all. Any pointers?

karn09 commented 5 years ago

Just came across this issue. This helped me solve it. Thanks!

mattock commented 5 years ago

@karn09 no problem!

DLeich commented 3 years ago

I just ran into this issue on Oracle Linux 8. Unfortunately, considering there hasn't been an updated release since 2016, that makes me think that this module has unfortunately fizzled out. Unless this PR gets merged, that means this module will not support modern OS versions which include GnuPG 2.1+.

DLeich commented 3 years ago

@dgolja - What's the status of this module? Seems like maybe you need a little help maintaining it?

mattock commented 3 years ago

I think this module is unmaintained. @DLeich maybe we should just fork this to get changes merged in one place.

dgolja commented 3 years ago

sorry it's almost unmaintained. Happy to merge this PR and happy to add elevated privileges to help maintain this module.

I will check things out during the weekend and I can release the new version next week.

DLeich commented 3 years ago

@dgolja - Thank you for merging this in! Really appreciate it. Would you be perhaps interested in migrating your module to Vox Pupuli? That would probably really help with sharing maintenance of the code. See https://voxpupuli.org/docs/migrate_module/ on the procedures to get it migrated.