Now I had a similar problem with debian packages.
That's what I got from dpkg-buildpackage :
dpkg-buildpackage: warning: Failed to sign .dsc and .changes file
Checking signature on .changes
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the
On Tue, 28 Aug 2012 21:48, ricu...@gmail.com said:
F Hi Werner,
the ! exclamation mark did the trick!
I tried specifying the subkey I wanted before, but only the exclamation
mark makes it work.
With the exclamation mark, also signing in evolution works again.
Is this documented somewhere?
On Mon, 27 Aug 2012 22:57, ricu...@gmail.com said:
#gpg --sign setup_my_system.sh
gpg: sending command `SCD PKSIGN' to agent failed: ec=6.18
The error is:
$ gpg-error 6.18
100663314 = (6, 18) = [...] = (SCD, Wrong secret key used)
The scdaemon would have printed this to its log file:
Hi Werner,
the ! exclamation mark did the trick!
I tried specifying the subkey I wanted before, but only the exclamation
mark makes it work.
With the exclamation mark, also signing in evolution works again.
Is this documented somewhere?
Thanks a lot.
Richard
On Di, 2012-08-28 at 10:47 +0200,
Hi,
this is my first post to this list.
I have a crypto stick from www.privacyfoundation.de, and when I first
set it up, signing emails worked flawlessly.
But then I wanted to also be able to use my crypto-stick for ssh
authentication.
As adding the authentication sub key turned out to be
