Problems with gnome-keyring et al. (was: Card only available to root user)

2011-08-09 Thread Werner Koch
On Tue, 9 Aug 2011 02:44, l...@debethencourt.com said: So it looks like GNOME's ssh-agent is interfering. How can I avoid this? Tell them that they should not interfere with GnuPG. If you put a line use-standard-socket into ~/.gnupg/gpg-agent.conf and stop starting gpg-agent in the

Re: Working with a system-shared keyring

2011-08-09 Thread Werner Koch
On Fri, 10 Jun 2011 20:43, do...@dougbarton.us said: But fixes a lot of problems. The keyring is a database and if we distribute this database to several files without a way to sync them; this leads to problems. You may have not been affected by such problems but only due to the way you use

Card Reader on Cherry Keyboard (omnikey) with OpenPGP Smart Card

2011-08-09 Thread Oleksandr Shneyder
Hello list, I have issues using OpenPGP smart cards from kernel concepts with omnikey card reader integrated in Cherry keyboard (Cherry XX44 USB keyboard) I can read a smart card status: $ gpg --card-status Application ID ...: D276000124010205102E Version ..: 2.0

Re: Problem with GPG

2011-08-09 Thread lists . gnupg-users
Hello Werner, Yesterday, Aug 8, Werner Koch wrote to lists.gnupg-us...@duinheks.nl about...: WK You should better use WK gpg --batch --sign --armour --clearsig --passphrase-fd 0 --yes -o $1.asc $1 I will do that in future. WK to avoid the mv. Even better use gpg-agent. That will take

Re: Card Reader on Cherry Keyboard (omnikey) with OpenPGP Smart Card

2011-08-09 Thread Werner Koch
On Tue, 9 Aug 2011 12:04, oleksandr.shney...@obviously-nice.de said: I have issues using OpenPGP smart cards from kernel concepts with omnikey card reader integrated in Cherry keyboard (Cherry XX44 USB keyboard) Omnikey based readers don't work with that card because the readers don't support

Re: Card Reader on Cherry Keyboard (omnikey) with OpenPGP Smart Card

2011-08-09 Thread Oleksandr Shneyder
Thank you for your answer, Werner Actually, I only need, that ssh authentication works with that cards and omnikey card readers. How do you think, is there are a chances, that it'll be work soon? Should I try to use pc/sc driver? lg, alex Am 09.08.2011 15:31, schrieb Werner Koch: On Tue, 9

Re: Card Reader on Cherry Keyboard (omnikey) with OpenPGP Smart Card

2011-08-09 Thread Werner Koch
On Tue, 9 Aug 2011 16:28, oleksandr.shney...@obviously-nice.de said: Actually, I only need, that ssh authentication works with that cards and omnikey card readers. How do you think, is there are a chances, that it'll be work soon? Should I try to use pc/sc driver? The pc/sc driver won't

Re: Working with a system-shared keyring

2011-08-09 Thread Doug Barton
On 08/09/2011 02:38, Werner Koch wrote: On Fri, 10 Jun 2011 20:43, do...@dougbarton.us said: But fixes a lot of problems. The keyring is a database and if we distribute this database to several files without a way to sync them; this leads to problems. You may have not been affected by such

Re: Problem with GPG

2011-08-09 Thread Werner Koch
On Tue, 9 Aug 2011 13:34, lists.gnupg-us...@duinheks.nl said: gpg (GnuPG) 2.0.18 libgcrypt 1.5.0 Okay, I only asked to make sure that we are really using the right version. It would be helpful if you could change this function in gnupg/g10/pkglue.c: static gcry_mpi_t mpi_from_sexp

OpenPGP Card CHV* failed: general error

2011-08-09 Thread Mike Cardwell
Hi, My OpenPGP Card (v2) has been working fine for a couple of days now, but it has stopped tonight. Simply trying to sign some text gives the following error: mike@Fuzzbutt:~$ date|gpg --clearsign -BEGIN PGP SIGNED

Re: Problem with GPG

2011-08-09 Thread Heinz Diehl
On 08.08.2011, Werner Koch wrote: echo | /usr/bin/gpg --batch --sign --armour --clearsig --passphrase-fd 0 $1 gpg --batch --sign --armour --clearsig --passphrase-fd 0 --yes -o $1.asc $1 Shouldn't this be --armor

Re: Problem with GPG

2011-08-09 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Tuesday 9 August 2011 at 9:40:13 PM, in mid:20110809204013.ga2...@fritha.org, Heinz Diehl wrote: Shouldn't this be --armor (and not --armour)?! The output from gpg --dump-options shows that both spellings are valid (for v 1.4.11 at