Compilation errors...
Hello, I'm trying to install gnupg-1.9.17 on my Debian spar64 workstation. After several issues (that I managed to resolve ony my own), I am now faced with a showstopper. Here is it is black'n'white: mylinux:/opt/gnupg-1.9.17/agent# make source='call-scd.c' object='call-scd.o' libtool=no \ DEPDIR=.deps depmode=gcc /bin/sh ../scripts/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../gl -I../common -I../intl -DLOCALEDIR=\"/usr/local/share/locale\" -DGNUPG_BINDIR="\"/usr/local/bin\"" -DGNUPG_LIBEXECDIR="\"/usr/local/libexec\"" -DGNUPG_LIBDIR="\"/usr/local/lib/gnupg\"" -DGNUPG_DATADIR="\"/usr/local/share/gnupg\"" -I/usr/include -g -O2 -Wall -c call-scd.c In file included from call-scd.c:34: /usr/include/pth.h:341: warning: `_XOPEN_SOURCE' redefined /usr/include/features.h:133: warning: this is the location of the previous definition call-scd.c: In function `agent_scd_check_aliveness': call-scd.c:409: warning: implicit declaration of function `assuan_set_flag' call-scd.c:409: `ASSUAN_NO_WAITPID' undeclared (first use in this function) call-scd.c:409: (Each undeclared identifier is reported only once call-scd.c:409: for each function it appears in.) make: *** [call-scd.o] Error 1 `ASSUAN_NO_WAITPID' is undeclared. Am I comipiling this thing wrong, or do I need to tweak the "call-scd.c" file to make this work? (My C/C++ skills are limited, but I'm not afraid of any learning curve.) If someone has seen this before, and knows how to go about correcting this problem, I would appreciate any help you can offer. Thanks, Bob __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Incompatibility between GnuPG 1.2 and 1.4?
As requested: $ gpg-1.4.2 -vv mail.asc gpg: armor: BEGIN PGP MESSAGE gpg: armor header: Version: GnuPG v1.2.5 (GNU/Linux) :pubkey enc packet: version 3, algo 16, keyid 4AA7E00CB0BE33B2 data: [3070 bits] data: [3071 bits] gpg: public key is B0BE33B2 gpg: using subkey B0BE33B2 instead of primary key 50F9CA2F You need a passphrase to unlock the secret key for user: "Christian H. Stork (University) <[EMAIL PROTECTED]>" gpg: using subkey B0BE33B2 instead of primary key 50F9CA2F 3072-bit ELG-E key, ID B0BE33B2, created 1999-10-02 (main key ID 50F9CA2F) gpg: public key encrypted data: good DEK :pubkey enc packet: version 3, algo 16, keyid 110C58544A12AF6D data: [2048 bits] data: [2046 bits] gpg: public key is 4A12AF6D :encrypted data packet: length: unknown gpg: using subkey 4A12AF6D instead of primary key 6A6DDB60 gpg: encrypted with 2048-bit ELG-E key, ID 4A12AF6D, created 2001-12-14 "Marc-Andre Lemburg <[EMAIL PROTECTED]>" gpg: encrypted with 3072-bit ELG-E key, ID B0BE33B2, created 1999-10-02 "Christian H. Stork (University) <[EMAIL PROTECTED]>" gpg: CAST5 encrypted data :compressed packet: algo=121 gpg: uncompressing failed: unknown compress algorithm gpg: decryption okay gpg: WARNING: message was not integrity protected So, what's algo 121 ? -- Chris Stork <> Support eff.org! <> http://www.ics.uci.edu/~cstork/ OpenPGP fingerprint: B08B 602C C806 C492 D069 021E 41F3 8C8D 50F9 CA2F ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Incompatibility between GnuPG 1.2 and 1.4?
On Mon, Sep 26, 2005 at 09:23:56PM +0400, Pawel Shajdo wrote: > On Sat, Sep 24, 2005 at 09:41:53AM -0700, Christian Stork wrote: > > gpg: uncompressing failed: unknown compress algorithm > > gpg: WARNING: message was not integrity protected > > I'd be happy to provide more details if that is needed. > What show gpg --version ? The --version output of the encrypting GnuPG (my oringinal 1.2.1 claim was wrong): gpg (GnuPG) 1.2.5 Copyright (C) 2004 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Home: ~/.gnupg Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Hash: MD5, SHA1, RIPEMD160, SHA256 Compression: Uncompressed, ZIP, ZLIB, BZIP2 And I updated my decrypting gpg to 1.4.2 in the meantime: gpg (GnuPG) 1.4.2 Copyright (C) 2005 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Home: ~/.gnupg Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512 Compression: Uncompressed, ZIP, ZLIB, BZIP2 Unfortunately the problems persist. -- Chris Stork <> Support eff.org! <> http://www.ics.uci.edu/~cstork/ OpenPGP fingerprint: B08B 602C C806 C492 D069 021E 41F3 8C8D 50F9 CA2F ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Incompatibility between GnuPG 1.2 and 1.4?
Christian Stork wrote: > As requested: > > So, what's algo 121 ? > According to http://www.ietf.org/rfc/rfc2440.txt, it doesn't exist. The message is probably corrupt. -- Alphax | /"\ Encrypted Email Preferred | \ / ASCII Ribbon Campaign OpenPGP key ID: 0xF874C613 |X Against HTML email & vCards http://tinyurl.com/cc9up| / \ ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Can't check message signature
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hello. Recently I submitted my key to PGP Global Directory and received a verification request. I can't check it't signature, I see the following: OpenPGP Security Info Unverified signature gpg command line and output: C:\\Program Files\\GNU\\GnuPG\\gpg.exe --charset utf8 --verbose --batch - - - --no-tty --status-fd 2 --verify gpg: armor header: Hash: SHA1 gpg: original file name='' gpg: armor header: Version: PGP Universal 2.0.3 gpg: Signature made 09/29/05 19:40:01 using RSA key ID CA57AD7C gpg: WARNING: signature digest conflict in message gpg: Can't check signature: general error What may be a problem? GnuPG 1.4.2, Windows XP SP2, Enigmail 0.92.1.0 - -- Current OpenPGP key ID: 0x500B8987 Fingerprint: E883 045D 36FB 8CA3 8D69 9C79 9E35 3B56 500B 8987 Keyserver to use: sks.keyserver.penguin.de Encrypted mail preferred. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iD8DBQFDPTyAnjU7VlALiYcRA7O5AKC1tovmDY+eIyQoS6AffJI4bZRPjwCeKpob UuyDPqW8WNqj3SgVcd53Crk= =0pX/ -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Can't check message signature
On Fri, Sep 30, 2005 at 05:24:22PM +0400, lusfert wrote: > Hello. > > Recently I submitted my key to PGP Global Directory and received a > verification request. I can't check it't signature, I see the following: > > OpenPGP Security Info > > Unverified signature > > gpg command line and output: > C:\\Program Files\\GNU\\GnuPG\\gpg.exe --charset utf8 --verbose --batch > - - --no-tty --status-fd 2 --verify > gpg: armor header: Hash: SHA1 > gpg: original file name='' > gpg: armor header: Version: PGP Universal 2.0.3 > gpg: Signature made 09/29/05 19:40:01 using RSA key ID CA57AD7C > gpg: WARNING: signature digest conflict in message > gpg: Can't check signature: general error Interesting. This means that the signature is malformed in a particular way. If there is nothing private in it, could you send me the message off-list? David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Incompatibility between GnuPG 1.2 and 1.4?
On Fri, Sep 30, 2005 at 07:36:34PM +0930, Alphax wrote: > Christian Stork wrote: > > As requested: > > > So, what's algo 121 ? > According to http://www.ietf.org/rfc/rfc2440.txt, it doesn't exist. The > message is probably corrupt. But it this happens to all the messages I get from him (by now 6 or so) and why then does gpg 1.2 decrypt the same message without problems. I have gpg 1.2.4 installed on my Mac and it produces the following output on the _identical_ message: $ gpg-1.2.4 mal1.asc gpg: armor: BEGIN PGP MESSAGE gpg: armor header: Version: GnuPG v1.2.5 (GNU/Linux) :pubkey enc packet: version 3, algo 16, keyid 4AA7E00CB0BE33B2 data: [3070 bits] data: [3071 bits] gpg: public key is B0BE33B2 gpg: using secondary key B0BE33B2 instead of primary key 50F9CA2F You need a passphrase to unlock the secret key for user: "Christian H. Stork (University) <[EMAIL PROTECTED]>" gpg: using secondary key B0BE33B2 instead of primary key 50F9CA2F 3072-bit ELG-E key, ID B0BE33B2, created 1999-10-02 (main key ID 50F9CA2F) gpg: public key encrypted data: good DEK :pubkey enc packet: version 3, algo 16, keyid 110C58544A12AF6D data: [2048 bits] data: [2046 bits] gpg: public key is 4A12AF6D :encrypted data packet: length: unknown gpg: using secondary key 4A12AF6D instead of primary key 6A6DDB60 gpg: encrypted with 2048-bit ELG-E key, ID 4A12AF6D, created 2001-12-14 "Marc-Andre Lemburg <[EMAIL PROTECTED]>" gpg: encrypted with 3072-bit ELG-E key, ID B0BE33B2, created 1999-10-02 "Christian H. Stork (University) <[EMAIL PROTECTED]>" gpg: CAST5 encrypted data :compressed packet: algo=1 :literal data packet: mode b, created 1127158105, name="", raw data: 0 bytes gpg: original file name='' :signature packet: algo 17, keyid F37A79CD6A6DDB60 version 3, created 1127158105, md5len 5, sigclass 00 digest algo 2, begin of digest 4f 9d data: [158 bits] data: [160 bits] gpg: old style (PGP 2.x) signature gpg: Signature made Mon Sep 19 12:28:25 2005 PDT using DSA key ID 6A6DDB60 gpg: Good signature from "Marc-Andre Lemburg <[EMAIL PROTECTED]>" gpg: aka "Marc-Andre Lemburg <[EMAIL PROTECTED]>" gpg: key 50F9CA2F: accepted as trusted key gpg: key C3D4D9D4: accepted as trusted key gpg: key DC8492FA: accepted as trusted key gpg: key 61F2C6B1: accepted as trusted key gpg: key EAB24878: accepted as trusted key gpg: key C9A2607F: accepted as trusted key gpg: key 6D2033CA: accepted as trusted key gpg: key 65EB1001: accepted as trusted key gpg: binary signature, digest algorithm SHA1 gpg: decryption okay gpg: WARNING: message was not integrity protected So in contrast to gpg 1.4 this gpg 1.2.4 identifies the compression algo as 1 and decrypts just fine. Could there still be an integrity problem as the warning at the end suggests? -- Chris Stork <> Support eff.org! <> http://www.ics.uci.edu/~cstork/ OpenPGP fingerprint: B08B 602C C806 C492 D069 021E 41F3 8C8D 50F9 CA2F ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Compilation errors...
On Thu, 29 Sep 2005 11:59:44 -0700 (PDT), bob bobby said: > `ASSUAN_NO_WAITPID' is undeclared. Am I comipiling > this thing wrong, or do I need to tweak the You need to update the libassuan development package. You need version 0.6.10 which is the latest released on. You should also get a newer gnupg1.9 tarball: The current one is 1.9.19. Shalom-Salam, Werner ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Can't check message signature
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 David Shaw wrote: > On Fri, Sep 30, 2005 at 05:24:22PM +0400, lusfert wrote: > >>Hello. >> >>Recently I submitted my key to PGP Global Directory and received a >>verification request. I can't check it't signature, I see the following: >> >>OpenPGP Security Info >> >>Unverified signature >> >>gpg command line and output: >>C:\\Program Files\\GNU\\GnuPG\\gpg.exe --charset utf8 --verbose --batch >>- - --no-tty --status-fd 2 --verify >>gpg: armor header: Hash: SHA1 >>gpg: original file name='' >>gpg: armor header: Version: PGP Universal 2.0.3 >>gpg: Signature made 09/29/05 19:40:01 using RSA key ID CA57AD7C >>gpg: WARNING: signature digest conflict in message >>gpg: Can't check signature: general error > > > Interesting. This means that the signature is malformed in a > particular way. If there is nothing private in it, could you send me > the message off-list? I receive message ([PGP Global Directory] Verify Your Key) with such "unverified signature" each time after submitting a key to PGP Global Directory. What is "the message off-list"? Regards - -- Current OpenPGP key ID: 0x500B8987 Fingerprint: E883 045D 36FB 8CA3 8D69 9C79 9E35 3B56 500B 8987 Keyserver to use: sks.keyserver.penguin.de Encrypted mail preferred. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iD8DBQFDPYeNnjU7VlALiYcRAwtTAJ44m9jQilLRh0SsyQgUHtfk5Y1vBwCgicon feDu0RbQiETpmPOGGuibacw= =h/ut -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
