Hi,
gpg may also write to the keyring if you verify key signatures. The
signatures verification status is cached in the keyring.
This bug should be closed because this seems to be due to an OS crash.
The rename operation is atomic and thus even if you kill gpg at a bad
time you should never end
On Wed, 7 Sep 2011 16:49, pm.deb...@googlemail.com said:
I cannot not remember though executing any `gpg` commands. Are other
programs like GNOME Keyring or Evolution accessing gpg through some
library causing the same effect?
Gpg often writes to the keyring. Importing or refeshing a key
Am Donnerstag, den 08.09.2011, 11:08 +0200 schrieb Werner Koch:
On Wed, 7 Sep 2011 16:49, pm.deb...@googlemail.com said:
I cannot not remember though executing any `gpg` commands. Are other
programs like GNOME Keyring or Evolution accessing gpg through some
library causing the same
On Sun, 4 Sep 2011 16:15, pm.deb...@googlemail.com said:
The question now is: “What program created `pubring.gpg.tmp` at 10:55
when the system froze (probably unrelated)?”.
gpg does this. Updates to the keyring are done by creating a copy and
then renaming it back.
Salam-Shalom,
Werner
Am Mittwoch, den 07.09.2011, 13:36 +0200 schrieb Werner Koch:
On Sun, 4 Sep 2011 16:15, pm.deb...@googlemail.com said:
The question now is: “What program created `pubring.gpg.tmp` at 10:55
when the system froze (probably unrelated)?”.
gpg does this. Updates to the keyring are done by
severity 640241 normal
quit
Dear Debian folks,
Am Samstag, den 03.09.2011, 16:48 +0200 schrieb Paul Menzel:
Package: gnupg
Version: 1.4.11-3
Severity: important
today I noticed that Evolution does not sign or decrypt my messages
anymore.
Trying it manually with `gpg` I got the same
Package: gnupg
Version: 1.4.11-3
Severity: important
Dear Debian folks,
today I noticed that Evolution does not sign or decrypt my messages
anymore.
Trying it manually with `gpg` I got the same error.
$ LANG=C gpg --decrypt /tmp/test.mbox
gpg: key 5DD5BC10: secret key without
7 matches
Mail list logo
