Skip to content
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

Using gpg 2.1 and long gpghome paths fails without meaningful error #40

Open
kornysietsma opened this issue May 22, 2017 · 0 comments
Open

Comments

@kornysietsma
Copy link

Gpg 2.1 has problems if you run your gpg-agent from a directory that is more than 108 characters long: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847206

(we had this situation on some machines because our puppet rspec tests use a custom gpg home for testing)

Hiera-eyaml fails in this scenario with an error similar to:
Error from DataBinding 'hiera' while looking up 'foo::bar': Decryption failed on node baz.local

It's reasonable to fail in this scenario, but it'd be much nicer if there were some way to expose the underlying gpg errors, which are rather more meaningful.

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

No branches or pull requests

2 participants