Josef Wolf wrote:
Hello!
I need a setup where the user running gpg -e -r foobar is not able to
modify keyring contents. I tried:
# chown -R root:user ~user/.gnupg
# chmod -R o=rwX,g=rX,o= ~user/.gnupg
Unfortunately, this don't work because gpg does some write operations
in
On Mon, 11 Sep 2006 00:16, Josef Wolf said:
1. It locks the keyring. --lock-never will avoid this. Is it safe
to use --lock-never as long as it is guaranteed that _only_ gpg -e
If the keyrings are read-only, there is no need for locking. Thus
--lock-never is safe.
2. There's the
On Fri, 8 Sep 2006 19:33, Werner Koch [EMAIL PROTECTED] said:
It is possible that the iconv detection does not work.
And yes, we are falling back to an internal iconv replacement.
Look into util/strgutil.c:
snip
You might want to just add a line
|| !ascii_strcasecmp (newset, 88591
Hi.
I am having a problem with my smartcard. I am running Suse 10.1 and my
card has worked previously under Suse 10.0. Here is my debug log. Can
anybody give me an advice?
Cheers! Kai
gpg: DBG: ccid-driver: using CCID reader 0 (ID=04E6:5115:21120617208494:0)
gpg: DBG: ccid-driver: idVendor:
