From aegypten-issues at intevation.de Fri Oct 1 17:24:21 2004 From: aegypten-issues at intevation.de (=?utf-8?q?Ingo_Kl=C3=B6cker?=) Date: Fri Oct 1 17:20:55 2004 Subject: [issue258] Misleading error messages if (OpenPGP) backend is disabled Message-ID: <1096644261.5.0.875023660831.issue258@intevation.de> New submission from Ingo Kl?cker : If I disable the gpgme/OpenPGP backend while a composer is open I can enable signing/encryption (which is okay because of kpgp), but trying to send the message will result in misleading error messages. When I try to send the message I get a message box "Send &Unsigned" "You have requested to sign this message, but no valid signing keys have been configured for this identity. If you choose to continue, no signing will be performed." (According to the KDE GUI style guide the Continue button SHOULD have the text "Send Unsigned" which I've just fixed in HEAD.) and, after continuing, I get the message box "Send &Unencrypted" "You have requested to encrypt this message, and to encrypt a copy to yourself, but no valid trusted encryption keys have been configured for this identity." (Here the user isn't even told that the message will be send unencrypted if he clicks on Continue. That's actually a small security problem because the user might unintentionally send a message unencrypted. I've also fixed this in HEAD by putting the text "Send Unencrypted" on the Continue button.) ---------- messages: 1546 nosy: ingo priority: bug status: unread title: Misleading error messages if (OpenPGP) backend is disabled ______________________________________________________ Aegypten issue tracker ______________________________________________________ From cepl at surfbest.net Sat Oct 2 01:54:35 2004 From: cepl at surfbest.net (Matej Cepl) Date: Sat Oct 2 02:34:57 2004 Subject: gpg 1.9 for Debian/sarge References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <20040927181014.GB9642@intevation.de> Message-ID: <9315241.fkR0le72rs@blahoslav.surfbest.net> Jan-Oliver Wagner wrote: > On Sun, Sep 26, 2004 at 02:13:28PM -0400, Matej Cepl wrote: > you may try this one: > http://apt.intevation.de/deb/dists/woody/aegypten_2_0_0_rc1/\ > binary-i386/gnupg1.9_1.9.10-0.0.0.1_i386.deb After trying everything (including this GNUPG package), I finally done the most brutal thing -- I went to http://jdurand.home.cern.ch/jdurand/cern_ca_and_mail/, find out which packages I should downloaded and the I have downloaded them from http://smurf.noris.de/code/debian/experimental/i386/. I have installed them, restarted gpg-agent and now it really seems to work. -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 From cepl at surfbest.net Sat Oct 2 07:39:08 2004 From: cepl at surfbest.net (Matej Cepl) Date: Sat Oct 2 07:36:25 2004 Subject: gpg 1.9 for Debian/sarge References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <20040927181014.GB9642@intevation.de> <9315241.fkR0le72rs@blahoslav.surfbest.net> Message-ID: <40649858.PZpbcsNnRn@blahoslav.surfbest.net> Matej Cepl wrote: > After trying everything (including this GNUPG package), I > finally done the most brutal thing -- I went to > http://jdurand.home.cern.ch/jdurand/cern_ca_and_mail/, find out > which packages I should downloaded and the I have downloaded > them from http://smurf.noris.de/code/debian/experimental/i386/. > I have installed them, restarted gpg-agent and now it really > seems to work. Well, it doesn't -- I can read/write PGP messages, but only read S/MIME. When trying to send S/MIME message, I get into some kind of endless loop (see attached log -- these are just first couple lines of the file which was 4.5MB when I killed KMail -- the rest was the same as the beginning, see also a list of installed packages on my Debian/sarge). Any thoughts? Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 -------------- next part -------------- A non-text attachment was scrubbed... Name: gpgsm.log.bz2 Type: application/x-bzip2 Size: 2275 bytes Desc: not available Url : /pipermail/attachments/20041002/00beca4e/gpgsm.log.bin -------------- next part -------------- ii cryptplug 0.3.16-1 Collection of plugins to crytographic engine ii libcrypt-sslea 0.51-1 Support for https protocol in LWP ii libgcrypt11 1.2.0-4 LGPL Crypto library - runtime library ii libgcrypt11-de 1.2.0-4 LGPL Crypto library - development files ii libgcrypt7 1.1.90-9 LGPL Crypto library - runtime library ii gnupg 1.2.4-4 GNU privacy guard - a free PGP replacement ii gnupg-agent 1.9.11+cvs2004 GNU privacy guard - password agent ii gnupg2 1.9.11+cvs2004 GNU privacy guard - a free PGP replacement ii gpgsm 1.9.11+cvs2004 GNU privacy guard - password agent ii kgpg 3.2.2-2 GnuPG frontend for KDE ii kgpgcertmanage 3.2.2-2 KDE Certificate Manager ii libgpg-error-d 1.0-1 library for common error values and messages ii libgpg-error0 1.0-1 library for common error values and messages ii libgpgme6 0.3.16-2 GPGME - GnuPG Made Easy ii libgwrapguile1 1.3.4-12 g-wrap: Tool for exporting C libraries into From wk at gnupg.org Sat Oct 2 08:30:26 2004 From: wk at gnupg.org (Werner Koch) Date: Sat Oct 2 08:34:14 2004 Subject: gpg 1.9 for Debian/sarge In-Reply-To: <40649858.PZpbcsNnRn@blahoslav.surfbest.net> (Matej Cepl's message of "Sat, 02 Oct 2004 01:39:08 -0400") References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <20040927181014.GB9642@intevation.de> <9315241.fkR0le72rs@blahoslav.surfbest.net> <40649858.PZpbcsNnRn@blahoslav.surfbest.net> Message-ID: <873c0xhbst.fsf@wheatstone.g10code.de> On Sat, 02 Oct 2004 01:39:08 -0400, Matej Cepl said: > Any thoughts? You are using an old kgpgcertmanager, IIRC it is now called kleopatra. Quite some time ago we changed the semantics on how to build the certificate chain for displaying and Kgpgcertmanager still uses the old one. That won't be too severe if it had put a limit on the maximum chain length to detect such a loop. I have always suggested to do this. A proper way of coding it would be something like: int maxdepth = 100; k = key->kobj; gpgme_key_ref (k); while ((s = k->chain_id) && k->subkeys && strcmp (s, k->subkeys->fpr) ) { putc ('\n', fp); err = gpgme_op_keylist_start (listctx, s, 0); gpgme_key_release (k); k = NULL; if (!err) err = gpgme_op_keylist_next (listctx, &k); if (err) { fprintf (fp, _("Error finding issuer key: %s\n"), gpgme_strerror (err)); goto leave; } gpgme_op_keylist_end (listctx); print_key_info (k, fp); if (!--maxdepth) { putc ('\n', fp); fputs (_("Error: certification chain to long - stopping here\n"), fp); break; } } Werner From aegypten-issues at intevation.de Sat Oct 2 15:35:24 2004 From: aegypten-issues at intevation.de (Bernhard Reiter) Date: Sat Oct 2 15:32:00 2004 Subject: [issue259] mutt not reporting old CRL, claiming error and good verification Message-ID: <1096724124.36.0.133059849844.issue259@intevation.de> New submission from Bernhard Reiter : mutt cvs (build 20040926) with patch-1.5.6cvs.g10.mdn.3 patch-1.5.6cvs.g10.gpgme.6 (wrongly reported as 4) gpgsm (GnuPG) 1.9.12-cvs (CVS from 20041001) Trying to verify a message where one on the CRLs of the chain is too old. Mutt says: Error checking signature And in the status line: S/MIME Unterschrift erfolgreich ?berpr?ft. ---------- assignedto: werner messages: 1557 nosy: bernhard, bh, werner priority: bug status: unread title: mutt not reporting old CRL, claiming error and good verification topic: mutt ______________________________________________________ Aegypten issue tracker ______________________________________________________ From cepl at surfbest.net Sun Oct 3 02:08:52 2004 From: cepl at surfbest.net (Matej Cepl) Date: Sun Oct 3 02:05:43 2004 Subject: gpg 1.9 for Debian/sarge References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <20040927181014.GB9642@intevation.de> <9315241.fkR0le72rs@blahoslav.surfbest.net> <40649858.PZpbcsNnRn@blahoslav.surfbest.net> <873c0xhbst.fsf@wheatstone.g10code.de> Message-ID: <1664096.bORdIy5MbG@blahoslav.surfbest.net> Werner Koch wrote: > You are using an old kgpgcertmanager, IIRC it is now called > kleopatra. > > Quite some time ago we changed the semantics on how to build > the certificate chain for displaying and Kgpgcertmanager still > uses the old one. That won't be too severe if it had put a > limit on the maximum chain length to detect such a loop. I > have always suggested to do this. A proper way of coding it > would be something like: Do you have any idea how to make S/MIME chain work with KMail and in sarge. Unfortunately, kleopatra is only part of KDE 3.3, and there is only KDE 3.2.3 on sarge. And I really do not think like fixing kgpgcertmanager myself (being just a lawyer :-). Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 From nolden at kde.org Sun Oct 3 07:44:17 2004 From: nolden at kde.org (Ralf Nolden) Date: Sun Oct 3 07:40:57 2004 Subject: gpg 1.9 for Debian/sarge In-Reply-To: <1664096.bORdIy5MbG@blahoslav.surfbest.net> References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <873c0xhbst.fsf@wheatstone.g10code.de> <1664096.bORdIy5MbG@blahoslav.surfbest.net> Message-ID: <200410030744.20320.nolden@kde.org> On Sonntag 03 Oktober 2004 02:08, Matej Cepl wrote: > Werner Koch wrote: > > You are using an old kgpgcertmanager, IIRC it is now called > > kleopatra. > > > > Quite some time ago we changed the semantics on how to build > > the certificate chain for displaying and Kgpgcertmanager still > > uses the old one. That won't be too severe if it had put a > > limit on the maximum chain length to detect such a loop. I > > have always suggested to do this. A proper way of coding it > > would be something like: > > Do you have any idea how to make S/MIME chain work with KMail and > in sarge. Unfortunately, kleopatra is only part of KDE 3.3, and > there is only KDE 3.2.3 on sarge. And I really do not think like > fixing kgpgcertmanager myself (being just a lawyer :-). Hi, after being absent for a while, I now seem to have some more time again to play with KDE on debian again. I got a new IBM laptop on monday and installed sarge on it as the hassle with woody is just too time consuming for me to get everything running again with a 2.6 kernel etc and as it seems sarge is coming to a release stage later this year. I fought with the same problem for getting openpgp to work with kmail under sarge, and based on my prior experiences, I just compiled gpg 1.9's gpg-agent and copied that to /usr/local/bin, then changing my configuration files for pinentry-qt and gpg-agent to get everything to work again (though I don't use S/MIME). However, I'm still not satisfied as I really miss trying KDE 3.3. That makes me think it may be worth the effort of packaging 3.3.1 as soon as it comes out in the next weeks for sarge, doing the same for recent Aegypten packages and upload it somewhere like I did with woody packages before. Maybe that will help most people struggling with the same problems under sarge that they had with woody and running KDE3. Ralf > > Matej -- We're not a company, we just produce better code at less costs. -------------------------------------------------------------------- Ralf Nolden nolden@kde.org The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: signature Url : /pipermail/attachments/20041003/98c50556/attachment.bin From cepl at surfbest.net Sun Oct 3 22:40:58 2004 From: cepl at surfbest.net (Matej Cepl) Date: Sun Oct 3 23:34:06 2004 Subject: gpg 1.9 for Debian/sarge References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <873c0xhbst.fsf@wheatstone.g10code.de> <1664096.bORdIy5MbG@blahoslav.surfbest.net> <200410030744.20320.nolden@kde.org> Message-ID: <2164403.mzYJe4W7Ed@blahoslav.surfbest.net> Ralf Nolden wrote: > However, I'm still not satisfied as I really miss trying KDE > 3.3. That makes me think it may be worth the effort of > packaging 3.3.1 as soon as it comes out in the next weeks for > sarge, doing the same for recent Aegypten packages and upload > it somewhere like I did with woody packages before. Maybe that > will help most people struggling with the same problems under > sarge that they had with woody and running KDE3. Wouldn't it be more valuable to go Debian-way and fix all bugs in unstable which bar KDE 3.3 from getting into sarge? I know that there used to be a policy against KDE 3.3 in sarge, but it doesn't seem to be coming anytime soon (http://article.gmane.org/gmane.linux.debian.user.news/193 and particularly http://lists.debian.org/debian-devel-announce/2004/09/msg00005.html), so we could at leat hope to persuade Steve about allowing KDE 3.3 into sarge, if all bugs are fixed. What about that? Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 From bh at intevation.de Mon Oct 4 11:54:23 2004 From: bh at intevation.de (Bernhard Herzog) Date: Mon Oct 4 11:50:59 2004 Subject: gpg 1.9 for Debian/sarge In-Reply-To: <1664096.bORdIy5MbG@blahoslav.surfbest.net> (Matej Cepl's message of "Sat, 02 Oct 2004 20:08:52 -0400") References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <20040927181014.GB9642@intevation.de> <9315241.fkR0le72rs@blahoslav.surfbest.net> <40649858.PZpbcsNnRn@blahoslav.surfbest.net> <873c0xhbst.fsf@wheatstone.g10code.de> <1664096.bORdIy5MbG@blahoslav.surfbest.net> Message-ID: Matej Cepl writes: > Do you have any idea how to make S/MIME chain work with KMail and > in sarge. Unfortunately, kleopatra is only part of KDE 3.3, and > there is only KDE 3.2.3 on sarge. All the aegypten stuff in KDE is in kdepim which is still compatible with kde 3.2. We compile and run it with KDE 3.2.2 because that's the reference platform of the paying customer of the aegypten project. Bernhard -- Intevation GmbH http://intevation.de/ Skencil http://sketch.sourceforge.net/ Thuban http://thuban.intevation.org/ From nolden at kde.org Mon Oct 4 22:28:42 2004 From: nolden at kde.org (Ralf Nolden) Date: Mon Oct 4 22:25:22 2004 Subject: gpg 1.9 for Debian/sarge In-Reply-To: References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <1664096.bORdIy5MbG@blahoslav.surfbest.net> Message-ID: <200410042228.42396.nolden@kde.org> On Montag 04 Oktober 2004 11:54, Bernhard Herzog wrote: > Matej Cepl writes: > > Do you have any idea how to make S/MIME chain work with KMail and > > in sarge. Unfortunately, kleopatra is only part of KDE 3.3, and > > there is only KDE 3.2.3 on sarge. > > All the aegypten stuff in KDE is in kdepim which is still compatible > with kde 3.2. We compile and run it with KDE 3.2.2 because that's the > reference platform of the paying customer of the aegypten project. Very unlikely that people will make an exception just for aegypten. Even gnupg2 is missing in unstable, so I guess that it just won't be a part of testing anytime soon either. Ralf > > Bernhard -- We're not a company, we just produce better code at less costs. -------------------------------------------------------------------- Ralf Nolden nolden@kde.org The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org From aegypten-issues at intevation.de Tue Oct 5 19:10:32 2004 From: aegypten-issues at intevation.de (Bernhard Reiter) Date: Tue Oct 5 19:07:11 2004 Subject: [issue260] mutt crash when trying to view big s/mime mail Message-ID: <1096996232.01.0.372157559224.issue260@intevation.de> New submission from Bernhard Reiter : mutt CVS 20040916 with patch-1.5.6cvs.g10.mdn.3 patch-1.5.6cvs.g10.gpgme.6 (wrongly reported as .4) Got a huge mail encrypted when pressing "v" for view attachments I get a crash. (See dump bt below.) An attempt to decrypt it gives: Error: decryption failed: General error #0 0x40153404 in write () from /lib/libc.so.6 #1 0x4008b240 in __DTOR_END__ () from /usr/local/aegypten/lib/libgpgme.so.11 #2 0x40080178 in _gpgme_io_write (fd=19, buffer=0x40089203, count=3) at posix-io.c:96 #3 0x40085f16 in _gpgme__assuan_simple_write (ctx=0x816b548, buffer=0x40089203, size=3) at assuan-io.c:35 #4 0x40082b63 in writen (ctx=0x816b548, buffer=0x40089203 "BYE", length=3) at assuan-buffer.c:35 #5 0x400830af in _gpgme_assuan_write_line (ctx=0x816b548, line=0x40089203 "BYE") at assuan-buffer.c:258 #6 0x40084cbb in _gpgme_assuan_disconnect (ctx=0x816b548) at assuan-connect.c:42 #7 0x40085ba3 in _gpgme_assuan_pipe_connect (ctx=0x816b4c0, name=0x400884ed "/usr/local/proko2//bin/gpgsm", argv=0xbfffe630, fd_child_list=0xbfffe620) at assuan-pipe-connect.c:266 #8 0x4007e0d7 in gpgsm_new (engine=0x80d746c, lc_ctype=0x0, lc_messages=0x0) at engine-gpgsm.c:399 #9 0x4007a759 in _gpgme_engine_new (proto=GPGME_PROTOCOL_CMS, r_engine=0x8169414, lc_ctype=0x0, lc_messages=0x0) at engine.c:187 #10 0x4007418b in _gpgme_op_reset (ctx=0x8169410, type=1) at op-support.c:79 #11 0x40074c83 in decrypt_start (ctx=0x8169410, synchronous=1, cipher=0x8169470, plain=0x816a498) at decrypt.c:191 #12 0x40074d49 in gpgme_op_decrypt (ctx=0x8169410, cipher=0x8169470, plain=0x816a498) at decrypt.c:234 #13 0x080a0f12 in decrypt_part (a=0x8135458, s=0xbfffe8fc, fpout=0x81692a0, is_smime=1, r_is_signed=0xbfffe8f8) at crypt-gpgme.c:1475 #14 0x080a1450 in smime_gpgme_decrypt_mime (fpin=0x8116790, fpout=0xbfffeab0, b=0x8135458, cur=0xbfffeab4) at crypt-gpgme.c:1666 #15 0x080a5c67 in crypt_mod_smime_decrypt_mime (a=0x8116790, b=0xbfffeab0, c=0x8135458, d=0xbfffeab4) at crypt-mod-smime-gpgme.c:48 #16 0x080552c6 in crypt_smime_decrypt_mime (a=0x8116790, b=0xbfffeab0, c=0x8135458, d=0xbfffeab4) at cryptglue.c:283 #17 0x080891fa in mutt_view_attachments (hdr=0x81353a8) at recvattach.c:923 #18 0x08062079 in mutt_index_menu () at curs_main.c:2063 #19 0x08073129 in main (argc=3, argv=0xbffff964) at main.c:911 ---------- assignedto: werner messages: 1585 nosy: bernhard, bh, werner priority: bug status: unread title: mutt crash when trying to view big s/mime mail topic: mutt ______________________________________________________ Aegypten issue tracker ______________________________________________________ From cepl at surfbest.net Tue Oct 5 20:31:54 2004 From: cepl at surfbest.net (Matej Cepl) Date: Tue Oct 5 23:26:54 2004 Subject: gpg 1.9 for Debian/sarge References: <3134492.AjnBl1Xzxd@komensky.surfbest.net> <1664096.bORdIy5MbG@blahoslav.surfbest.net> <200410042228.42396.nolden@kde.org> Message-ID: <22393826.B3MabME2jG@blahoslav.surfbest.net> Ralf Nolden wrote: >> All the aegypten stuff in KDE is in kdepim which is still >> compatible with kde 3.2. We compile and run it with KDE 3.2.2 >> because that's the reference platform of the paying customer >> of the aegypten project. > > Very unlikely that people will make an exception just for > aegypten. Even gnupg2 is missing in unstable, so I guess that > it just won't be a part of testing anytime soon either. And would be there some good soul (Bernard? :-) making unofficial (untested and unmaintained) kleopatra package for testing? Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 From aegypten-issues at intevation.de Fri Oct 8 15:17:49 2004 From: aegypten-issues at intevation.de (Bernhard Reiter) Date: Fri Oct 8 15:14:30 2004 Subject: [issue261] Cannot verify deprecated non-MIME OpenPGP anymore Message-ID: <1097241469.53.0.161884338764.issue261@intevation.de> New submission from Bernhard Reiter : mutt cvs 20041006 patch-1.5.6cvs.g10.mdn.3 mutt-crl-too-old-20041004 patch-1.5.6cvs.g10.gpgme.6 (wrongly reporting .4) Trying to verify deprecated non-MIME OpenPGP now gives me: Error: decryption/verification failed: No data but in the status line it says: PGP Unterschrift erfolgreich ?berpr?ft. (means succesul verified.) On PGP/MIME message I do get a correct message including the warning that it is not clear that this cerficate belongs to the owner. gpg (1.2.5) and gpg2 can verify the saved email on the command line correctly. ---------- assignedto: werner messages: 1606 nosy: bernhard, bh, werner status: unread title: Cannot verify deprecated non-MIME OpenPGP anymore topic: mutt ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 13 18:16:09 2004 From: aegypten-issues at intevation.de (Marc Mutz) Date: Wed Oct 13 18:12:51 2004 Subject: [issue262] usability bug: searching in external certificates needs to be a separate window Message-ID: <1097684169.89.0.775360972315.issue262@intevation.de> New submission from Marc Mutz : Some points to describe why I come to this conclusion: 1. The local search should be immediate, w/o the need to hit the "find" button 2. Hierarchical key view doesn't make any sense for search results. 3. The "details" page doesn't make sense for external certs, but an "import" action makes the more sense there. ---------- assignedto: marc messages: 1645 nosy: marc priority: minor bug status: unread title: usability bug: searching in external certificates needs to be a separate window topic: certmanager ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Thu Oct 14 10:00:09 2004 From: aegypten-issues at intevation.de (Bernhard Reiter) Date: Thu Oct 14 09:56:46 2004 Subject: [issue263] curses pinentry does not work with mutt Message-ID: <1097740809.74.0.126914170015.issue263@intevation.de> New submission from Bernhard Reiter : The pinentries do not work for mutt without X11: Tested with pinentry-qt (pinentry) 0.7.2-cvs and pinentry-curses (pinentry) 0.7.2-cvs gpgsm -s x >x.sig works with pinentry-curses, but in mutt I cannot sign. Symptoms are that a connection to the pinentry is build, but its output cannot be seen and the input does not reach it. It is easy to test when doing ssh to a machine and not forwarding X11. ---------- assignedto: werner messages: 1650 nosy: bernhard, marcus, werner priority: bug status: unread title: curses pinentry does not work with mutt topic: mutt, pinentry ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Fri Oct 15 14:32:20 2004 From: aegypten-issues at intevation.de (Matt Douhan) Date: Fri Oct 15 14:28:57 2004 Subject: [issue264] KMail does not allow selection of gpg key for signing Message-ID: <1097843540.54.0.731185348373.issue264@intevation.de> New submission from Matt Douhan : When trying to select a key for signing, I can get to the dialog where it shows my available keys, but at this moment it starts a loop as follows new value) switch to reset Kleo::ProgressBar::setTotalSteps( 0 ) libkleopatra: Kleo::ProgressDialog::slotDone() libkleopatra: KeySelectionDialog::slotSelectionChanged() libkleopatra: KeySelectionDialog::slotCheckSelection() Kleo::ProgressBar::startStopBusyTimer() cur = -1; tot = 0; real = -1 (new value) switch to reset this loop never ends and it never makes the OK button active so I cannot get out of it either. rgds Matt ---------- messages: 1651 nosy: mdouhan priority: urgent status: unread title: KMail does not allow selection of gpg key for signing ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Fri Oct 15 16:47:36 2004 From: aegypten-issues at intevation.de (spiralvoice) Date: Fri Oct 15 16:44:23 2004 Subject: [issue265] pinentry: Compiling fails on Solaris 9 Message-ID: <1097851656.86.0.13852251233.issue265@intevation.de> New submission from spiralvoice : Compiling fails on Solaris 9 SPARC with gcc-3.3.5. According to http://groups.google.de/groups?hl=de&lr=&selm=7hrnrp%243e6c%241%40www.univie.ac.at getopt.h is not needed on Solaris, unistd.h does the job which is already used in pinentry.c, I removed getopt.h but compiling still fails: Making all in pinentry make[2]: Entering directory `/disk/sunray/sd2h/local/lude/soft/pinentry-0.7.1/src/default/sparc_sun_solaris2.9/pinentry-0.7.1/pinentry' if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../assuan -I../secmem -Wall -g -O2 -Wall -Wcast-align -Wshadow -Wstrict-prototypes -MT pinentry.o -MD -MP -MF ".deps/pinentry.Tpo" \ -c -o pinentry.o `test -f 'pinentry.c' || echo './'`pinentry.c; \ then mv -f ".deps/pinentry.Tpo" ".deps/pinentry.Po"; \ else rm -f ".deps/pinentry.Tpo"; exit 1; \ fi pinentry.c:28:20: getopt.h: No such file or directory pinentry.c: In function `pinentry_utf8_to_local': pinentry.c:114: warning: passing arg 2 of `libiconv' from incompatible pointer type pinentry.c: In function `pinentry_local_to_utf8': pinentry.c:180: warning: passing arg 2 of `libiconv' from incompatible pointer type pinentry.c: In function `pinentry_parse_opts': pinentry.c:289: error: elements of array `opts' have incomplete type pinentry.c:290: warning: excess elements in struct initializer pinentry.c:290: warning: (near initialization for `opts[0]') pinentry.c:290: error: `no_argument' undeclared (first use in this function) pinentry.c:290: error: (Each undeclared identifier is reported only once pinentry.c:290: error: for each function it appears in.) pinentry.c:290: warning: excess elements in struct initializer pinentry.c:290: warning: (near initialization for `opts[0]') pinentry.c:290: warning: excess elements in struct initializer pinentry.c:290: warning: (near initialization for `opts[0]') pinentry.c:290: warning: excess elements in struct initializer pinentry.c:290: warning: (near initialization for `opts[0]') pinentry.c:291: warning: excess elements in struct initializer pinentry.c:291: warning: (near initialization for `opts[1]') pinentry.c:291: error: `required_argument' undeclared (first use in this function) pinentry.c:291: warning: excess elements in struct initializer pinentry.c:291: warning: (near initialization for `opts[1]') pinentry.c:291: warning: excess elements in struct initializer pinentry.c:291: warning: (near initialization for `opts[1]') pinentry.c:291: warning: excess elements in struct initializer pinentry.c:291: warning: (near initialization for `opts[1]') pinentry.c:292: warning: excess elements in struct initializer pinentry.c:292: warning: (near initialization for `opts[2]') pinentry.c:292: warning: excess elements in struct initializer pinentry.c:292: warning: (near initialization for `opts[2]') pinentry.c:292: warning: excess elements in struct initializer pinentry.c:292: warning: (near initialization for `opts[2]') pinentry.c:292: warning: excess elements in struct initializer pinentry.c:292: warning: (near initialization for `opts[2]') pinentry.c:293: warning: excess elements in struct initializer pinentry.c:293: warning: (near initialization for `opts[3]') pinentry.c:293: warning: excess elements in struct initializer pinentry.c:293: warning: (near initialization for `opts[3]') pinentry.c:293: warning: excess elements in struct initializer pinentry.c:293: warning: (near initialization for `opts[3]') pinentry.c:293: warning: excess elements in struct initializer pinentry.c:293: warning: (near initialization for `opts[3]') pinentry.c:294: warning: excess elements in struct initializer pinentry.c:294: warning: (near initialization for `opts[4]') pinentry.c:294: warning: excess elements in struct initializer pinentry.c:294: warning: (near initialization for `opts[4]') pinentry.c:294: warning: excess elements in struct initializer pinentry.c:294: warning: (near initialization for `opts[4]') pinentry.c:294: warning: excess elements in struct initializer pinentry.c:294: warning: (near initialization for `opts[4]') pinentry.c:295: warning: excess elements in struct initializer pinentry.c:295: warning: (near initialization for `opts[5]') pinentry.c:295: warning: excess elements in struct initializer pinentry.c:295: warning: (near initialization for `opts[5]') pinentry.c:295: warning: excess elements in struct initializer pinentry.c:295: warning: (near initialization for `opts[5]') pinentry.c:295: warning: excess elements in struct initializer pinentry.c:295: warning: (near initialization for `opts[5]') pinentry.c:296: warning: excess elements in struct initializer pinentry.c:296: warning: (near initialization for `opts[6]') pinentry.c:296: warning: excess elements in struct initializer pinentry.c:296: warning: (near initialization for `opts[6]') pinentry.c:296: warning: excess elements in struct initializer pinentry.c:296: warning: (near initialization for `opts[6]') pinentry.c:296: warning: excess elements in struct initializer pinentry.c:296: warning: (near initialization for `opts[6]') pinentry.c:297: warning: excess elements in struct initializer pinentry.c:297: warning: (near initialization for `opts[7]') pinentry.c:297: warning: excess elements in struct initializer pinentry.c:297: warning: (near initialization for `opts[7]') pinentry.c:297: warning: excess elements in struct initializer pinentry.c:297: warning: (near initialization for `opts[7]') pinentry.c:297: warning: excess elements in struct initializer pinentry.c:297: warning: (near initialization for `opts[7]') pinentry.c:298: warning: excess elements in struct initializer pinentry.c:298: warning: (near initialization for `opts[8]') pinentry.c:298: warning: excess elements in struct initializer pinentry.c:298: warning: (near initialization for `opts[8]') pinentry.c:298: warning: excess elements in struct initializer pinentry.c:298: warning: (near initialization for `opts[8]') pinentry.c:298: warning: excess elements in struct initializer pinentry.c:298: warning: (near initialization for `opts[8]') pinentry.c:299: warning: excess elements in struct initializer pinentry.c:299: warning: (near initialization for `opts[9]') pinentry.c:299: warning: excess elements in struct initializer pinentry.c:299: warning: (near initialization for `opts[9]') pinentry.c:299: warning: excess elements in struct initializer pinentry.c:299: warning: (near initialization for `opts[9]') pinentry.c:299: warning: excess elements in struct initializer pinentry.c:299: warning: (near initialization for `opts[9]') pinentry.c:300: warning: excess elements in struct initializer pinentry.c:300: warning: (near initialization for `opts[10]') pinentry.c:300: warning: excess elements in struct initializer pinentry.c:300: warning: (near initialization for `opts[10]') pinentry.c:300: warning: excess elements in struct initializer pinentry.c:300: warning: (near initialization for `opts[10]') pinentry.c:300: warning: excess elements in struct initializer pinentry.c:300: warning: (near initialization for `opts[10]') pinentry.c:301: warning: excess elements in struct initializer pinentry.c:301: warning: (near initialization for `opts[11]') pinentry.c:301: warning: excess elements in struct initializer pinentry.c:301: warning: (near initialization for `opts[11]') pinentry.c:301: warning: excess elements in struct initializer pinentry.c:301: warning: (near initialization for `opts[11]') pinentry.c:301: warning: excess elements in struct initializer pinentry.c:301: warning: (near initialization for `opts[11]') pinentry.c:289: error: array size missing in `opts' pinentry.c:289: error: storage size of `opts' isn't known pinentry.c:303: warning: implicit declaration of function `getopt_long' pinentry.c:289: warning: unused variable `opts' make[2]: *** [pinentry.o] Error 1 ---------- messages: 1652 nosy: spiralvoice priority: bug status: unread title: pinentry: Compiling fails on Solaris 9 ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Sun Oct 17 23:24:32 2004 From: aegypten-issues at intevation.de (Marc Mutz) Date: Sun Oct 17 23:21:06 2004 Subject: [issue266] Fix for issue 39 breaks inline forwarding Message-ID: <1098048272.52.0.191945311463.issue266@intevation.de> New submission from Marc Mutz : See comments in issue 39. ---------- messages: 1669 nosy: ingo, khz, marc priority: bug status: unread title: Fix for issue 39 breaks inline forwarding topic: KMail ______________________________________________________ Aegypten issue tracker ______________________________________________________ From john at johnrshannon.com Fri Oct 22 17:49:11 2004 From: john at johnrshannon.com (John R. Shannon) Date: Fri Oct 22 17:45:52 2004 Subject: crl retrieval via http proxy Message-ID: <200410220949.11545.john@johnrshannon.com> What must I do to configure dirmngr to use a http proxy? If I execute: env http_proxy=http://192.168.1.4:3128/ dirmngr --fetch-crl http://onsitecrl.verisign.com/USGovernmentDODIECA3G2Encryption/LatestCRL.crl my firewall log shows a blocked attempt to access port 80 indicating the http_proxy environment variable is not honored. -- John R. Shannon, CISSP Sr. Software Scientist Science Applications International Corporation john.r.shannon@saic.com john@johnrshannon.com From aegypten-issues at intevation.de Sat Oct 23 19:38:20 2004 From: aegypten-issues at intevation.de (Bernhard Herzog) Date: Sat Oct 23 19:34:51 2004 Subject: [issue267] kontact/kmail does not encrypt correctly with gpg when a BCC: is set Message-ID: <1098553100.26.0.211883597468.issue267@intevation.de> New submission from Bernhard Herzog : There's a bug in the kde bugtracke that looks relevant for us. I haven't tried it myself yet, but we should investigate this: http://bugs.kde.org/show_bug.cgi?id=91697 ---------- assignedto: marc messages: 1715 nosy: bh, marc priority: bug status: unread title: kontact/kmail does not encrypt correctly with gpg when a BCC: is set topic: KMail ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Mon Oct 25 12:01:44 2004 From: aegypten-issues at intevation.de (Bernhard Reiter) Date: Mon Oct 25 11:58:20 2004 Subject: [issue268] --default-key not implemented Message-ID: <1098698504.12.0.527631487526.issue268@intevation.de> New submission from Bernhard Reiter : Only a minor bug as followup of issue249 Currently --default-keys is not implemented, but shown with --help and not warned upon in gpgsm.conf. (no documentation in gnupg.info though, so that is missing anyway.) ---------- assignedto: werner messages: 1717 nosy: bernhard, bh, werner priority: minor bug status: unread title: --default-key not implemented topic: gpgsm ______________________________________________________ Aegypten issue tracker ______________________________________________________ From bernhard at intevation.de Mon Oct 25 19:49:44 2004 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon Oct 25 19:46:23 2004 Subject: crl retrieval via http proxy In-Reply-To: <200410220949.11545.john@johnrshannon.com> References: <200410220949.11545.john@johnrshannon.com> Message-ID: <20041025174944.GA19953@intevation.de> On Fri, Oct 22, 2004 at 09:49:11AM -0600, John R. Shannon wrote: > What must I do to configure dirmngr to use a http proxy? I don't know. Can you file an issue with the issue tracker so we do not forget? > If I execute: > > env http_proxy=http://192.168.1.4:3128/ dirmngr --fetch-crl > http://onsitecrl.verisign.com/USGovernmentDODIECA3G2Encryption/LatestCRL.crl > > my firewall log shows a blocked attempt to access port 80 indicating the > http_proxy environment variable is not honored. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20041025/526f5fcd/attachment.bin From aegypten-issues at intevation.de Wed Oct 27 11:35:53 2004 From: aegypten-issues at intevation.de (Jan-Oliver Wagner) Date: Wed Oct 27 11:32:24 2004 Subject: [issue269] store message content unencrypted Message-ID: <1098869753.06.0.607975522315.issue269@intevation.de> New submission from Jan-Oliver Wagner : If I open an encrypted email I can not store its content unencrypted. This is a serious problem. When displaying only the encrypted part the save as method should store the clear text. Currently always the whole message is stored. Or is this a feature and KMail does not allow to store the content only? ---------- assignedto: marc messages: 1730 nosy: jan, marc priority: critical status: unread title: store message content unencrypted topic: KMail ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 27 11:49:45 2004 From: aegypten-issues at intevation.de (Jan-Oliver Wagner) Date: Wed Oct 27 11:46:16 2004 Subject: [issue270] OCSP: If configured wrongly: MUA hangs! Message-ID: <1098870585.05.0.513450559696.issue270@intevation.de> New submission from Jan-Oliver Wagner : If OCSP is enabled but a wrong server is configured (e.g. a wrong port), the MUA (ie KMail) hangs. Actually I would have expected some timeout, but apparently KMail hangs forever. ---------- assignedto: werner messages: 1733 nosy: jan, werner priority: critical status: unread title: OCSP: If configured wrongly: MUA hangs! topic: DirMngr ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 27 11:52:39 2004 From: aegypten-issues at intevation.de (Jan-Oliver Wagner) Date: Wed Oct 27 11:49:08 2004 Subject: [issue271] Mutt: muttrc config options not described in documentation Message-ID: <1098870759.67.0.158484893844.issue271@intevation.de> New submission from Jan-Oliver Wagner : The new options are not documented in Mutt. Ie. I found neither the option to enable the gpgme smime interface nor the option to set the default smime key nor ??? (whats also new?) ---------- assignedto: werner messages: 1734 nosy: jan, werner priority: critical status: unread title: Mutt: muttrc config options not described in documentation topic: mutt ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 27 12:24:58 2004 From: aegypten-issues at intevation.de (Marc Mutz) Date: Wed Oct 27 12:21:28 2004 Subject: [issue272] kmail: "signature is bad" when OpenPGP key is revoked. Message-ID: <1098872698.91.0.336550506154.issue272@intevation.de> New submission from Marc Mutz : Assigning to KMail for now, might be a backend problem, or might be a backend "feature". ---------- messages: 1738 nosy: marc status: unread title: kmail: "signature is bad" when OpenPGP key is revoked. topic: KMail ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 27 12:31:22 2004 From: aegypten-issues at intevation.de (Marc Mutz) Date: Wed Oct 27 12:27:51 2004 Subject: [issue273] libkleopatra/keyselection dialog: preselected key stays selected when clicking another one Message-ID: <1098873082.83.0.7115847912.issue273@intevation.de> New submission from Marc Mutz : You have to click the preselected key once, then a click on another key will make the original selection go away. ---------- assignedto: marc messages: 1740 nosy: marc priority: minor bug status: unread title: libkleopatra/keyselection dialog: preselected key stays selected when clicking another one topic: libkleopatra ______________________________________________________ Aegypten issue tracker ______________________________________________________ From aegypten-issues at intevation.de Wed Oct 27 16:02:07 2004 From: aegypten-issues at intevation.de (Jan-Oliver Wagner) Date: Wed Oct 27 15:58:38 2004 Subject: [issue274] crl retrieval via http: proxy not used Message-ID: <1098885727.24.0.689692276388.issue274@intevation.de> New submission from Jan-Oliver Wagner : A report from the gpa-dev mailing list by John R. Shannon, Oct 22 2004: Dirmngr seem not to use environment variable http_proxy. ---------- assignedto: werner messages: 1747 nosy: jan, werner priority: bug status: unread title: crl retrieval via http: proxy not used topic: DirMngr ______________________________________________________ Aegypten issue tracker ______________________________________________________ From jan at intevation.de Wed Oct 27 16:02:52 2004 From: jan at intevation.de (Jan-Oliver Wagner) Date: Wed Oct 27 15:59:22 2004 Subject: crl retrieval via http proxy In-Reply-To: <20041025174944.GA19953@intevation.de> References: <200410220949.11545.john@johnrshannon.com> <20041025174944.GA19953@intevation.de> Message-ID: <20041027140252.GE29943@intevation.de> On Mon, Oct 25, 2004 at 07:49:44PM +0200, Bernhard Reiter wrote: > On Fri, Oct 22, 2004 at 09:49:11AM -0600, John R. Shannon wrote: > > What must I do to configure dirmngr to use a http proxy? > > I don't know. > Can you file an issue with the issue tracker so we do not forget? Now, I did so: https://intevation.de/roundup/aegypten/issue274 -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From msansome at troodos.demon.co.uk Fri Oct 29 13:59:14 2004 From: msansome at troodos.demon.co.uk (Mark Sansome) Date: Fri Oct 29 13:55:44 2004 Subject: GPA - Bug fix + Enhancement Request Message-ID: <1099051153.2871.37.camel@localhost.localdomain> Dear all, I don't know if this is the appropriate forum in which to post this (2 part) message so I apologise in advance if I have got it wrong. Moreover, I could find no easy to search the archive so I am not sure if these points have been made before.... I have just successfully installed GPA v.0.7.0 and I am absolutely delighted with it. I do however have 2 points to make; one a "Bug report" (possibly) and the other an "enhancement request". 1) Bug report On very first loading of the software - if you already have a keyring with both public and private keys - the program still says something to the effect of "You do not have a private key - do you wish to create one now?" and will not allow any further action. "Cancel" does not work and even if you try to allow it to create a new key that does not work either. In fact the only possible action is to kill the process. Once you have killed the process and start it for a second time it finds the keys and works perfectly. Starting it the first time from a user account with no keys works correctly as intended. It should be relatively easy to recreate this fault. Make a couple of new user accounts - create a set of keys in one but not in the other - and then launch GPA in each account. Once again apologies if this has already been reported. 2) Enhancement request Once up and running I was delighted with GPA. There is however one aspect that I would like to see. As far as I can tell there is no means to perform the usual encrypt / decrypt etc. functions on text pasted in from the clipboard. Working only with saved files is a particular chore when posting text into web pages or when using anonymous email servers which require multiple encryption. Whilst I admit that my C++ skills extend only just beyond the realms of the "Hello World" program; it seems to me that this would be a relatively simple enhancement (?) and would vastly improve the usability of the application. It is found in most similar applications and, for me at least, would make this a supreme example of Open Source applications at their best. Please let my know if I have not explained myself very well. Once again I apologise if these points have been made before or if this is not the appropriate forum. Well done to all concerned for an excellent product. Best regards Mark From bernhard at intevation.de Fri Oct 29 14:17:01 2004 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri Oct 29 14:13:36 2004 Subject: GPA - Bug fix + Enhancement Request In-Reply-To: <1099051153.2871.37.camel@localhost.localdomain> References: <1099051153.2871.37.camel@localhost.localdomain> Message-ID: <20041029121701.GA23682@intevation.de> Hi Mark, this is certainly is the right forum. Thanks for the feedback on GPA. Bernhard On Fri, Oct 29, 2004 at 12:59:14PM +0100, Mark Sansome wrote: > I don't know if this is the appropriate forum in which to post this (2 > part) message so I apologise in advance if I have got it wrong. > Moreover, I could find no easy to search the archive so I am not sure if > these points have been made before.... > > I have just successfully installed GPA v.0.7.0 and I am absolutely > delighted with it. I do however have 2 points to make; one a "Bug > report" (possibly) and the other an "enhancement request". -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20041029/1bc3e062/attachment.bin From erik.wasser at iquer.net Sun Oct 31 23:24:58 2004 From: erik.wasser at iquer.net (Erik Wasser) Date: Sun Oct 31 23:21:32 2004 Subject: kmail doesn t sign/encrypt e-mails, broken pipe Message-ID: <200410312324.58710.erik.wasser@iquer.net> Hi list, I read "Using OpenPGP and PGP/MIME with KMail >= 1.7"[1] and installed a few libraries on my Gentoo System: dev-libs/pth-1.4.0 dev-libs/libksba-0.9.8 dev-libs/libassuan-0.6.6 app-crypt/gnupg-1.9.10 app-crypt/gpgme-0.9.0-r1 dev-libs/libgcrypt-1.1.94 The installation is so great that I can do the > echo "test" | gpg -ase -r 0xDEADBEEF | gpg 'trick' and the 'eval "$(gpg-agent --daemon)"' is working fine. I can read decrypted mails but I can't encrypting mails in kmail and that is bad. When I try to send a decrypted mail I enter the pass phrase and everything seems okay but when kmail really sends the mail I got an error box with "Encyption failed: Brocken pipe" What is the error here? What can I test so solve this problem? Any ideas? Is this a plugin error or an kmail error? I read also the bug reports[2][3] in kmail but I unsure what is the problem here. [1] http://kmail.kde.org/kmail-pgpmime-howto.html [2] http://bugs.kde.org/show_bug.cgi?id=85009 [3] http://bugs.kde.org/show_bug.cgi?id=83086 -- So long... Fuzz