From wk at gnupg.org Thu Dec 1 12:07:53 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Dec 1 12:11:48 2005 Subject: libksba > 0.9.11 + gnupg-1.9.19 'make check' failures on x86_64 In-Reply-To: (Rex Dieter's message of "Wed, 30 Nov 2005 11:51:48 -0600") References: Message-ID: <87br01t6ra.fsf@wheatstone.g10code.de> On Wed, 30 Nov 2005 11:51:48 -0600, Rex Dieter said: > gpgsm: signal Segmentation fault caught ... exiting Can you please run it under gdb or create a core dump. You need to convince gpgsm to use the option --debug-allow-core-dums for example by putting a gpgsm.conf file with that option into tests/ and to set ulimit appropriate. Then please the core file into gdb and run "bt full". Shalom-Salam, Werner From rdieter at math.unl.edu Thu Dec 1 12:49:07 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Thu Dec 1 12:42:58 2005 Subject: libksba > 0.9.11 + gnupg-1.9.19 'make check' failures on x86_64 In-Reply-To: <87br01t6ra.fsf@wheatstone.g10code.de> References: <87br01t6ra.fsf@wheatstone.g10code.de> Message-ID: <438EE333.9090507@math.unl.edu> Werner Koch wrote: > On Wed, 30 Nov 2005 11:51:48 -0600, Rex Dieter said: > > >>gpgsm: signal Segmentation fault caught ... exiting > > > Can you please run it under gdb or create a core dump. You need to > convince gpgsm to use the option --debug-allow-core-dums for example > by putting a gpgsm.conf file with that option into tests/ and to set > ulimit appropriate. Then please the core file into gdb and run "bt > full". Difficult, as I don't have a x86_64 box. This is just the results when trying to build-on/use Fedora Extras' build servers. Do any of the gnupg dev's use/have-access-to any x86_64 boxes? -- Rex From kfitzner at excelcia.org Thu Dec 1 15:21:01 2005 From: kfitzner at excelcia.org (Kurt Fitzner) Date: Thu Dec 1 16:55:42 2005 Subject: GnuPG exit codes Message-ID: <438F06CD.1090103@excelcia.org> I have done some looking at the GnuPG source and it seems to me that GnuPG only ever exits with a code of 0, 1, or 2. I just need to confirm that this is the case and what the exit codes mean. My interpretation is: 0 = success 1 = processing error - the command line was a correct command, but GnuPG ran into some sort of problems while trying to complete the task 2 = command error - GnuPG could not start because it could not correctly interpret the command line Is this correct? Kurt. From wk at gnupg.org Thu Dec 1 17:30:19 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Dec 1 17:36:55 2005 Subject: GnuPG exit codes In-Reply-To: <438F06CD.1090103@excelcia.org> (Kurt Fitzner's message of "Thu, 01 Dec 2005 07:21:01 -0700") References: <438F06CD.1090103@excelcia.org> Message-ID: <87mzjksrtw.fsf@wheatstone.g10code.de> On Thu, 01 Dec 2005 07:21:01 -0700, Kurt Fitzner said: > 0 = success > 1 = processing error - the command line was a correct command, but GnuPG > ran into some sort of problems while trying to complete the task I general any error due to the actual data processing. > 2 = command error - GnuPG could not start because it could not correctly > interpret the command line ... or any other system error like missing files or out of memory. However, there is no clear distinction between the codes and for proper error reporting you are advised to use the --status-fd messages. Salam-Shalom, Werner From sharon.mirsky at gmail.com Thu Dec 1 18:12:20 2005 From: sharon.mirsky at gmail.com (Sharon) Date: Thu Dec 1 20:18:37 2005 Subject: What i need to use my usb-tokens with gnupg? References: Message-ID: kazabe gmail.com> writes: > > Hi > > I need use my usb-tokens with gnupg, but simply dont work. All to i > found is related with smart card readers, and another usb tokens > (aladdin by example). Hi, I am trying to use my Aladdin eToken with GnuPG 1.4.2 for windows. I've noticed that you've said you found information regarding the usage of Aladdin tokens in this environment. I will appreciate if you could forward me to this documentation. If you have any other documentation, tutorials etc. that could help I will appreciate if you could point them out for me. Thanks in advanced, Sharon. From david.kirkby at onetel.net Sat Dec 3 07:01:26 2005 From: david.kirkby at onetel.net (David Kirkby) Date: Tue Dec 6 10:08:00 2005 Subject: gnupg-1.4.2 Excessive warnings when using Sun's cc Message-ID: <439134B6.5090800@onetel.net> I built gnupg-1.4.2 on a Sun Ultra 80 with Solaris 10 and Sun's Studio 11 compiler suite (which is now free). Sun's compiler is generally acknowledged to be stricter than gcc, but it gives a lot of warnings when compiling gnupg-1.4.2 - see below. I'ts a bit worring given the type of software this is to have some many issues in the source. Here's a list of the warnings which I saved by redirecting stderr to a file. # cat warnings.txt "miscutil.c", line 255: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 193 argument : pointer to const unsigned char "strgutil.c", line 291: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 291: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 293: warning: assignment type mismatch: pointer to const char "=" pointer to const unsigned char "strgutil.c", line 298: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 298: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 310: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 310: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 312: warning: assignment type mismatch: pointer to const char "=" pointer to const unsigned char "strgutil.c", line 317: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 317: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 685: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 692: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "strgutil.c", line 692: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 719: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 808: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "strgutil.c", line 813: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 839: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 882: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 892: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 895: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 952: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 968: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "strgutil.c", line 1005: warning: assignment type mismatch: pointer to const char "=" pointer to unsigned char "strgutil.c", line 1040: warning: return value type mismatch "ttyio.c", line 354: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 193 argument : pointer to const unsigned char "argparse.c", line 869: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/stdio_iso.h", line 222 argument : pointer to const unsigned char "iobuf.c", line 630: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "iobuf.c", line 709: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 115 argument : pointer to char "iobuf.c", line 740: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "iobuf.c", line 755: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "iobuf.c", line 762: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "iobuf.c", line 828: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "iobuf.c", line 1592: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "iobuf.c", line 2079: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "iobuf.c", line 2088: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "iobuf.c", line 2108: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "http.c", line 353: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 69 argument : pointer to char "http.c", line 372: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 69 argument : pointer to char "http.c", line 388: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 72 argument : pointer to char "http.c", line 455: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 130 argument : pointer to const unsigned char "http.c", line 462: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "http.c", line 480: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 130 argument : pointer to unsigned char "http.c", line 480: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "http.c", line 484: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "http.c", line 487: warning: assignment type mismatch: pointer to const char "=" pointer to unsigned char "http.c", line 490: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "http.c", line 490: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "http.c", line 498: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "http.c", line 518: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to char "http.c", line 537: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 409 argument : pointer to char "http.c", line 538: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 124 argument : pointer to char "http.c", line 547: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "http.c", line 77 argument : pointer to const unsigned char "http.c", line 556: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 409 argument : pointer to char "http.c", line 559: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "http.c", line 409 argument : pointer to char "http.c", line 562: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 124 argument : pointer to char "http.c", line 574: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "http.c", line 574: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "http.c", line 583: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "http.c", line 596: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "http.c", line 601: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "http.c", line 601: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "http.c", line 79 argument : pointer to unsigned char "http.c", line 622: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 622: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 626: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to const char "http.c", line 626: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 628: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 628: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 634: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 634: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 639: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to const char "http.c", line 639: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 643: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 643: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "http.c", line 450 argument : pointer to char "http.c", line 674: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 130 argument : pointer to unsigned char "http.c", line 674: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "http.c", line 676: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 64 argument : pointer to unsigned char "http.c", line 679: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 131 argument : pointer to unsigned char "http.c", line 679: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "http.c", line 681: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 73 argument : pointer to unsigned char "http.c", line 687: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 131 argument : pointer to unsigned char "http.c", line 687: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "http.c", line 695: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/stdlib_iso.h", line 111 argument : pointer to unsigned char "simple-gettext.c", line 467: warning: empty translation unit "w32reg.c", line 181: warning: empty translation unit "assuan-client.c", line 183: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "assuan-client.c", line 188: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/stdlib_iso.h", line 111 argument : pointer to unsigned char "assuan-client.c", line 196: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "assuan-client.c", line 164 argument : pointer to unsigned char "assuan-client.c", line 215: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "assuan-client.c", line 254: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "assuan-client.c", line 160 argument : pointer to unsigned char "assuan-client.c", line 264: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "assuan-client.c", line 162 argument : pointer to unsigned char "assuan-util.c", line 122: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "mkdtemp.c", line 60: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "mkdtemp.c", line 66: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "md.c", line 411: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "des.c", line 758: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "des.c", line 131 argument : pointer to unsigned char "des.c", line 758: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "des.c", line 131 argument : pointer to unsigned char "blowfish.c", line 485: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "blowfish.c", line 58 argument : pointer to char "elgamal.c", line 134: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "elgamal.c", line 135: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "elgamal.c", line 187: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "elgamal.c", line 195: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "elgamal.c", line 199: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "elgamal.c", line 287: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "rsa.c", line 71: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "rsa.c", line 72: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "primegen.c", line 169: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "primegen.c", line 41 argument : pointer to unsigned char "primegen.c", line 334: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "primegen.c", line 335: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "primegen.c", line 468: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "primegen.c", line 469: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "random.c", line 183: warning: statement not reached "random.c", line 261: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "random.c", line 315: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "random.c", line 325: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "random.c", line 331: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "random.c", line 342: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "random.c", line 464: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 465: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 545: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 546: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 552: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 560: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 561: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "random.c", line 604: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "random.c", line 313 argument : pointer to char "dsa.c", line 98: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "dsa.c", line 104: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "dsa.c", line 108: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "dsa.c", line 149: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "dsa.c", line 150: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/mpi.h", line 137 argument : pointer to char "dsa.c", line 220: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "rndunix.c", line 874: warning: empty translation unit "rndegd.c", line 230: warning: empty translation unit "rndw32.c", line 704: warning: empty translation unit "rmd160.c", line 457: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "rmd160.c", line 176 argument : pointer to char "idea-stub.c", line 141: warning: return value type mismatch "gpgsplit.c", line 476: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "gpgsplit.c", line 491: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "bftest.c", line 96: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 163 argument : pointer to char "bftest.c", line 100: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 165 argument : pointer to char "bftest.c", line 100: warning: argument #3 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 165 argument : pointer to char "bftest.c", line 102: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 166 argument : pointer to char "bftest.c", line 102: warning: argument #3 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 166 argument : pointer to char "g10.c", line 1032: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "../include/util.h", line 185 argument : pointer to char "g10.c", line 1062: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "../include/util.h", line 185 argument : pointer to char "g10.c", line 1282: warning: statement not reached "g10.c", line 1331: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "g10.c", line 1336: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 158 argument : pointer to char "g10.c", line 1350: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "g10.c", line 3759: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "g10.c", line 3821: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to char "build-packet.c", line 212: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "build-packet.c", line 318: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "compress-bz2.c", line 71: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "compress-bz2.c", line 133: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "compress-bz2.c", line 186: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "compress-bz2.c", line 213: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "compress-bz2.c", line 228: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "keyring.c", line 783: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "keyring.c", line 797: warning: return value type mismatch "keyring.c", line 848: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "keyring.c", line 733 argument : pointer to const char "keyring.c", line 848: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "keyring.c", line 733 argument : pointer to const char "keyring.c", line 963: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "keyring.c", line 777 argument : pointer to const char "kbnode.c", line 367: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "mainproc.c", line 648: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to char "mainproc.c", line 842: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "mainproc.c", line 846: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 159 argument : pointer to char "mainproc.c", line 1082: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "mainproc.c", line 1101: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "armor.c", line 282: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 133 argument : pointer to unsigned char "armor.c", line 282: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "armor.c", line 311: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 64 argument : pointer to unsigned char "armor.c", line 345: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 130 argument : pointer to unsigned char "armor.c", line 345: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "armor.c", line 360: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "armor.c", line 222 argument : pointer to unsigned char "armor.c", line 362: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "armor.c", line 982: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 987: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1006: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1019: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1050: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1108: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1114: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1128: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "armor.c", line 1135: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/iobuf.h", line 121 argument : pointer to unsigned char "misc.c", line 1041: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "openfile.c", line 146: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 161 argument : pointer to const char "keyid.c", line 418: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/cipher.h", line 151 argument : pointer to unsigned char "keyid.c", line 418: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/cipher.h", line 151 argument : pointer to unsigned char "keyid.c", line 420: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/cipher.h", line 151 argument : pointer to unsigned char "keyid.c", line 735: warning: assignment type mismatch: pointer to const char "=" pointer to unsigned char "parse-packet.c", line 565: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 115 argument : pointer to char "parse-packet.c", line 566: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "parse-packet.c", line 572: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 115 argument : pointer to char "parse-packet.c", line 573: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "parse-packet.c", line 579: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 115 argument : pointer to char "parse-packet.c", line 582: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/iobuf.h", line 120 argument : pointer to char "parse-packet.c", line 1991: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2000: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2082: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2090: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2179: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2339: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "parse-packet.c", line 2379: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "plaintext.c", line 104: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 161 argument : pointer to char "sig-check.c", line 140: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "sig-check.c", line 141: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "sig-check.c", line 143: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "sig-check.c", line 144: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "status.h", line 123 argument : pointer to unsigned char "sig-check.c", line 316: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to char "keylist.c", line 237: warning: argument #3 is incompatible with prototype: prototype: pointer to const char : "status.h", line 126 argument : pointer to const unsigned char "keylist.c", line 277: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "status.h", line 124 argument : pointer to const unsigned char "keylist.c", line 394: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "status.h", line 124 argument : pointer to const unsigned char "keylist.c", line 395: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "status.h", line 124 argument : pointer to const unsigned char "keylist.c", line 856: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 159 argument : pointer to char "keylist.c", line 988: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 159 argument : pointer to char "keylist.c", line 1149: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "keylist.c", line 1337: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "keylist.c", line 1347: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "cardglue.c", line 285: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "cardglue.c", line 287: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "cardglue.c", line 642: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 647: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 656: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 661: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 671: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 708: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 710: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 712: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 736: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 738: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 740: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "cardglue.c", line 748: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "cardglue.c", line 1061: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "cardglue.c", line 586 argument : pointer to char "card-util.c", line 208: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 160 argument : pointer to const char "card-util.c", line 210: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 41 argument : pointer to const char "card-util.c", line 238: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 240: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 160 argument : pointer to char "card-util.c", line 242: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 41 argument : pointer to char "card-util.c", line 251: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 253: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 160 argument : pointer to char "card-util.c", line 255: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 41 argument : pointer to char "card-util.c", line 347: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 355: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 360: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 376: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "card-util.c", line 382: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 383: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 384: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 387: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 388: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 389: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 185 argument : pointer to char "card-util.c", line 425: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 430: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 435: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 445: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 450: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 455: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 462: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to char "card-util.c", line 479: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 215 argument : pointer to char "card-util.c", line 479: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 215 argument : pointer to char "card-util.c", line 479: warning: argument #4 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 215 argument : pointer to char "card-util.c", line 563: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 592: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 634: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "keyserver-internal.h", line 38 argument : pointer to char "card-util.c", line 640: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "keyserver-internal.h", line 38 argument : pointer to char "card-util.c", line 708: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 777: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 813: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 848: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to const char "card-util.c", line 918: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 963: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 991: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "cardglue.h", line 176 argument : pointer to char "card-util.c", line 1006: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 1008: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "card-util.c", line 1010: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "card-util.c", line 165 argument : pointer to char "app-openpgp.c", line 1897: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "iso7816.h", line 63 argument : pointer to char "app-openpgp.c", line 2419: warning: initializer does not fit or is out of range: 210 "iso7816.c", line 157: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 96 argument : pointer to unsigned char "iso7816.c", line 161: warning: statement not reached "iso7816.c", line 289: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 96 argument : pointer to const unsigned char "iso7816.c", line 306: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 96 argument : pointer to const unsigned char "iso7816.c", line 327: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 98 argument : pointer to const unsigned char "iso7816.c", line 368: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 98 argument : pointer to unsigned char "iso7816.c", line 374: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 98 argument : pointer to const unsigned char "iso7816.c", line 402: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 98 argument : pointer to const unsigned char "iso7816.c", line 429: warning: argument #7 is incompatible with prototype: prototype: pointer to const char : "apdu.h", line 98 argument : pointer to const unsigned char "apdu.c", line 508: warning: statement not reached "apdu.c", line 2312: warning: assignment type mismatch: pointer to function(unsigned short, unsigned short) returning char "=" pointer to void "apdu.c", line 2313: warning: assignment type mismatch: pointer to function(unsigned short, pointer to unsigned char, pointer to unsigned char, unsigned short, pointer to unsigned char, pointer to unsigned short, pointer to unsigned char) returning char "=" pointer to void "apdu.c", line 2314: warning: assignment type mismatch: pointer to function(unsigned short) returning char "=" pointer to void "apdu.c", line 2341: warning: assignment type mismatch: pointer to function(unsigned long, pointer to const void, pointer to const void, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2342: warning: assignment type mismatch: pointer to function(unsigned long) returning long "=" pointer to void "apdu.c", line 2343: warning: assignment type mismatch: pointer to function(unsigned long, pointer to const char, pointer to char, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2348: warning: assignment type mismatch: pointer to function(unsigned long, unsigned long, pointer to struct pcsc_readerstate_s {pointer to const char reader, pointer to void user_data, unsigned long current_state, unsigned long event_state, unsigned long atrlen, array[33] of unsigned char atr}, unsigned long) returning long "=" pointer to void "apdu.c", line 2353: warning: assignment type mismatch: pointer to function(unsigned long, pointer to const char, unsigned long, unsigned long, pointer to unsigned long, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2358: warning: assignment type mismatch: pointer to function(unsigned long, unsigned long, unsigned long, unsigned long, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2363: warning: assignment type mismatch: pointer to function(unsigned long, unsigned long) returning long "=" pointer to void "apdu.c", line 2364: warning: assignment type mismatch: pointer to function(unsigned long, pointer to char, pointer to unsigned long, pointer to unsigned long, pointer to unsigned long, pointer to unsigned char, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2369: warning: assignment type mismatch: pointer to function(unsigned long) returning long "=" pointer to void "apdu.c", line 2370: warning: assignment type mismatch: pointer to function(unsigned long) returning long "=" pointer to void "apdu.c", line 2371: warning: assignment type mismatch: pointer to function(unsigned long, const pointer to struct pcsc_io_request_s {unsigned long protocol, unsigned long pci_len}, pointer to const unsigned char, unsigned long, pointer to struct pcsc_io_request_s {unsigned long protocol, unsigned long pci_len}, pointer to unsigned char, pointer to unsigned long) returning long "=" pointer to void "apdu.c", line 2372: warning: assignment type mismatch: pointer to function(unsigned long, unsigned long) returning long "=" pointer to void "apdu.c", line 2574: warning: return value type mismatch "ccid-driver.c", line 2403: warning: empty translation unit "pkclist.c", line 439: warning: statement not reached "pkclist.c", line 817: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "pkclist.c", line 822: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "pubkey-enc.c", line 201: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 76 argument : pointer to unsigned char "pubkey-enc.c", line 253: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 76 argument : pointer to unsigned char "passphrase.c", line 403: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "passphrase.c", line 771: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "main.h", line 127 argument : pointer to const char "passphrase.c", line 1044: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to char "passphrase.c", line 1052: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to char "passphrase.c", line 1056: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to char "encr-data.c", line 151: warning: argument #2 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 166 argument : pointer to char "encr-data.c", line 151: warning: argument #3 is incompatible with prototype: prototype: pointer to unsigned char : "../include/cipher.h", line 166 argument : pointer to char "encode.c", line 559: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 76 argument : pointer to unsigned char "encode.c", line 738: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 76 argument : pointer to unsigned char "sign.c", line 167: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to char "sign.c", line 195: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to char "sign.c", line 231: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/cipher.h", line 133 argument : pointer to const char "sign.c", line 477: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "sign.c", line 479: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "/usr/include/iso/stdio_iso.h", line 210 argument : pointer to unsigned char "revoke.c", line 650: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "../include/util.h", line 185 argument : pointer to char "revoke.c", line 658: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 161 argument : pointer to char "keyedit.c", line 187: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to const unsigned char "keyedit.c", line 269: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 41 argument : pointer to char "keyedit.c", line 316: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 394: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to char "keyedit.c", line 2493: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "keyedit.c", line 2740: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 2839: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 2865: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 3098: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 4256: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "keyedit.c", line 4307: warning: argument #1 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/ttyio.h", line 40 argument : pointer to char "import.c", line 712: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 159 argument : pointer to char "import.c", line 1097: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 159 argument : pointer to char "trustdb.c", line 1348: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "../include/util.h", line 157 argument : pointer to char "trustdb.c", line 2302: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "../include/memory.h", line 63 argument : pointer to const unsigned char "tdbio.c", line 1171: warning: assignment type mismatch: pointer to const unsigned char "=" pointer to const char "tdbio.c", line 1348: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "tdbio.c", line 148 argument : pointer to unsigned char "keygen.c", line 574: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to char "keygen.c", line 618: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to char "keygen.c", line 684: warning: argument #3 is incompatible with prototype: prototype: pointer to const unsigned char : "packet.h", line 446 argument : pointer to const char "keygen.c", line 727: warning: statement not reached "keygen.c", line 2270: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "keygen.c", line 2283: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "../include/util.h", line 185 argument : pointer to char "keygen.c", line 2335: warning: argument #1 is incompatible with prototype: prototype: pointer to unsigned char : "../include/util.h", line 185 argument : pointer to char "keygen.c", line 3523: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3523: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3525: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3525: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3530: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3530: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3535: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3535: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3540: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3540: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3544: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3544: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keygen.c", line 3547: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "../include/util.h", line 205 argument : pointer to unsigned char "keygen.c", line 3547: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "keyserver.c", line 361: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "keyserver.c", line 168 argument : pointer to unsigned char "keyserver.c", line 696: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 201 argument : pointer to unsigned char "keyserver.c", line 697: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "keyserver.c", line 697: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 201 argument : pointer to unsigned char "keyserver.c", line 702: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 201 argument : pointer to unsigned char "keyserver.c", line 703: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 69 argument : pointer to unsigned char "keyserver.c", line 703: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 201 argument : pointer to unsigned char "keyserver.c", line 711: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "../include/util.h", line 201 argument : pointer to unsigned char "keyserver.c", line 713: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "keyserver.c", line 772: warning: argument #1 is incompatible with prototype: prototype: pointer to char : "keyserver.c", line 451 argument : pointer to unsigned char "keyserver.c", line 1277: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "gpgkeys_oldhkp.c", line 275: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char "gpgkeys_oldhkp.c", line 276: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_oldhkp.c", line 280: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_oldhkp.c", line 282: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char "gpgkeys_oldhkp.c", line 601: warning: argument #2 is incompatible with prototype: prototype: pointer to char : "gpgkeys_oldhkp.c", line 424 argument : pointer to unsigned char "gpgkeys_finger.c", line 327: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char "gpgkeys_finger.c", line 328: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_finger.c", line 331: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_finger.c", line 333: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char "gpgkeys_http.c", line 93: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char "gpgkeys_http.c", line 94: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_http.c", line 98: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : "/usr/include/iso/string_iso.h", line 71 argument : pointer to unsigned char "gpgkeys_http.c", line 100: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : "ksutil.h", line 103 argument : pointer to unsigned char # -- David Kirkby, G8WRB Please check out http://www.g8wrb.org/ of if you live in Essex http://www.southminster-branch-line.org.uk/ From rdieter at math.unl.edu Mon Dec 5 15:46:32 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue Dec 6 10:14:06 2005 Subject: Latest (stable) gpgme, 1.0.3 or 1.1.0? Message-ID: http://www.gnupg.org/ Says gpgme-1.0.3 is the latest, but gpgme-1.1.0 is available from the ftp/download site. Which is the latest (stable) version? If 1.0.3, then what is 1.1.0? -- Rex From wk at gnupg.org Tue Dec 6 10:50:53 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 6 10:57:41 2005 Subject: scdaemon w pcsc (towitoko usb) problem In-Reply-To: <20051205115800.GB4663@intevation.de> (Bernhard Reiter's message of "Mon, 5 Dec 2005 12:58:00 +0100") References: <20051205115800.GB4663@intevation.de> Message-ID: <87hd9mpn9e.fsf@wheatstone.g10code.de> On Mon, 5 Dec 2005 12:58:00 +0100, Bernhard Reiter said: > scdaemon[10852]: handler for fd -1 started > scdaemon[10852]: error sending PC/SC OPEN request: Broken pipe We use a wrapper program (pcsc-wrapper) to overcome problems with pcsclite (it uses pthreads and that conflicts with our use of Pth). It seems that this wrapper program died to early or is too old. I suggest to replace pcsc-wrapper by a script running the real pcsc-wrapper under strace - this is the fastest method to see what went wrong. ========pcsc-wrapper=== #!/bin/sh strace -o /tmp/pcsc-wrapper.log /usr/local/lib/gnupg/pcsc-wrapper.real "$@" ========= Salam-Shalom, Werner From ahasenack at terra.com.br Mon Dec 5 13:34:21 2005 From: ahasenack at terra.com.br (Andreas Hasenack) Date: Tue Dec 6 12:35:18 2005 Subject: make check fails on x86_64 (1.9.19) Message-ID: <20051205123420.GB4834@conectiva.com.br> Attached are two log files resulting from make check being run with "--verbose" in the runtest script and "--no-echo" removed from it. The first test fails on x86_64 and I have no idea why. Could somebody shed some light into this please? Thanks in advance. -------------- next part -------------- make check-TESTS make[1]: Entering directory `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests' gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=5' expecting OK read_assuan: read "OK" read_assuan: read " " sending `SIGN' expecting OK gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: DBG: adding certificates at level 1 gpgsm: signature created read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S SIG_CREATED S 1 2 00 20021202T132959 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " sending `RESET' expecting OK read_assuan: read "OK" read_assuan: read " " sending `INPUT FD=6' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=7' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-12-02 13:29:59 using certificate ID 33BDB76E gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-12-02 20021202T132959 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " asschk: files match gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=5' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-12-02 13:29:59 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-12-02 20021202T132959 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " goodsig=1 trusted=1 asschk: files match sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " PASS: sm-sign+verify gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=5' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:46 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T122246 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " asschk: files match gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `MESSAGE FD=5' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:54 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T122254 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=8' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=10' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:46 using certificate ID 33BDB76E gpgsm: invalid signature: message digest attribute does not match calculated one read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S BADSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=1 goodsig=0 trusted=0 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=13' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:38:22 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T123822 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=16' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-07 12:38:22 using certificate ID 33BDB76E gpgsm: invalid signature: Bad signature read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S BADSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=1 goodsig=0 trusted=0 sending `BYE' expecting OK read_assuan: read "OK closing connection " PASS: sm-verify ================== All 2 tests passed ================== make[1]: Leaving directory `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests' -------------- next part -------------- make check-TESTS make[1]: Entering directory `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests' gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=4' expecting OK read_assuan: read "OK" read_assuan: read " " sending `SIGN' expecting OK gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: DBG: adding certificates at level 1 gpgsm: signature created read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S SIG_CREATED S 1 2 00 20021202T132959 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " sending `RESET' expecting OK read_assuan: read "OK" read_assuan: read " " sending `INPUT FD=5' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=6' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: no signature value available read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " goodsig=0 trusted=0 FAIL: sm-sign+verify gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=4' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:46 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T122246 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " asschk: files match gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=3' expecting OK read_assuan: read "OK" read_assuan: read " " sending `MESSAGE FD=4' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:54 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T122254 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=7' expecting OK read_assuan: read "OK" read_assuan: read " " sending `OUTPUT FD=9' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:22:46 using certificate ID 33BDB76E gpgsm: invalid signature: message digest attribute does not match calculated one read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S BADSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=1 goodsig=0 trusted=0 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=12' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-08 12:38:22 using certificate ID 33BDB76E gpgsm: can't connect to `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests/S.gpg-agent': No such file or directory gpgsm: CRLs not checked due to --disable-crl-checks option gpgsm: Good signature from "/CN=test cert 1/OU=Aegypten Project/O=g10 Code GmbH/L=D?sseldorf/C=DE" read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S PROGRESS starting_agent ? 0 0" read_assuan: read " " read_assuan: read "S GOODSIG" read_assuan: read " " read_assuan: read "S VALIDSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E 2002-08-08 20020808T123822 20021203T093638" read_assuan: read " " read_assuan: read "S TRUST_FULLY" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=0 goodsig=1 trusted=1 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " gpgsm: WARNING: running with faked system time: 2002-12-02 13:29:59 read_assuan: read "OK GNU Privacy Guard's S/M server 1.9.19 ready" read_assuan: read " " sending `INPUT FD=15' expecting OK read_assuan: read "OK" read_assuan: read " " sending `VERIFY' expecting OK gpgsm: Signature made 2002-08-07 12:38:22 using certificate ID 33BDB76E gpgsm: invalid signature: Bad signature read_assuan: read "S NEWSIG" read_assuan: read " " read_assuan: read "S BADSIG 3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E" read_assuan: read " " read_assuan: read "OK" read_assuan: read " " badsig=1 goodsig=0 trusted=0 sending `BYE' expecting OK read_assuan: read "OK closing connection" read_assuan: read " " PASS: sm-verify ====================================== 1 of 2 tests failed Please report to gnupg-devel@gnupg.org ====================================== make[1]: *** [check-TESTS] Error 1 make[1]: Leaving directory `/home/andreas/rpm/gnupg2/BUILD/gnupg-1.9.19/tests' make: *** [check-am] Error 2 From wk at gnupg.org Tue Dec 6 12:30:55 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 6 12:36:54 2005 Subject: Latest (stable) gpgme, 1.0.3 or 1.1.0? In-Reply-To: (Rex Dieter's message of "Mon, 05 Dec 2005 08:46:32 -0600") References: Message-ID: <87fyp6o428.fsf@wheatstone.g10code.de> On Mon, 05 Dec 2005 08:46:32 -0600, Rex Dieter said: > http://www.gnupg.org/ Says gpgme-1.0.3 is the latest, but gpgme-1.1.0 is > available from the ftp/download site. Which is the latest (stable) > version? If 1.0.3, then what is 1.1.0? Odd minor numbers are commonly used to declare development versions; thus 1.1.0 is actually a development version. Anyway, neither API nor ABI changed and we use 1.1.0 regulary, so there is nothing which speaks against 1.1.0. The next version will likely be 1.2.0 however we have to solve some glib issues for W32 first. Salam-Shalom, Werner From wk at gnupg.org Tue Dec 6 12:36:59 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 6 12:41:54 2005 Subject: gnupg-1.4.2 Excessive warnings when using Sun's cc In-Reply-To: <439134B6.5090800@onetel.net> (David Kirkby's message of "Sat, 03 Dec 2005 06:01:26 +0000") References: <439134B6.5090800@onetel.net> Message-ID: <87bqzuo3s4.fsf@wheatstone.g10code.de> On Sat, 03 Dec 2005 06:01:26 +0000, David Kirkby said: > I built gnupg-1.4.2 on a Sun Ultra 80 with Solaris 10 and Sun's Studio > 11 compiler suite (which is now free). Sun's compiler is generally > acknowledged to be stricter than gcc, but it gives a lot of warnings > when compiling gnupg-1.4.2 - see below. Those signed/unsigned warning are well known and harmless. If you tell me a compiler option to suppress these warning I will add this as a default option for this compiler. We already did this for gcc 4 which also complains about it. GnuPG 1.9 has been changed to to solve the unsigend/signed conflicts (needs quite some casts and I still wonder whether this is really for the good). We won't change 1.4.2 as this will for sure introduce bugs. BTW, now that some Sun stuff seems to be free, anyone thinking of implementing funopen in their libc? Shalom-Salam, Werner From wk at gnupg.org Tue Dec 6 12:38:42 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 6 12:42:04 2005 Subject: What i need to use my usb-tokens with gnupg? In-Reply-To: (sharon.mirsky@gmail.com's message of "Thu, 1 Dec 2005 17:12:20 +0000 (UTC)") References: Message-ID: <877jaio3p9.fsf@wheatstone.g10code.de> On Thu, 1 Dec 2005 17:12:20 +0000 (UTC), Sharon said: > I am trying to use my Aladdin eToken with GnuPG 1.4.2 for windows. I've noticed You can't use it with gpg unless you manage to implement the OpenPGP application on that token. Salam-Shalom, Werner From bernhard at intevation.de Mon Dec 5 12:58:00 2005 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue Dec 6 12:53:15 2005 Subject: scdaemon w pcsc (towitoko usb) problem Message-ID: <20051205115800.GB4663@intevation.de> Using scdaemon (GnuPG) 1.9.19 (1.9.19-0kk3) on GNU/Linux ppc Debian sarge. (Big engian I think.) scdaemon does not seem to like the pcsc connection, the log has an error message right after starting it up: scdaemon --disable-ccid --debug-all --pcsc-driver /usr/lib/libpcsclite.so.1.0.0 --server scdaemon[10852]: handler for fd -1 started scdaemon[10852]: error sending PC/SC OPEN request: Broken pipe pcscd -af does not indicate a connect. Without using the agent, I can access the driver over pcsc allright, which I can see when using gnupg 1.4.2, like gpg --disable-ccid --card-status --pcsc-driver /usr/lib/libpcsclite.so.1.0.0 --no-use-agent pcscd -af indicates a connect that way. Any ideas? Bernhard From zix_ccbt1 at yahoo.ca Mon Dec 5 21:16:53 2005 From: zix_ccbt1 at yahoo.ca (ssdfsdlfk sldkfjsdlfksjdlfk) Date: Tue Dec 6 14:05:36 2005 Subject: Large PGP keyrings available for testing purposes Message-ID: <20051205201653.78923.qmail@web60622.mail.yahoo.com> Hi everyone, I was wondering if any of you had some large PGP pub keyrings of sizes 500, 1000, or 2000 that you could send me for testing purposes. I'm performance testing my application that is using GnuPG, and I need to test with large keyrings. Any help would be appreciated. Thanks, Michael PS: If any of the email addresses for the keys are valid, the users will not receive mail since I am using a driver-sink for my tests. __________________________________________________________ Find your next car at http://autos.yahoo.ca From rdieter at math.unl.edu Tue Dec 6 14:09:37 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue Dec 6 14:09:16 2005 Subject: gpgme-1.0.3 'make check' failure. Should I be worried? Message-ID: <43958D91.6060505@math.unl.edu> Building gpgme-1.0.3 (against gnupg-1.2.6, libksba-0.9.13, gnupg2-1.9.19) I'm seeing a failure when issuing 'make check' (in t-keylist) after a successful build (appended). Should I be worried that something is build/configured incorrectly? -- Rex -------------------------------------------------------- make[3]: Entering directory `/usr/local/tmp/BUILD/gpgme-1.0.3/tests/gpgsm' PASS: t-import Key has unexpected number of user IDs FAIL: t-keylist -----BEGIN ENCRYPTED MESSAGE----- MIAGCSqGSIb3DQEHA6CAMIACAQAxggEJMIIBBQIBADBwMGsxCzAJBgNVBAYTAkRF MRMwEQYDVQQHFApE/HNzZWxkb3JmMRYwFAYDVQQKEw1nMTAgQ29kZSBHbWJIMRkw FwYDVQQLExBBZWd5cHRlbiBQcm9qZWN0MRQwEgYDVQQDEwt0ZXN0IGNlcnQgMQIB ADALBgkqhkiG9w0BAQEEgYDFuyO26Ipo2UZks58ucayWsiD9j52U8GcyVITvI8vI oUsBXivYP4wdCPsbuaPPFw78BSmZ1Kg2nhlye9iaZ1kmAujc23zgo8oD4wgRJLFx gfapH55asHfji2OA0ftS09jV8ev0ti2I6WKlqt0jVC+eOcTEqrI4qA0wIEQ6xtwZ 3TCABgkqhkiG9w0BBwEwFAYIKoZIhvcNAwcECHxSmTXvA1VZoIAECNUlOR/EPiN+ BAhYRKrq9k5mCAAAAAAAAAAAAAA= -----END ENCRYPTED MESSAGE----- From rdieter at math.unl.edu Tue Dec 6 14:26:26 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue Dec 6 14:31:06 2005 Subject: make check fails on x86_64 (1.9.19) In-Reply-To: <20051205123420.GB4834__30345.8449351185$1133869088$gmane$org@conectiva.com.br> References: <20051205123420.GB4834__30345.8449351185$1133869088$gmane$org@conectiva.com.br> Message-ID: Andreas Hasenack wrote: > Attached are two log files resulting from make check being run with > "--verbose" in the runtest script and "--no-echo" removed from it. > > The first test fails on x86_64 and I have no idea why. I've seen the same thing on x86_64 builds. Unfortunately, I have no x86_64 box, but am packaging gnupg2 for Fedora Extras (which builds for x86_64 too). Only thing I've been able to determine is that the 'make check' failures began with upgrading libksba beyond 0.9.11. gnupg2 hacked(*) to build against libksba-0.9.11 passes 'make check'. libksba-0.9.12/0.9.13 fails the "sm-sign+verify" test. My failed build log is available at: http://buildsys.fedoraproject.org/logs/fedora-development-extras/1443-gnupg2-1.9.19-3.fc5/x86_64/ -- Rex (*) my hack was simple: sed -i -e 's|^NEED_KSBA_VERSION=.*|NEED_KSBA_VERSION=0.9.11|' \ configure.ac configure From rdieter at math.unl.edu Tue Dec 6 15:03:53 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue Dec 6 15:03:33 2005 Subject: gpgme-1.0.3 'make check' failure. In-Reply-To: <43958D91.6060505@math.unl.edu> References: <43958D91.6060505@math.unl.edu> Message-ID: <43959A49.1010706@math.unl.edu> Rex Dieter wrote: > Building gpgme-1.0.3 (against gnupg-1.2.6, libksba-0.9.13, > gnupg2-1.9.19) I'm seeing a failure when issuing 'make check' (in > t-keylist) after a successful build (appended). Should I be worried > that something is build/configured incorrectly? > > -- Rex > > -------------------------------------------------------- > make[3]: Entering directory `/usr/local/tmp/BUILD/gpgme-1.0.3/tests/gpgsm' > PASS: t-import > Key has unexpected number of user IDs > FAIL: t-keylist Ah, thought this looked familiar... I just slightly modified a patch posted here for gpgme-1.1.0 for the same problem. -- Rex -------------- next part -------------- --- gpgme-1.1.0/tests/gpgsm/t-keylist.c.tests 2005-09-08 09:42:32.000000000 -0500 +++ gpgme-1.1.0/tests/gpgsm/t-keylist.c 2005-10-11 09:24:40.000000000 -0500 @@ -44,6 +44,7 @@ char *issuer_name; char *chain_id; char *uid; + char *email; gpgme_validity_t validity; unsigned int key_length; } @@ -53,7 +54,7 @@ "CN=test cert 1,OU=Aegypten Project,O=g10 Code GmbH,L=D\xc3\xbcsseldorf,C=DE", "3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E", "CN=test cert 1,OU=Aegypten Project,O=g10 Code GmbH,L=D\xc3\xbcsseldorf,C=DE", - GPGME_VALIDITY_ULTIMATE, 1024 + NULL, GPGME_VALIDITY_ULTIMATE, 1024 }, { "DFA56FB5FC41E3A8921F77AD1622EEFD9152A5AD", 0, 909684190, 1009821790, "01", "1.2.840.113549.1.9.1=#63657274696679407063612E64666E2E6465," @@ -63,7 +64,7 @@ "1.2.840.113549.1.9.1=#63657274696679407063612E64666E2E6465," "CN=DFN Top Level Certification Authority,OU=DFN-PCA," "O=Deutsches Forschungsnetz,C=DE", - GPGME_VALIDITY_NEVER, 2048 + "", GPGME_VALIDITY_NEVER, 2048 }, { "2C8F3C356AB761CB3674835B792CDA52937F9285", 0, 973183644, 1009735200, "15", "1.2.840.113549.1.9.1=#63657274696679407063612E64666E2E6465," @@ -73,7 +74,7 @@ "1.2.840.113549.1.9.1=#63657274696679407063612E64666E2E6465," "CN=DFN Server Certification Authority,OU=DFN-PCA," "O=Deutsches Forschungsnetz,C=DE", - GPGME_VALIDITY_UNKNOWN, 2048 + "", GPGME_VALIDITY_UNKNOWN, 2048 }, { NULL } }; @@ -286,7 +287,8 @@ exit (1); } - if (!key->uids || key->uids->next) + /* Be tolerant against a missing email (ie, older gpgsm versions). */ + if (!key->uids || (key->uids->next && !keys[i].email)) { fprintf (stderr, "Key has unexpected number of user IDs\n"); exit (1); @@ -336,6 +338,13 @@ key->uids->uid); exit (1); } + if (key->uids->next && strcmp (key->uids->next->uid, keys[i].email)) + { + fprintf (stderr, "Unexpected email in user ID: %s\n", + key->uids->next->uid); + exit (1); + } + gpgme_key_unref (key); i++; From david.kirkby at onetel.net Tue Dec 6 15:08:00 2005 From: david.kirkby at onetel.net (David Kirkby) Date: Tue Dec 6 15:08:19 2005 Subject: gnupg-1.4.2 Excessive warnings when using Sun's cc In-Reply-To: <87bqzuo3s4.fsf@wheatstone.g10code.de> References: <439134B6.5090800@onetel.net> <87bqzuo3s4.fsf@wheatstone.g10code.de> Message-ID: <43959B40.7000502@onetel.net> Werner Koch wrote: > On Sat, 03 Dec 2005 06:01:26 +0000, David Kirkby said: > > >>I built gnupg-1.4.2 on a Sun Ultra 80 with Solaris 10 and Sun's Studio >>11 compiler suite (which is now free). Sun's compiler is generally >>acknowledged to be stricter than gcc, but it gives a lot of warnings >>when compiling gnupg-1.4.2 - see below. > > > Those signed/unsigned warning are well known and harmless. There is not only signed/unsigned warnings. The list is long so finding all the others is not easy, but: "ccid-driver.c", line 2403: warning: empty translation unit "pkclist.c", line 439: warning: statement not reached are two I spotted > If you > tell me a compiler option to suppress these warning I will add this as > a default option for this compiler. We already did this for gcc 4 > which also complains about it. I don't think finding a compiler option is the right approach to take. Once you go start going down that slippery slope, you will probably live to regret it. Others (myself included) manage to write large bits of C that are okay with -Wall on gcc. > GnuPG 1.9 has been changed to to solve the unsigend/signed conflicts > (needs quite some casts and I still wonder whether this is really for > the good). But why does the underlying source need to many casts to avoid the warnings? I know sometimes casts are necessary (particulary with things that have void in them, such as fread where you need to cast the pointer to void). But there should be no need for loads of unsigned/signed mismatches. -- David Kirkby, G8WRB Please check out http://www.g8wrb.org/ of if you live in Essex http://www.southminster-branch-line.org.uk/ From jam at jamux.com Tue Dec 6 15:47:58 2005 From: jam at jamux.com (John A. Martin) Date: Tue Dec 6 15:54:09 2005 Subject: Large PGP keyrings available for testing purposes References: <20051205201653.78923.qmail__40312.1472838849$1133874535$gmane$org@web60622.mail.yahoo.com> Message-ID: <87bqzujn8h.fsf@athene.jamux.com> >>>>> "Michael" == ssdfsdlfk sldkfjsdlfksjdlfk >>>>> "Large PGP keyrings available for testing purposes" >>>>> Mon, 5 Dec 2005 15:16:53 -0500 (EST) Michael> Hi everyone, Michael> I was wondering if any of you had some large PGP pub Michael> keyrings of sizes 500, 1000, or 2000 that you could send Michael> me for testing purposes. I'm performance testing my Michael> application that is using GnuPG, and I need to test with Michael> large keyrings. Any help would be appreciated. The Debian keyrings have more than 1100 keys. ,---- README for the debian-keyring package ===================================== .... Getting debian-keyring.{gpg,pgp} -------------------------------- The current versions of debian-keyring.pgp and debian-keyring.gpg are always available via rsync from keyring.debian.org (module keyrings). There is also a (possibly slightly out-of-date) version available on your nearest debian mirror in debian/doc/debian-keyring.tar.gz and as the debian-keyring package. .... The tarball and Debian package are provided for user convenience and are not necessarily in sync with keyring.debian.org. `---- HTH jam -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 154 bytes Desc: not available Url : /pipermail/attachments/20051206/46584b85/attachment.pgp From bernhard at intevation.de Tue Dec 6 15:58:59 2005 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue Dec 6 16:34:03 2005 Subject: solved (was: scdaemon w pcsc (towitoko usb) problem) Message-ID: <20051206145859.GI6193@intevation.de> Werner wrote: | On Mon, 5 Dec 2005 12:58:00 +0100, Bernhard Reiter said: | | > scdaemon[10852]: handler for fd -1 started | > scdaemon[10852]: error sending PC/SC OPEN request: Broken pipe | | We use a wrapper program (pcsc-wrapper) to overcome problems with | pcsclite (it uses pthreads and that conflicts with our use of Pth). | It seems that this wrapper program died to early or is too old. I | suggest to replace pcsc-wrapper by a script running the real | pcsc-wrapper under strace - this is the fastest method to see what | went wrong. Indeed I saw that "pcsc-wrapper" is missing completely, it was dropped out of -kk packaging, Changelog entry, by Bernhard H.: * removed /usr/lib/gnupg/pcsc-wrapper as it's no longer built It used to be in the gpgsm Debian Package, together with scdaemon. Thinking about this: scdaemon probably is used by the agent for OpenPGP, too, so it would make some sense to put pcsc-wrapper and scdaemon into the gnupg-agent package. Werner: Can you confirm? Bernhard H.: If Werner confirms, we need to improve that package and also send the diff to Debian "gnupg2" source, they are still at 1.9.15-6. Werner: I suggest to at least check for the existence of pcsc-wrapper to give a better error message. Bernhard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20051206/e306a858/attachment.pgp From ahasenack at terra.com.br Tue Dec 6 16:55:36 2005 From: ahasenack at terra.com.br (Andreas Hasenack) Date: Tue Dec 6 16:55:20 2005 Subject: make check fails on x86_64 (1.9.19) In-Reply-To: References: <20051205123420.GB4834__30345.8449351185$1133869088$gmane$org@conectiva.com.br> Message-ID: <20051206155535.GG11769@conectiva.com.br> On Tue, Dec 06, 2005 at 07:26:26AM -0600, Rex Dieter wrote: > Andreas Hasenack wrote: > >Attached are two log files resulting from make check being run with > >"--verbose" in the runtest script and "--no-echo" removed from it. > > > >The first test fails on x86_64 and I have no idea why. > > I've seen the same thing on x86_64 builds. Unfortunately, I have no > x86_64 box, but am packaging gnupg2 for Fedora Extras (which builds for > x86_64 too). Only thing I've been able to determine is that the 'make > check' failures began with upgrading libksba beyond 0.9.11. gnupg2 I'm using libksba 0.9.13 here (forgot to mention it before). From wk at gnupg.org Tue Dec 6 16:58:45 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 6 17:01:55 2005 Subject: solved In-Reply-To: <20051206145859.GI6193@intevation.de> (Bernhard Reiter's message of "Tue, 6 Dec 2005 15:58:59 +0100") References: <20051206145859.GI6193@intevation.de> Message-ID: <87fyp6md3e.fsf@wheatstone.g10code.de> On Tue, 6 Dec 2005 15:58:59 +0100, Bernhard Reiter said: > it was dropped out of -kk packaging, Changelog entry, by Bernhard H.: > * removed /usr/lib/gnupg/pcsc-wrapper as it's no longer built Hmmm, it is important. > It used to be in the gpgsm Debian Package, together with scdaemon. > Thinking about this: scdaemon probably is used by the agent > for OpenPGP, too, so it would make some sense to put pcsc-wrapper > and scdaemon into the gnupg-agent package. > Werner: Can you confirm? No, this is not a good idea. gpg-agent is useful on its own and scdaemon may be used without gpg-agent. > Bernhard H.: If Werner confirms, we need to improve that package > and also send the diff to Debian "gnupg2" source, > they are still at 1.9.15-6. The pscs-wrapper needs to be packaged with scdaemon - it is the only package which needs it. It is similar to dirmngr where we need a wrapper for LDAP for the same reason (thread library conflicts). > Werner: I suggest to at least check for the existence of pcsc-wrapper > to give a better error message. Will do so. Shalom-Salam, Werner From beebe at math.utah.edu Tue Dec 6 16:01:02 2005 From: beebe at math.utah.edu (Nelson H. F. Beebe) Date: Tue Dec 6 18:34:45 2005 Subject: Large PGP keyrings available for testing purposes Message-ID: Michael asks about large PGP keyrings for testing. Try this one: ftp://ftp.gnu.org/gnu/gnu-keyring.gpg Here is what I just found for an account that previously had not registered those keys: % pgp -ka gnu-keyring.gpg ... Added : 173 new key(s) 2368 new signatures(s) 306 new user ID(s) 13 new revocation(s) ------------------------------------------------------------------------------- - Nelson H. F. Beebe Tel: +1 801 581 5254 - - University of Utah FAX: +1 801 581 4148 - - Department of Mathematics, 110 LCB Internet e-mail: beebe@math.utah.edu - - 155 S 1400 E RM 233 beebe@acm.org beebe@computer.org - - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ - ------------------------------------------------------------------------------- From wk at gnupg.org Wed Dec 7 11:46:34 2005 From: wk at gnupg.org (Werner Koch) Date: Wed Dec 7 11:51:59 2005 Subject: gnupg-1.4.2 Excessive warnings when using Sun's cc In-Reply-To: <43959B40.7000502@onetel.net> (David Kirkby's message of "Tue, 06 Dec 2005 14:08:00 +0000") References: <439134B6.5090800@onetel.net> <87bqzuo3s4.fsf@wheatstone.g10code.de> <43959B40.7000502@onetel.net> Message-ID: <87fyp5kwvp.fsf@wheatstone.g10code.de> On Tue, 06 Dec 2005 14:08:00 +0000, David Kirkby said: > "ccid-driver.c", line 2403: warning: empty translation unit Well, undefing a module is easier than makefile magic. > "pkclist.c", line 439: warning: statement not reached Well, some compilers choke if there is no return statement because they can't analyse the previous case statement. I have added a NOTREACHED comment. > I don't think finding a compiler option is the right approach to take. > Once you go start going down that slippery slope, you will probably live > to regret it. We introduced some severe bugs in 1.9 while changing the signed/unsigned things. It was hard to find them even that the number of changes in 1.9 are less than those we would need in 1.4. > Others (myself included) manage to write large bits of C that are okay > with -Wall on gcc. GnuPG used to compile without any warnings with older GCC versions (IIRC < gcc 3.3) and once the GNU standards actually said: Don't care about signed/unsigned mismatches. Actually we build using -Wall -Wcast-align -Wshadow -Wstrict-prototypes -Wformat-nonliteral without any warnings and only added -Wno-pointer-sign recently. I know that these warnings are annoying and dangerous because you may the not notice real problems. Thus my question on a compiler option to disable this warning. > But why does the underlying source need to many casts to avoid the > warnings? I know sometimes casts are necessary (particulary with things The main reason is that GnuPG "unsigend char *" (or typedefed as "byte") and most string functiosn take and return "char *". This isued to be no problem and actually helped a lot to avoid security problems: char *foo; if (isdigit (*foo)) will at least segv on many machines if foo is not unsigned and its referenced value is > 127. A proposed solution is to use a cast - however casts are evil in themself and should be avoided if at all possible. We changed this by avoiding the ctype.h macros or by firsttesting with isascii(). > that have void in them, such as fread where you need to cast the pointer > to void). But there should be no need for loads of unsigned/signed > mismatches. fread is just fine: -- Function: size_t fread (void *DATA, size_t SIZE, size_t COUNT, FILE *STREAM) No need to cast any data pointer. Shalom-Salam, Werner From bernhard at intevation.de Tue Dec 6 18:19:17 2005 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed Dec 7 12:12:04 2005 Subject: solved In-Reply-To: <87fyp6md3e.fsf@wheatstone.g10code.de> References: <20051206145859.GI6193@intevation.de> <87fyp6md3e.fsf@wheatstone.g10code.de> Message-ID: <20051206171917.GL6193@intevation.de> Am 6. Dec 2005 um 16:58:45 schrieb Werner Koch: > On Tue, 6 Dec 2005 15:58:59 +0100, Bernhard Reiter said: > > > it was dropped out of -kk packaging, Changelog entry, by Bernhard H.: > > * removed /usr/lib/gnupg/pcsc-wrapper as it's no longer built > > Hmmm, it is important. Good to know, we will correct this problem. > > It used to be in the gpgsm Debian Package, together with scdaemon. > > Thinking about this: scdaemon probably is used by the agent > > for OpenPGP, too, so it would make some sense to put pcsc-wrapper > > and scdaemon into the gnupg-agent package. > > Werner: Can you confirm? > > No, this is not a good idea. gpg-agent is useful on its own and > scdaemon may be used without gpg-agent. So you are saying that scdaemon should be a package on its own? Currently it is put in the gpgsm package. Which application is using scdaemon, besides gpg-agent for openpgp and smime access over pcsc? > > Bernhard H.: If Werner confirms, we need to improve that package > > and also send the diff to Debian "gnupg2" source, > > they are still at 1.9.15-6. > > The pscs-wrapper needs to be packaged with scdaemon - it is the only > package which needs it. It is similar to dirmngr where we need a > wrapper for LDAP for the same reason (thread library conflicts). Yes, my suggestion was to move scdaemon and pscs-wrapper to gnupg-agent and not keep it in gpgsm for Debian packaging. > > Werner: I suggest to at least check for the existence of pcsc-wrapper > > to give a better error message. > > Will do so. Thanks, Bernhard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20051206/95df54bd/attachment.pgp From wk at gnupg.org Wed Dec 7 14:37:12 2005 From: wk at gnupg.org (Werner Koch) Date: Wed Dec 7 14:41:54 2005 Subject: solved In-Reply-To: <20051206171917.GL6193@intevation.de> (Bernhard Reiter's message of "Tue, 6 Dec 2005 18:19:17 +0100") References: <20051206145859.GI6193@intevation.de> <87fyp6md3e.fsf@wheatstone.g10code.de> <20051206171917.GL6193@intevation.de> Message-ID: <871x0pkozb.fsf@wheatstone.g10code.de> On Tue, 6 Dec 2005 18:19:17 +0100, Bernhard Reiter said: > So you are saying that scdaemon should be a package on its own? > Currently it is put in the gpgsm package. > Which application is using scdaemon, besides gpg-agent > for openpgp and smime access over pcsc? None so war. However eventually Poldi (the smart card PAM module) will make use of scdaemon. Thus from a strategic point of view it should be its own package. Putting it into gpgsm is definitely wrong; thus gpg-agent would be better. Salam-Shalom, Werner From jam at jamux.com Thu Dec 8 16:01:59 2005 From: jam at jamux.com (John A. Martin) Date: Thu Dec 8 16:10:03 2005 Subject: libksba-0.9.13: undefined reference in gpg-error.h Message-ID: <87y82vfx94.fsf@athene.jamux.com> Using libgpg-error-dev 1.1-4 When building on Sid with 'dpkg-buildpackage -rfakeroot': ,---- .libs/reader.o: In function `gpg_error_from_errno':/usr/include/gpg-error.h:563: undefined reference to `gpg_err_code_from_errno' .libs/reader.o: In function `ksba_reader_new':/usr/include/gpg-error.h:563: undefined reference to `gpg_err_code_from_errno' .libs/reader.o: In function `gpg_error_from_errno':/usr/include/gpg-error.h:563: undefined reference to `gpg_err_code_from_errno' .libs/writer.o: In function `ksba_writer_new':/usr/include/gpg-error.h:563: undefined reference to `gpg_err_code_from_errno' .libs/writer.o: In function `gpg_error_from_errno':/usr/include/gpg-error.h:563: undefined reference to `gpg_err_code_from_errno' .libs/writer.o:/usr/include/gpg-error.h:563: more undefined references to `gpg_err_code_from_errno' follow `---- jam -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 154 bytes Desc: not available Url : /pipermail/attachments/20051208/9bdff586/attachment.pgp From jam at jamux.com Thu Dec 8 22:44:31 2005 From: jam at jamux.com (John A. Martin) Date: Thu Dec 8 22:48:36 2005 Subject: GnuPG v1.9.20-cvs3947: 1 of 2 tests failed Message-ID: <87k6effem8.fsf@athene.jamux.com> asschk: cmd_expect_ok: expected OK but got `ERR 50331649 General error ' FAIL: sm-sign+verify PASS: sm-verify libksba-0.9.13.tar.bz2 Debian Sid jam -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 154 bytes Desc: not available Url : /pipermail/attachments/20051208/61bfd90b/attachment.pgp From jam at jamux.com Thu Dec 8 23:46:16 2005 From: jam at jamux.com (John A. Martin) Date: Thu Dec 8 23:49:47 2005 Subject: GnuPG v1.9.20-cvs3947: 1 of 2 tests failed References: <87k6effem8.fsf__9456.87308344549$1134078640$gmane$org@athene.jamux.com> Message-ID: <87fyp3fbrb.fsf@athene.jamux.com> >>>>> "jam" == John A Martin >>>>> "GnuPG v1.9.20-cvs3947: 1 of 2 tests failed" >>>>> Thu, 08 Dec 2005 16:44:31 -0500 jam> asschk: cmd_expect_ok: expected OK but got `ERR 50331649 jam> General error ' FAIL: sm-sign+verify PASS: sm-verify Oops... Operator error. Now: PASS: sm-sign+verify PASS: sm-verify jam -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 154 bytes Desc: not available Url : /pipermail/attachments/20051208/384aa165/attachment.pgp From desrt at desrt.ca Sat Dec 10 21:27:36 2005 From: desrt at desrt.ca (Ryan Lortie) Date: Sat Dec 10 22:34:32 2005 Subject: [patch] gpg 1.4.2 ignores --no-tty (regression since 1.4.1) Message-ID: <1134246456.31664.5.camel@localhost.localdomain> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 701 bytes Desc: This is a digitally signed message part Url : /pipermail/attachments/20051210/9b2e70e1/attachment-0001.pgp From colin.granville at gmx.co.uk Sat Dec 10 20:59:02 2005 From: colin.granville at gmx.co.uk (Colin Granville) Date: Sun Dec 11 02:34:29 2005 Subject: --status-file output, trust and encryption Message-ID: Hi I'd like to propose a change to the --status-file output when encrypting a message. In batch mode when you encrypt a message where the recipient isn't trusted the encryption fails and INV_RECP 10 is output to the status file. If I use '--trust-model always' the encryption says nothing of the status of the recipient. What I want to do is give the user the option to send the message if the recipient isn't trusted. At present I have to try to encrypt the message and if I get a INV_REP 10 I tell the user that the receiver isn't trusted and if he wants to continue encrypt again with '--trust-model always'. The problem is that the level of trust is not output in the status file - which would be useful for the user to make a decision as to whether or not to continue, Also I have to run gpg twice which slows things down. What I propose is that encrypt always outputs the recipients trust level using the same trust output as when you verify a message ie TRUST_MARGINAL,TRUST_FULL,TRUST_ULTIMATE etc. Then I can encrypt with --trust-always and if the recipient isn't fully trusted then I can ask if the user wants to continue - with trust level info - and if he does the message is already encrypted Thank you. -- Colin From sadam at CLEMSON.EDU Sun Dec 11 03:57:20 2005 From: sadam at CLEMSON.EDU (Adam Schreiber) Date: Sun Dec 11 11:34:25 2005 Subject: [patch] gpg 1.4.2 ignores --no-tty (regression since 1.4.1) In-Reply-To: <1134246456.31664.5.camel@localhost.localdomain> References: <1134246456.31664.5.camel@localhost.localdomain> Message-ID: <439B9590.9090804@clemson.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Lortie wrote: > I've tested the patch and it solves the problem for me. Nobody else has > tried it, though, so additional testing and review is probably > appropriate. I've tested this patch and found it to fix a lot more in Seahorse than it was originally intended to. Cheers, Adam Schreiber - -- Why isn't all of your email protected? http://gnupg.org http://enigmail.mozdev.org http://seahorse.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDm5WQjU1oaHEI4wgRAuUIAJ49Cfjda5wyfseoR0NWDncOxuJSwgCeKw8Y lyxRXgXEz704O/uPbMlOGrs= =KEyM -----END PGP SIGNATURE----- From dshaw at jabberwocky.com Mon Dec 12 04:20:29 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Mon Dec 12 04:20:18 2005 Subject: [patch] gpg 1.4.2 ignores --no-tty (regression since 1.4.1) In-Reply-To: <1134246456.31664.5.camel@localhost.localdomain> References: <1134246456.31664.5.camel@localhost.localdomain> Message-ID: <20051212032029.GA25244@jabberwocky.com> On Sat, Dec 10, 2005 at 03:27:36PM -0500, Ryan Lortie wrote: > I've discovered a problem in gnupg 1.4.2 (regression since 1.4.1). > > If you try and run seahorse with this version with seahorse not invoked > from the commandline (ie: run from the gnome menu, for example) then you > are unable to assign new trust values to keys. > > The problem is described in Launchpad: > > https://launchpad.net/products/gnupg/+bug/5570 > > The bug is caused because gnupg is ignoring the --no-tty option passed > to it by seahorse and trying to open("/dev/tty/") anyway (and failing). > This is caused by the command-completion code for edit mode. When > initialising, it doesn't check no_terminal before trying to open the > tty. > > I've attached a small patch to fix that. Patch applied for 1.4.3. Thank you. David From mo at g10code.com Mon Dec 12 09:20:07 2005 From: mo at g10code.com (Moritz Schulte) Date: Mon Dec 12 12:36:10 2005 Subject: Poldi 0.3 released Message-ID: <439D32B7.1030208@g10code.com> Poldi 0.3 has been released. Poldi is a PAM module implementing authentication via OpenPGP smartcards. Files: ftp://ftp.gnupg.org/gcrypt/alpha/poldi/poldi-0.3.tar.gz (315K) ftp://ftp.gnupg.org/gcrypt/alpha/poldi/poldi-0.3.tar.gz.asc ftp://ftp.gnupg.org/gcrypt/alpha/poldi/poldi-0.3.tar.bz2 (261K) ftp://ftp.gnupg.org/gcrypt/alpha/poldi/poldi-0.3.tar.bz2.asc SHA1 sums are: 3daaef1c77cc935e549f2b4b0b5756fdbf888bcf poldi-0.3.tar.bz2 07832a64cd965fb716fcaf7e1f663017829c7644 poldi-0.3.tar.bz2.asc 49a91d1102bbf397b6c3cea08c5ae776f1b2eefc poldi-0.3.tar.gz b693b7a141798c94a4ff2a1832b6d4202ab7a402 poldi-0.3.tar.gz.asc ChangeLog: * Smartcard to account mapping: In the past, Poldi implemented a 1:1 mapping between smartcards and system accounts. As of now, Poldi implements a M:N mapping, meaning that one user can have multiple cards and that several users can share a card. Instead of "add-user" and "remove-user" commands we now have: - "register-card" - "unregister-card" - "list-cards" - "associate" - "disassociate". * Better support for Version 0x0101 cards: no Admin PIN necessary for public key retrival. * Work around a problem in libpam_misc, which causes the PIN prompt to appear to late. * Improved documentation. * Support for creating a skeleton configuration hierarchy. * Support for a timeout while waiting for smartcard insertion. * Removed `fake-wait-for-card'-feature. * Dropped ugly `install-pam-module' mechanism; now the PAM module gets installed automatically during `make install'. * Improved error reporting. * Code cleanup: heavily improved code documentation. Greetings, Moritz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature Url : /pipermail/attachments/20051212/b6876c17/signature.pgp From kfitzner at excelcia.org Mon Dec 12 01:31:58 2005 From: kfitzner at excelcia.org (Kurt Fitzner) Date: Tue Dec 13 01:34:34 2005 Subject: [Announce] GnuPG Explorer Extension (GPGee) version 1.2.2 released! Message-ID: <439CC4FE.2040105@excelcia.org> Skipped content of type multipart/signed-------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From kfitzner at excelcia.org Mon Dec 12 23:52:11 2005 From: kfitzner at excelcia.org (Kurt Fitzner) Date: Tue Dec 13 10:09:05 2005 Subject: [Announce] GPGee 1.2.2 has a bug - 1.2.3 corrects this. Message-ID: <439DFF1B.6020007@excelcia.org> Skipped content of type multipart/signed-------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From cam at mathematica.scientia.net Thu Dec 15 02:54:27 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Thu Dec 15 02:54:10 2005 Subject: keyflag subpacket and key expiration subpacket Message-ID: <43A0CCD3.8020303@mathematica.scientia.net> Hi. Everything applies to primary keys only: Why does gpg store the key flags (subpacket 27) and the key expiration time (subpacet 9) in a typ 0x13 selfsignature? Of course the standard allows this but wouldn't a 1F-sig be more appropriate? btw: in keyid.c there's the method usagestr_from_pk() is it a bug that only keys that have the S-flag can have a C-flag, too? If a key would have more than one UID with different key flag subpackets (this wouldn't make sense, that's why I asked about the 1F-sig before) which one does gpg take? Best wishes, Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051215/3ab42dc9/cam-0001.vcf From dshaw at jabberwocky.com Thu Dec 15 22:43:32 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Thu Dec 15 22:43:18 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <43A0CCD3.8020303@mathematica.scientia.net> References: <43A0CCD3.8020303@mathematica.scientia.net> Message-ID: <20051215214332.GD6647@jabberwocky.com> On Thu, Dec 15, 2005 at 02:54:27AM +0100, Christoph Anton Mitterer wrote: > Hi. > > Everything applies to primary keys only: > > Why does gpg store the key flags (subpacket 27) and the key expiration > time (subpacet 9) in a typ 0x13 selfsignature? Of course the standard > allows this but wouldn't a 1F-sig be more appropriate? It's tradition and history. GnuPG will accept subpackets on either the 0x13 (0x10, 0x11, 0x12) or 0x1F, of course, but only generates the 0x13. If we switched over to 0x1F, we'd probably break compatibility with other OpenPGP implementations. I agree, though, that things like key expiration would really make more sense on a 0x1F sig. > btw: in keyid.c there's the method usagestr_from_pk() is it a bug that > only keys that have the S-flag can have a C-flag, too? I assume you're looking at 1.4.2. No, it's not a bug because in 1.4.2 there is only one internal flag (PUBKEY_USAGE_SIG) for both sign and certify. The extra check for a primary key is just so the "C" flag is set in the display string. It's different in 1.4.3, by the way, where PUBKEY_USAGE_CERT is used in addition to PUBKEY_USAGE_SIG. None of this is visible from the outside though. David From cam at mathematica.scientia.net Fri Dec 16 00:36:37 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Fri Dec 16 00:46:18 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <20051215214332.GD6647@jabberwocky.com> References: <43A0CCD3.8020303@mathematica.scientia.net> <20051215214332.GD6647@jabberwocky.com> Message-ID: <43A1FE05.1000908@mathematica.scientia.net> David Shaw wrote: >It's tradition and history. GnuPG will accept subpackets on either >the 0x13 (0x10, 0x11, 0x12) or 0x1F, of course, but only generates the >0x13. > So does this mean if a key would have its key-exp-time/key-flags on an 0x1F that gpg would understand this? All the other subpackets, that don't refer to a signature itself (like creation/expiration time of the sig/exportability), preferred algos and even things like the features subpacket would make sense on a 0x10-0x13 selfsig indeed. >If we switched over to 0x1F, we'd probably break compatibility >with other OpenPGP implementations. > > Well these applications are not really implementations of OpenPGP. The standard clearly specifies which parts an implementation must not implement. And as far as I can see implementations are allowed to don't implement subpackets (but in that case they must consider these packets if the critical bit is set) but they aren't allowed to recognize subpackets only on specifiv sig-types (expect those where the standard itself allows a subpacket type only on special sig-types). >I agree, though, that things like key expiration would really make >more sense on a 0x1F sig. > > Yes,.. as an intermediate improvement, gpg could create the subpackets (key-exp and key flags) on a primary-flagged sig only. >>btw: in keyid.c there's the method usagestr_from_pk() is it a bug that >>only keys that have the S-flag can have a C-flag, too? >> >> >I assume you're looking at 1.4.2. No, it's not a bug because in 1.4.2 >there is only one internal flag (PUBKEY_USAGE_SIG) for both sign and >certify. The extra check for a primary key is just so the "C" flag is >set in the display string. > >It's different in 1.4.3, by the way, where PUBKEY_USAGE_CERT is used >in addition to PUBKEY_USAGE_SIG. None of this is visible from the >outside though. > > Ahh, ooops,.. you're right :-) . Best wishes, Chris. -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051216/07fa4595/cam.vcf From cam at mathematica.scientia.net Fri Dec 16 02:08:37 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Fri Dec 16 02:14:56 2005 Subject: preferred keyserver settings Message-ID: <43A21395.2070908@mathematica.scientia.net> Hi. Ok, this is a little bit off topic... The RFC says the following about the preferred keyserver: 5.2.3.18. Preferred key server (String) This is a URI of a key server that the key holder prefers be used for updates. Note that keys with multiple User IDs can have a preferred key server for each User ID. Note also that since this is a URI, the key server can actually be a copy of the key retrieved by ftp, http, finger, etc. What does this "the key server can actually be a copy of the key retrieved by" mean? Does it mean that I is totally conformant to specify an URI like: "http://foo.bar/myPersonalKey.asc" (note that I'm aware that there is no bar TLD ;-) )? This URI would simply hold a copy of the key (and probably all its signatures (including revokation certs and so on)) that could be retrieved via http. Would this be conformant with the standard? Would it work with gpg? ;) Best wishes, Chris. -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051216/753dcc23/cam.vcf From dshaw at jabberwocky.com Fri Dec 16 03:28:47 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Fri Dec 16 03:28:31 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <43A1FE05.1000908@mathematica.scientia.net> References: <43A0CCD3.8020303@mathematica.scientia.net> <20051215214332.GD6647@jabberwocky.com> <43A1FE05.1000908@mathematica.scientia.net> Message-ID: <20051216022847.GA8407@jabberwocky.com> On Fri, Dec 16, 2005 at 12:36:37AM +0100, Christoph Anton Mitterer wrote: > David Shaw wrote: > > >It's tradition and history. GnuPG will accept subpackets on either > >the 0x13 (0x10, 0x11, 0x12) or 0x1F, of course, but only generates the > >0x13. > > > So does this mean if a key would have its key-exp-time/key-flags on an > 0x1F that gpg would understand this? Yes. > >If we switched over to 0x1F, we'd probably break compatibility > >with other OpenPGP implementations. > > > > > Well these applications are not really implementations of OpenPGP. The > standard clearly specifies which parts an implementation must not > implement. And as far as I can see implementations are allowed to don't > implement subpackets (but in that case they must consider these packets > if the critical bit is set) but they aren't allowed to recognize > subpackets only on specifiv sig-types (expect those where the standard > itself allows a subpacket type only on special sig-types). I don't agree that the standard requires this, but even if it did, the IETF "be conservative in what you generate, liberal in what you accept" meta-rule applies. Where is the benefit in using 0x1F and not being able to communicate with others? David From dshaw at jabberwocky.com Fri Dec 16 03:32:14 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Fri Dec 16 03:31:56 2005 Subject: preferred keyserver settings In-Reply-To: <43A21395.2070908@mathematica.scientia.net> References: <43A21395.2070908@mathematica.scientia.net> Message-ID: <20051216023214.GB8407@jabberwocky.com> On Fri, Dec 16, 2005 at 02:08:37AM +0100, Christoph Anton Mitterer wrote: > Hi. > > Ok, this is a little bit off topic... > > The RFC says the following about the preferred keyserver: > > 5.2.3.18. Preferred key server > (String) > This is a URI of a key server that the key holder prefers be used > for updates. Note that keys with multiple User IDs can have a > preferred key server for each User ID. Note also that since this is > a URI, the key server can actually be a copy of the key retrieved by > ftp, http, finger, etc. > > > What does this "the key server can actually be a copy of the key > retrieved by" mean? > Does it mean that I is totally conformant to specify an URI like: > "http://foo.bar/myPersonalKey.asc" (note that I'm aware that there is no > bar TLD ;-) )? > This URI would simply hold a copy of the key (and probably all its > signatures (including revokation certs and so on)) that could be > retrieved via http. > > Would this be conformant with the standard? Yes. > Would it work with gpg? ;) Yes. Current versions of GPG allow http and finger URLs. The upcoming version adds support for everything that cURL supports (https, ftp, ftps, etc). David From cam at mathematica.scientia.net Fri Dec 16 04:14:28 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Fri Dec 16 04:31:54 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <20051216022847.GA8407@jabberwocky.com> References: <43A0CCD3.8020303@mathematica.scientia.net> <20051215214332.GD6647@jabberwocky.com> <43A1FE05.1000908@mathematica.scientia.net> <20051216022847.GA8407@jabberwocky.com> Message-ID: <43A23114.7090805@mathematica.scientia.net> >>So does this mean if a key would have its key-exp-time/key-flags on an >>0x1F that gpg would understand this? >> >> >Yes. > > Ah, great, so gpg is compliant to the standard in that point. I think only key expiration time (9), revokation key (12), notation data (20) (in those cases where the data applies to the key itself and not to a specific UID), key flags (27) and reasons for revokation (29) should go there..... Would it be easily possible with gpg to put those subpackets (currently I'd only need it with 9 and 27) in a 0x1F sig? If so could you please give me a hint to some function(s) in the code that I'd have to parse and modify for my personal needs (as with the key flags when I wanted to change it to C-only ;-) ). (Yes I'm still trying to create the - in my opinion - perfect OpenPGP key ;-) ) >>Well these applications are not really implementations of OpenPGP. The >>standard clearly specifies which parts an implementation must not >>implement. And as far as I can see implementations are allowed to don't >>implement subpackets (but in that case they must consider these packets >>if the critical bit is set) but they aren't allowed to recognize >>subpackets only on specifiv sig-types (expect those where the standard >>itself allows a subpacket type only on special sig-types). >> >> >I don't agree that the standard requires this, but even if it did, the >IETF "be conservative in what you generate, liberal in what you >accept" meta-rule applies. > Well that's always a problem.... but therfore we have standards, I think. - First of all: I didn't say that gpg (or another implementation) MUST put it in an 0x1F. - I quick-parsed section 5.2 of the RFC an it says nowhere that an conforming application would be allowed to not-implement any of the given sig-types. - It even says that an application MUST understand (but not necessarily generate) v4 sigs; this follows from "Implementations SHOULD accept V3 signatures. Implementations SHOULD generate V4 signatures.", I think. - In 5.2.3.1 it says that an "implementation SHOULD ignore any subpacket of a type that it does not recognize" (except the "critical" bit is set) BUT it says nowhere that an implementation understand a subpacket type in on sig type but not in another.... This is why I came to the idea that in my opinion the standard requires to understand this (of course: only if an implementation understands it in other sig-types (i.e. 0x13), too) btw: does gpg fully support the critical bit an can I somehow set it (if so, please point me to specific functions, too; if possible)? I'd like to do this for my: - signature expiration time (3) (which requires a critical bit for signature creation time (2), too) - exportable certification (4) - key expiration time (9) - key flags (27) subpackets, because I think those are really security relevant if an application wouldn't be able to understand them. The other subpackets are not so relevant, I think, because they couldn't create a security hole if an application wouldn't understand them (e.g. if the trust package isn't understood, other keys wouldn't be taken as valid => ok, not so nice, but not a security problem BUT if an application doesn't understand the 0x3 subpacket it wouldn't notice if the signature is already invalid). >Where is the benefit in using 0x1F and not being able to communicate with others? > > - Well I think thats why there is a standard: To strictly specify how implementations from different vendors can interoperate together. If a vendor (e.g. PGP Corp.) would not comply with the rules, he'd break interoperability, but I think just because a vendor has many users, no other vendor should break the standard, too. gpg doesn't do that, as you said it fully supports 0x1F sigs. - The same thing applies (in my opinion) to the compliance options that gpg supports,... I think the reason for their existance are that there are a older applications (e.g. PGP 2.6.x) and especillay older keys (and most users would like to continue using their existing keys). Of course that's a good thing, ... But: Are there really those many users of OLD implementations? And for the old keys: Is it really cleaver to strongly support those users in continue using their old keys? I think with v3 keys there is that key-id-forging issue,... and the old v3 sigs use MD5 only, jesus! It wouldn't be that bad (I think) to offend sensibilities of those users and "force" them to create new keys... Thanks and best wishes, Chris. btw: is there a policy for the gpg list? Should the author whom I reply to be CC'ed? -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051216/09807a99/cam.vcf From dshaw at jabberwocky.com Fri Dec 16 04:51:07 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Fri Dec 16 04:50:54 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <43A23114.7090805@mathematica.scientia.net> References: <43A0CCD3.8020303@mathematica.scientia.net> <20051215214332.GD6647@jabberwocky.com> <43A1FE05.1000908@mathematica.scientia.net> <20051216022847.GA8407@jabberwocky.com> <43A23114.7090805@mathematica.scientia.net> Message-ID: <20051216035107.GA5063@jabberwocky.com> On Fri, Dec 16, 2005 at 04:14:28AM +0100, Christoph Anton Mitterer wrote: > > >>So does this mean if a key would have its key-exp-time/key-flags on an > >>0x1F that gpg would understand this? > >> > >> > >Yes. > > > > > Ah, great, so gpg is compliant to the standard in that point. > I think only > key expiration time (9), > revokation key (12), > notation data (20) (in those cases where the data applies to the key > itself and not to a specific UID), > key flags (27) and > reasons for revokation (29) > should go there..... > > Would it be easily possible with gpg to put those subpackets (currently > I'd only need it with 9 and 27) in a 0x1F sig? Honestly, no. It would be a significant project to rewrite those sections of the program. GPG is compliant with the standard now, and changing this would risk compatibility for no gain beyond the aesthetic desire to have subpackets in a different place. David From cam at mathematica.scientia.net Sat Dec 17 01:32:15 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Sat Dec 17 01:31:57 2005 Subject: keyflag subpacket and key expiration subpacket In-Reply-To: <20051216035107.GA5063@jabberwocky.com> References: <43A0CCD3.8020303@mathematica.scientia.net> <20051215214332.GD6647@jabberwocky.com> <43A1FE05.1000908@mathematica.scientia.net> <20051216022847.GA8407@jabberwocky.com> <43A23114.7090805@mathematica.scientia.net> <20051216035107.GA5063@jabberwocky.com> Message-ID: <43A35C8F.9010703@mathematica.scientia.net> David Shaw wrote: >Honestly, no. It would be a significant project to rewrite those >sections of the program. > > Ok, thanks anyway :-) I'm going to try to create such sigs by patching a lokal version of gpg,... 1) Creating a new 0x1F sig containing the required stuff (this should be the same things as found on the 0x1F sigs for the revokation-key, correct? - of course without the revokation key subpacket itself) with an additional key-expiration-time and key-flag subpacket. 2) Recreate the 0x13 for all the UIDs,.. and simply delete the key-expiration-time and key-flag subpacket, correct? Ok,.. I'm always unsure if my patches are correct, but is true that everything should have worked well if: - I manually look up the hexcode of the whole signature packet and compare it with the standard,... - import the sig in gpg to see if the signature data itself has been calculatet correctly. If not gpg should complain... Chris. -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051217/d20f72ff/cam.vcf From cam at mathematica.scientia.net Sat Dec 17 21:53:19 2005 From: cam at mathematica.scientia.net (Christoph Anton Mitterer) Date: Sat Dec 17 21:52:54 2005 Subject: Policy URLs Message-ID: <43A47ABF.30400@mathematica.scientia.net> Hi. Just a short question: The rfc says the following about the policy url: "This subpacket contains a URI of a document that describes the policy that the signature was issued under." This is clear for certifactions of other users and or "normal" data. But is there any DEFINED meaning when a Policy URL is set on a selfsignature of a key? When found on a 0x1F something like: "This whole (primary) key makes signatures under the following policy." On a 0x18 something like: "This (secondary) key makes signatures under the following policy." On 0x10-0x13 sth. like "When this users made the signature, the following policy applies" (of course this would require a signers UID packet. This would mean that in such a case (when found on any self sig) the policy URL subpacket doesn't relate to the signature itself but to the key (-> which policy will be used by this key). Chris. -------------- next part -------------- A non-text attachment was scrubbed... Name: cam.vcf Type: text/x-vcard Size: 449 bytes Desc: not available Url : /pipermail/attachments/20051217/e2a57e0c/cam.vcf From wk at gnupg.org Tue Dec 20 12:14:05 2005 From: wk at gnupg.org (Werner Koch) Date: Tue Dec 20 13:51:52 2005 Subject: [Announce] GnuPG 1.9.20 (S/MIME and gpg-agent) released Message-ID: <87acewc96q.fsf@wheatstone.g10code.de> Skipped content of type multipart/signed-------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From rdieter at math.unl.edu Wed Dec 21 14:57:54 2005 From: rdieter at math.unl.edu (Rex Dieter) Date: Wed Dec 21 15:02:32 2005 Subject: gnupg2-1.9.20: continued 'make check' failures: x86_64, ppc Message-ID: We're seeing (continued) failures when issuing 'make check' after successful build on non-ix86 platforms (x86_64 and ppc in particular). Build logs can be viewed at: http://buildsys.fedoraproject.org/logs/fedora-development-extras/2038-gnupg2-1.9.20-1.fc5/ I personally only have access to ix86 boxes, so cannot diagnose much more myself. -- Rex From marc.schiffbauer at siemens.com Thu Dec 22 14:04:55 2005 From: marc.schiffbauer at siemens.com (Marc Schiffbauer) Date: Thu Dec 22 20:34:31 2005 Subject: Problems importing my pkcs#12 cert Message-ID: <200512221404.55745.marc.schiffbauer@siemens.com> Hi all, I want to use kmail with S/MIME to handle encrypted email. Importing my .p12 cert does not work though. Here is what I tried: ~$ gpgsm --import Marc_Schiffbauer_cert_backup.p12 gpgsm: NOTE: THIS IS A DEVELOPMENT VERSION! gpgsm: It is only intended for test purposes and should NOT be gpgsm: used in a production environment or with production keys! gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default gpgsm: gpg-protect-tool: error at "bags", offset 24 gpgsm: gpg-protect-tool: error parsing or decrypting the PKCS-12 file gpgsm: error running `/usr/lib//gpg-protect-tool': exit status 2 gpgsm: gesamte verarbeitete Anzahl: 0 secmem usage: 0/16384 bytes in 0 blocks (pinentry-qt asked for the passphrase) Any hints what the problem might be? Thanks -Marc -- ****.~.************************************************************* * /V\ * * * // \\ Free Software * Siemens Business Services * * /( )\ Solution Design * Competence-Center Open Source * * ^`~'^ * Tel.: +49 (0) 173.263.06.21 * ******************************************************************** From jan at intevation.de Thu Dec 22 23:42:00 2005 From: jan at intevation.de (Jan-Oliver Wagner) Date: Fri Dec 23 02:34:18 2005 Subject: Problems importing my pkcs#12 cert In-Reply-To: <200512221404.55745.marc.schiffbauer@siemens.com> References: <200512221404.55745.marc.schiffbauer@siemens.com> Message-ID: <200512222342.01062.jan@intevation.de> Am Donnerstag, 22. Dezember 2005 14:04 schrieb Marc Schiffbauer: > I want to use kmail with S/MIME to handle encrypted email. Importing > my .p12 cert does not work though. known bug, fixed with 1.9.20. Best Jan From wfahmy at rdmcorp.com Thu Dec 22 15:23:24 2005 From: wfahmy at rdmcorp.com (Waleed Fahmy) Date: Fri Dec 23 13:35:59 2005 Subject: Using GnuPG ver 1.0.5 Message-ID: Hi I am using the GnuPG ver 1.0.5 but I am getting errors when the file path includes spaces for ex the command line "gpg -r xxx -o C:\Test New\Test.gpg --encrypt C:\Test New\Test.txt" does not work giving me the message "usage: gpg [options] [filename]" Please cc me on the reply Thanks Waleed From lionel at mamane.lu Fri Dec 23 14:36:46 2005 From: lionel at mamane.lu (Lionel Elie Mamane) Date: Fri Dec 23 19:10:05 2005 Subject: Using GnuPG ver 1.0.5 In-Reply-To: References: Message-ID: <20051223133646.GA30477@capsaicin.mamane.lu> On Thu, Dec 22, 2005 at 09:23:24AM -0500, Waleed Fahmy wrote: > I am using the GnuPG ver 1.0.5 but I am getting errors when the > file path includes spaces for ex the command line "gpg -r xxx -o > C:\Test New\Test.gpg --encrypt C:\Test New\Test.txt" does not work > giving me the message "usage: gpg [options] [filename]" Put the filename between double quotes. So for example: gpg -r xxx -o "C:\Test New\Test.gpg" --encrypt "C:\Test New\Test.txt" -- Lionel From sithtracy at yahoo.com Fri Dec 23 14:00:13 2005 From: sithtracy at yahoo.com (Tracy D. Bossong) Date: Fri Dec 23 21:35:37 2005 Subject: Using GnuPG ver 1.0.5 In-Reply-To: Message-ID: <20051223130013.67080.qmail@web51715.mail.yahoo.com> Any file name/path with spaces needs quotes around it: i.e. "C:\Test New\Test.txt" "C:\Test New\Test.gpg" --- Waleed Fahmy wrote: > Hi > > I am using the GnuPG ver 1.0.5 but I am getting > errors when the file path > includes spaces for ex the command line "gpg -r xxx > -o C:\Test > New\Test.gpg --encrypt C:\Test New\Test.txt" does > not work giving me the > message "usage: gpg [options] [filename]" > > Please cc me on the reply > > Thanks > Waleed > > > _______________________________________________ > Gnupg-devel mailing list > Gnupg-devel@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-devel > From JPClizbe at comcast.net Fri Dec 23 22:43:09 2005 From: JPClizbe at comcast.net (John Clizbe) Date: Fri Dec 23 22:43:35 2005 Subject: Using GnuPG ver 1.0.5 In-Reply-To: References: Message-ID: <43AC6F6D.9040307@comcast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Waleed Fahmy wrote: > Hi > > I am using the GnuPG ver 1.0.5 but I am getting errors when the file path > includes spaces for ex the command line "gpg -r xxx -o C:\Test > New\Test.gpg --encrypt C:\Test New\Test.txt" does not work giving me the > message "usage: gpg [options] [filename]" > > Please cc me on the reply 1) Put the filename in quotes. So for example: gpg -r xxx -o "C:\Test New\Test.gpg" --encrypt "C:\Test New\Test.txt" 2) use 8.3 naming, e.g. the default GnuPG homedir in new versions would be DOCUME~1\username\APPLIC~1\GnuPG gpg -r xxx -o C:\TestNe~1\Test.gpg --encrypt C:\TestNe~1\Test.txt You can use DIR/X to get 8.3 file names On a different note, Any reason to hang on to such an old version of GnuPG? - -- John P. Clizbe Inet: JPClizbe(a)comcast DOT nyet Golden Bear Networks PGP/GPG KeyID: 0x608D2A10 "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr Seuss, "Oh the Places You'll Go" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3-cvs-3977-2005-12-23 (Windows XP Pro SP2) Comment: When cryptography is outlawed, b25seSBvdXRsYXdzIHdpbGwgdXNlIG Comment: Be part of the ?33t ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQ6xvaL4fmBEYuzc6AQLNEgQAs4Jsyf0WtecwcdwKL7Avs/9M0phvKyU4 OrRCfF2bqr3dZqRyHQhlhfOB9GygWpLFR4YhQ7hVuf+NjOdjWidvOg3bB7aLcwMs YHFJYCTEG2MWCh7r5eMUQBzHsTBy1KRgMtY+/GerAgAtcrEfPTfgHA3xjhQJCCJW 0m6Tn1x6eKmIPwMFAUOsb2wdBKxKYI0qEBECgRUAn1cTGlwvh0Qinaiy6M4WtQ+3 GSqFAKDVzDrKLSHgJ1q6slO1+WaoNsivEg== =JKjZ -----END PGP SIGNATURE----- From dshaw at jabberwocky.com Fri Dec 23 22:49:45 2005 From: dshaw at jabberwocky.com (David Shaw) Date: Fri Dec 23 22:49:25 2005 Subject: Using GnuPG ver 1.0.5 In-Reply-To: <43AC6F6D.9040307@comcast.net> References: <43AC6F6D.9040307@comcast.net> Message-ID: <20051223214945.GD27970@jabberwocky.com> On Fri, Dec 23, 2005 at 03:43:09PM -0600, John Clizbe wrote: > On a different note, Any reason to hang on to such an old version of GnuPG? I'd recommend against it. David From wildfire at progsoc.uts.edu.au Mon Dec 26 09:27:47 2005 From: wildfire at progsoc.uts.edu.au (Anand Kumria) Date: Mon Dec 26 11:34:49 2005 Subject: exporting private key from gpgsm Message-ID: <20051226082747.GA10348@progsoc.uts.edu.au> Hi, I stumbled across which documents how to generate a server certificate. I've done this and had it successfully signed by CAcert. However I'm not able to extract the private key in a usable form. For the public key I can do: gpgsm --export keygrab > server.crt But the server software (exim4 from Debian) I am using does NOT like: gpgsm --export-secret-key-p12 > server.key It wants the private key in -----BEGIN RSA PRIVATE KEY----- [...] -----END RSA PRIVATE KEY----- form, which I believe is PKCS#8 form. Worse neither openssl (0.9.8a-3) not gnutls (1.2.9-2) are able to parse the PKCS#12 secret key that gpgsm (1.9.19-2) produces. eve:[~/PKI/CA]% openssl pkcs12 -info -in giskard.key.p12 14397:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1282: 14397:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:374:Type=PKCS12 eve:[~/PKI/CA]% certtool --p12-info --infile giskard.key.pem Enter password: p12_import: Base64 decoding error. Any information, or suggestions, would be appreciatd. Thanks, Anand -- `When any government, or any church for that matter, undertakes to say to its subjects, "This you may not read, this you must not see, this you are forbidden to know," the end result is tyranny and oppression no matter how holy the motives' -- Robert A Heinlein, "If this goes on --" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: Digital signature Url : /pipermail/attachments/20051226/6bcbd1fc/attachment.pgp From jas at extundo.com Mon Dec 26 19:05:22 2005 From: jas at extundo.com (Simon Josefsson) Date: Mon Dec 26 21:04:43 2005 Subject: exporting private key from gpgsm In-Reply-To: <20051226082747.GA10348__49644.4822093055$1135593399$gmane$org@progsoc.uts.edu.au> (Anand Kumria's message of "Mon, 26 Dec 2005 19:27:47 +1100") References: <20051226082747.GA10348__49644.4822093055$1135593399$gmane$org@progsoc.uts.edu.au> Message-ID: Anand Kumria writes: > form, which I believe is PKCS#8 form. Worse neither openssl (0.9.8a-3) > not gnutls (1.2.9-2) are able to parse the PKCS#12 secret key that gpgsm > (1.9.19-2) produces. > > eve:[~/PKI/CA]% openssl pkcs12 -info -in giskard.key.p12 > 14397:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1282: > 14397:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:374:Type=PKCS12 > > eve:[~/PKI/CA]% certtool --p12-info --infile giskard.key.pem > Enter password: > p12_import: Base64 decoding error. > > Any information, or suggestions, would be appreciatd. You may want to try GnuTLS 1.3.2; I fixed several PKCS#12 and PKCS#8 problems in 1.3.1. One of the bugs caused the certtool output above. The OpenSSL output suggest there is a deeper problem though. Cheers, Simon From ssrini at linuxmail.org Tue Dec 27 13:05:45 2005 From: ssrini at linuxmail.org (Srinivasan S) Date: Tue Dec 27 13:05:58 2005 Subject: gpgol cross compilation error Message-ID: <20051227120545.EBE4A7B524@ws5-10.us4.outblaze.com> Hi, Iam using the latest sources from the cvs trunk of gpgol Have the following compilation error (attempting cross compilation on Debian box) Please help Regards Srini Make output: ssrini@debian:~/gpg_cvs/gpgol$ make make all-recursive make[1]: Entering directory `/home/ssrini/gpg_cvs/gpgol' Making all in src make[2]: Entering directory `/home/ssrini/gpg_cvs/gpgol/src' if i586-mingw32msvc-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/home/ssrini/w32root/include -I/home/ssrini/w32root/include -shared -g -O2 -Wall -mms-bitfields -Wcast-align -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wformat-security -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi In file included from intern.h:26, from main.c:31: util.h:47:25: w32-gettext.h: No such file or directory main.c: In function `i18n_init': main.c:94: warning: implicit declaration of function `setlocale' main.c:94: error: `LC_ALL' undeclared (first use in this function) main.c:94: error: (Each undeclared identifier is reported only once main.c:94: error: for each function it appears in.) main.c:101: warning: implicit declaration of function `bindtextdomain' main.c:104: warning: implicit declaration of function `textdomain' make[2]: *** [main.o] Error 1 make[2]: Leaving directory `/home/ssrini/gpg_cvs/gpgol/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ssrini/gpg_cvs/gpgol' make: *** [all] Error 2 ssrini@debian:~/gpg_cvs/gpgol$ -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log.zip Type: application/x-zip-compressed Size: 7262 bytes Desc: not available Url : /pipermail/attachments/20051227/aa755a7e/config.log-0001.bin From wildfire at progsoc.uts.edu.au Wed Dec 28 11:36:29 2005 From: wildfire at progsoc.uts.edu.au (Anand Kumria) Date: Wed Dec 28 11:36:25 2005 Subject: interop. issues was: exporting private key from gpgsm In-Reply-To: References: <20051226082747.GA10348__49644.4822093055$1135593399$gmane$org@progsoc.uts.edu.au> Message-ID: <20051228103629.GJ27957@progsoc.uts.edu.au> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: Digital signature Url : /pipermail/attachments/20051228/87f9eb45/attachment.pgp