Re: OpenPGP card stopped working

Hi, Andreas Grassl wrote: > Sven Radde schrieb: >> 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 aga

Re: Graphical problem with pinentry - was: [Announce] GnuPG 2.0.9 released

Werner Koch wrote: Not really. It is just that the text displayed is now longer. I don't know the Mac pinentry and whether it auto-adjusts its size as the GTK pinentries do. The native Windows pinentery for example does not resize and thus the displayed text gets truncated. That's exactly th

Re: OpenPGP card stopped working

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven Radde schrieb: > 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, r

Re: [Announce] GnuPG 2.0.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 working fine here. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBCgAGBQJH6qH9AAoJEM+FBuO1wKhL5XEP/3XKy/zUomr5ZtpeVOePi4aU rm3xPbnmX0HmNIJQFAfXboS73b3mbTW5/hknbGK

Re: Graphical problem with pinentry - was: [Announce] GnuPG 2.0.9 released

Charly Avital wrote: It is only a graphical thing, the functioning of gpg-agent itself has not been affected. Could you please send me a screen capture off list? Ben ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/l

Re: [Announce] GnuPG 1.4.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Werner Koch wrote the following on 3/26/08 2:08 PM: > Hello! > > We are pleased to announce the availability of a new stable GnuPG-1 > release: Version 1.4.9. This is a maintenance release to fix a possible > vulnerability introduced with 1.4.8

[Announce] GnuPG 1.4.9 released

Hello! We are pleased to announce the availability of a new stable GnuPG-1 release: Version 1.4.9. This is a maintenance release to fix a possible vulnerability introduced with 1.4.8. The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It is a complete and

Re: [Announce] GnuPG 2.0.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've just upgraded to 2.0.9, overwriting an existing 2.0.8., under Ubuntu 7.10, running under Parallels in a Macbook with an Intel processor. Encountered no problems. Charly -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment

Re: [Announce] GnuPG 2.0.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've just upgraded to 2.0.9, overwriting an existing 2.0.8. Encountered no problems. Charly -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEcBAEBCAAGBQJH6olVAAoJE

Re: [Announce] GnuPG 2.0.9 released - make check failed

On Wed, 26 Mar 2008 16:11, [EMAIL PROTECTED] said: > make[3]: Leaving directory `/dev/shm/gpg/gnupg-2.0.9/tests/openpgp' Strange name for a working directory ;-) > make[3]: Entering directory `/dev/shm/gpg/gnupg-2.0.9/tests' > asschk: cmd_expect_ok: expected OK but got `ERR 50331649 General erro

Re: Graphical problem with pinentry - was: [Announce] GnuPG 2.0.9 released

On Wed, 26 Mar 2008 17:02, [EMAIL PROTECTED] said: > Maybe this specific pinentry needs to be re-written, but I would to > know, as I asked above, whether there might something different in gpg > 2.0.8's code that might affect pinentry *graphically*. Not really. It is just that the text displaye

Graphical problem with pinentry - was: [Announce] GnuPG 2.0.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, After compiling and installing GnuPG 2.0.9, overwriting an existing 2.0.8, the pinentry window that shows (when required) is slightly defective: the last text line shows only its upper part half, *as if* the whole pinentry window had "shrunk".

Re: [Announce] GnuPG 2.0.9 released - make check failed

checking for GPG Error - version >= 1.4... yes (1.6) checking for LIBGCRYPT - version >= 1.2.2... yes (1.4.0) checking for LIBASSUAN - version >= 1.0.4... yes (1.0.4) checking for LIBASSUAN pth - version >= 1.0.4... yes (1.0.4) checking for LIBASSUAN - version >= 1.0.1... yes (1.0.4) checking for K

Re: Key credentials validation problem

On Wed, 26 Mar 2008 01:32, [EMAIL PROTECTED] said: > gpg --list-packets < 0xdecafbad.asc or just gpg 0xdecafbad.asc to get an overview. Example: $ gpg 1e42b367.asc pub 2048D/1E42B367 2007-12-31 Werner Koch <[EMAIL PROTECTED]> uidWerner Koch <[EMAIL PROTEC

Re: Key credentials validation problem

Alexander Ratnikov wrote: > Hi, List. > As a newbie in GnuPG I desperately need some help. Here's my question. > What I have: > 1. User Public Key(created in gnupg) > What I need: > To get using gnupg(or programmatically) key credentials(UserID, KeyID). > The problem is that to get info about key I

Re: [Announce] GnuPG 2.0.9 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Werner Koch wrote the following on 3/26/08 7:10 AM: > Hello! > > We are pleased to announce the availability of a new stable GnuPG-2 > release: Version 2.0.9 > [...] GnuPG v2.0.9 has been configured as follows: Platform: Darwin (i3

[Announce] GnuPG 2.0.9 released

Hello! We are pleased to announce the availability of a new stable GnuPG-2 release: Version 2.0.9 The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It can be used to encrypt data, create digital signatures, help authenticating using Secure Shell and to p