Hi!
Am Sonntag, den 09.03.2008, 15:05 +0100 schrieb Sven Radde:
> Apart from applying the regular patches, the only action I remember that
> could possibly have an impact on GnuPG was installing the "seahorse"
> package. However, removing it again did not change anything.
Update: It works again.
On Mon, 2008-03-10 at 18:15 +0100, Werner Dittmann wrote:
> I've the same problem with an SCM 535. By running the pcscd in
> forgroung with debug enabled I got the follwoing messages:
>
have you tried posting directly the muscle's mailing list ?
http://lists.drizzle.com/pipermail/muscle/
Ludovi
hello,
i used
secret-keyring /media/USB/.gnupg/secring.gpg
and everything worked fine,
but now enigmail does not recognize ~/.gnupg/secring.gpg
as default seckeyring
even with this solution i am satisfied, but still i wander is there a way to
set additional seckeying from USB stick
?
than
I've the same problem with an SCM 535. By running the pcscd in
forgroung with debug enabled I got the follwoing messages:
pcscdaemon.c:294:main() pcscd set to foreground with debug send to stderr
pcscdaemon.c:507:main() pcsc-lite 1.4.3 daemon ready.
hotplug_libusb.c:454:HPAddHotPluggable() Adding
Hi gpg-users,
tried to make a detached signature of a tar file today and got this:
[EMAIL PROTECTED]:/tmp$ gpg --verbose --detach-sign foobar.tar.gz
gpg: verwende Vertrauensmodell PGP
gpg: Schlüssel : Akzeptiert als vertrauenswürdiger Schlüssel
gpg: Schlüssel : Akzeptiert als ver
