Am Samstag, den 14.03.2015, 09:40 +0100 schrieb Matthias Beyer:
gpg: m...@beyermatthias.de: skipped: No public key
gpg: [stdin]: encryption failed: No public key
Can somebody tell me what causes this error?
Let me guess: You were updating GnuPG 2 recently and you were using a
Phew. That's a bummer.
Only thing I can think of is that pass is using another gpg binary
than you are on the cli that is not aware of your key.
Do you have any combination of gpg1/gpg2/gpg2.1 installed?
If so: do you have a gpg2 binary? Is your key both in the output of
`gpg -k` and `gpg2 -k`?
Hmm,
I guess something went wrong on the pass init step then.
Did you get any output during init?
Can you retry your init with your key id instead of your mail address?
On 14.03.2015 10:20, Matthias Beyer wrote:
Hi,
On 14-03-2015 10:03:53, Lenz Weber wrote:
Hi, I guess it's to keep the
Hi,
On 14-03-2015 11:41:57, Lenz Weber wrote:
Phew. That's a bummer.
Only thing I can think of is that pass is using another gpg binary
than you are on the cli that is not aware of your key.
Do you have any combination of gpg1/gpg2/gpg2.1 installed?
I have only a gpg2 binary. I had
Okay,
I've got one more idea.
Edit your pass script, at the top insert
`set -o xtrace` in the line after `set -o pipefail`
Now every command that is executed by pass will be output to the
command line.
Then just do your gpg insert again - after entering both passwords,
it will print your
Hi,
here is mine:
I'm running
* gpg2.1.2
* pass 1.6.5
* bash 4.3.33
on NixOS. The output is not even close the same... surprisingly...
Output of bash -x pass insert test:
bash: warning: setlocale: LC_ALL: cannot change locale (en)
+ export
I just noticed you can do that without editing the pass script:
just call
bash -x `which pass` insert test
On 14.03.2015 12:02, Lenz Weber wrote:
Okay,
I've got one more idea.
Edit your pass script, at the top insert
`set -o xtrace` in the line after `set -o pipefail`
Now every command
On 14-03-2015 20:58:18, Mike Charlton wrote:
Possibly you are using Gnome???
Nope, no gnome here.
--
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer
Proudly sent with mutt.
Happily signed with gnupg.
pgpYUwmp5NZA4.pgp
Description: PGP signature
On 14-03-2015 13:36:33, Lenz Weber wrote:
Really no output?
Nope. Nothing.
Here's what I would expect (invalid target key test-id, creating
test/bla with password blas):
Enter password for test/bla: + echo
+ read -r -p 'Enter password for test/bla: ' -s password
Enter password for
On 14-03-2015 15:04:32, René Neumann wrote:
Just out of curiosity. Could you do
export
Really no output?
Here's what I would expect (invalid target key test-id, creating
test/bla with password blas):
Enter password for test/bla: + echo
+ read -r -p 'Enter password for test/bla: ' -s password
Enter password for test/bla: + echo
+ read -r -p 'Retype password for test/bla: ' -s
Possibly you are using Gnome??? Version 2.1 of gpg moved the private
keys off of the secring and they are now managed by gpg-agent.
Gnome has its own implementation of gpg-agent which is known to
be incompatible with gpg. I'm wondering whether the keys
are in a different directory for some
On Sat, Mar 14, 2015 at 12:51:59PM +0100, Matthias Beyer wrote:
On 14-03-2015 12:04:56, Lenz Weber wrote:
I just noticed you can do that without editing the pass script:
just call
bash -x `which pass` insert test
This prints some export PATH= things before anything, but does not print
On 14-03-2015 15:03:24, Lenz Weber wrote:
So now we have your GPG call.
On 14.03.2015 14:54, Matthias Beyer wrote:
gpg2 -e -r 20CA0F94 -o /home/m/.password-store/test.gpg --quiet
--yes --compress-algo=none --no-encrypt-to --batch --use-agent
I can only guess it's something in the path
On 14-03-2015 15:17:45, René Neumann wrote:
Am 14.03.2015 um 15:15 schrieb Matthias Beyer:
On 14-03-2015 15:04:32, René Neumann wrote:
Just out of curiosity. Could you do
export
On 14-03-2015 15:10:41, Matthias Beyer wrote:
On 14-03-2015 15:03:24, Lenz Weber wrote:
So now we have your GPG call.
On 14.03.2015 14:54, Matthias Beyer wrote:
gpg2 -e -r 20CA0F94 -o /home/m/.password-store/test.gpg --quiet
--yes --compress-algo=none --no-encrypt-to --batch
16 matches
Mail list logo
