From wk at gnupg.org Thu Jun 2 12:03:25 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Jun 2 12:00:58 2005 Subject: gnupg-1.4.1 In-Reply-To: <200505290650.54771.john@johnrshannon.com> (John R. Shannon's message of "Sun, 29 May 2005 06:50:49 -0600") References: <200505290650.54771.john@johnrshannon.com> Message-ID: <874qchxehe.fsf@wheatstone.g10code.de> On Sun, 29 May 2005 06:50:49 -0600, John R Shannon said: > Test problems: > 1. Algorithm name returned by gpg is uppercase and script checks for lowercase > name > 2. Incorrect algorithm matching (eg., idea for BLOWFISH) Thanks. I fixed that in CVS. Shalom-Salam, Werner From wk at gnupg.org Thu Jun 2 12:08:16 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Jun 2 12:05:57 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <200505311437.53327.kuenne@rentec.com> ( =?utf-8?q?Karsten_K=C3=BCnne's_message_of?= "Tue, 31 May 2005 14:37:44 -0400") References: <200505311437.53327.kuenne@rentec.com> Message-ID: <87zmu9vzov.fsf@wheatstone.g10code.de> On Tue, 31 May 2005 14:37:44 -0400, Karsten K?nne said: > The gpg-agent is running and GPG_AGENT_INFO is set correctly. Does anybody > know what's going on here? It does not find pinentry for reasons I don't know. The easiest workaround is to add a line like pinentry-program /usr/lib/pinentry/pinentry-gtk to gpg-agent.conf. Replace gtk by qt or gtk2 according on your taste. Also try to run pinnetry using exactly the filename as given in that line. Salam-Shalom, Werner From wk at gnupg.org Thu Jun 2 13:03:27 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Jun 2 13:01:00 2005 Subject: GPA and OpenPGP Cryptocard In-Reply-To: <20050531190622.5927644b.mario@codehack.org> (Mario Fuerderer's message of "Tue, 31 May 2005 19:06:22 +0200") References: <20050516232645.5651d46d.mario@codehack.org> <20050531160322.GE20045@intevation.de> <20050531190622.5927644b.mario@codehack.org> Message-ID: <87vf4xvx4w.fsf@wheatstone.g10code.de> On Tue, 31 May 2005 19:06:22 +0200, Mario Fuerderer said: > fd 7: got `[GNUPG:] NEED_PASSPHRASE_PIN OPENPGP 1 2004-10-15 Werner Koch * status.h (STATUS_NEED_PASSPHRASE_PIN): New. * status.c (get_status_string): Added. * passphrase.c (ask_passphrase): Moved status printing to .. * cardglue.c (pin_cb): .. here and issue new status message. So it is my fault. Someone requested to have a new status message for PIN and I have implemented this without thinking about possible breaking other code. In particular gpgme does not know about this new status message and is thus won't call the passphrase callback. I will change this in gpgme. The workaround and preferable soultion is to use gpg-agent. Shalom-Salam, Werner From wk at gnupg.org Thu Jun 2 13:17:18 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Jun 2 13:15:57 2005 Subject: GPA and OpenPGP Cryptocard In-Reply-To: <20050531190622.5927644b.mario@codehack.org> (Mario Fuerderer's message of "Tue, 31 May 2005 19:06:22 +0200") References: <20050516232645.5651d46d.mario@codehack.org> <20050531160322.GE20045@intevation.de> <20050531190622.5927644b.mario@codehack.org> Message-ID: <87r7flvwht.fsf@wheatstone.g10code.de> Hi! would you mind to check out the latest gpgme from CVS? It should allow you to enter the PIN. I have commited the changes to HEAD as well as the gpgme-1-0-branch. cvs -d :pserver:anoncvs@cvs.gnupg.org:/cvs/gnupg co gpgme Salam-Shalom, Werner From kuenne at rentec.com Thu Jun 2 22:42:09 2005 From: kuenne at rentec.com (Karsten =?utf-8?q?K=C3=BCnne?=) Date: Thu Jun 2 22:38:47 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <87zmu9vzov.fsf@wheatstone.g10code.de> References: <200505311437.53327.kuenne@rentec.com> <87zmu9vzov.fsf@wheatstone.g10code.de> Message-ID: <200506021642.15863.kuenne@rentec.com> On Thursday 02 June 2005 06:08, Werner Koch wrote: > On Tue, 31 May 2005 14:37:44 -0400, Karsten K?nne said: > > The gpg-agent is running and GPG_AGENT_INFO is set correctly. Does > > anybody know what's going on here? > > It does not find pinentry for reasons I don't know. The easiest > workaround is to add a line like > > pinentry-program /usr/lib/pinentry/pinentry-gtk > > to gpg-agent.conf. Replace gtk by qt or gtk2 according on your taste. > Also try to run pinnetry using exactly the filename as given in that > line. > The pinentry is not the issue, I configured it in gpg-agent.conf and it is found. I looked a bit deeper and apparently someone is talking garbage to the gpg-agent program. Following is from the agent's debug log: ... 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION display=:0.0 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION lc-ctype=en_US.UTF-8 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION lc-messages=en_US.UTF-8 That are the options the agent supposedly gets. BUT, somebody is lying here! Because this is what I can see if I strace the agent: 19760 read(0, "OPTION display=:0.0", 1002) = 19 19760 read(0, "OPTION lc-ctype=en_US.UTF-8", 1002) = 27 19760 read(0, "OPTION display=en_US.UTF-8", 1002) = 26 So, the first and second option are correct but the third one is garbage. The debug output says it's "lc-ctype=en_US.UTF8" but what the agent gets is "display=en_US.UTF8" which is completely bogus. And as a result pinentry fails to open the display. Now the question is where does that bogus option come from? Is it kmail which is talking to gpg-agent directly or is gpgme involved? I have no idea how the chain of command works in kmail from KDE 3.4.1. The interesting thing is that it works fine in the OpenPGP/Mime case (except for the fact that it apparently doesn't like german umlauts in the "To" header but that's another issue). Karsten. -- If you think education is expensive, try ignorance. -- Derek Bok, president of Harvard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20050602/1d256667/attachment.pgp From kuenne at rentec.com Thu Jun 2 22:55:29 2005 From: kuenne at rentec.com (Karsten =?utf-8?q?K=C3=BCnne?=) Date: Thu Jun 2 22:51:47 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <200506021642.15863.kuenne@rentec.com> References: <200505311437.53327.kuenne@rentec.com> <87zmu9vzov.fsf@wheatstone.g10code.de> <200506021642.15863.kuenne@rentec.com> Message-ID: <200506021655.35312.kuenne@rentec.com> On Thursday 02 June 2005 16:42, Karsten K?nne wrote: > On Thursday 02 June 2005 06:08, Werner Koch wrote: > > On Tue, 31 May 2005 14:37:44 -0400, Karsten K?nne said: > > > The gpg-agent is running and GPG_AGENT_INFO is set correctly. Does > > > anybody know what's going on here? > > > > It does not find pinentry for reasons I don't know. The easiest > > workaround is to add a line like > > > > pinentry-program /usr/lib/pinentry/pinentry-gtk > > > > to gpg-agent.conf. Replace gtk by qt or gtk2 according on your taste. > > Also try to run pinnetry using exactly the filename as given in that > > line. > > The pinentry is not the issue, I configured it in gpg-agent.conf and it is > found. I looked a bit deeper and apparently someone is talking garbage to > the gpg-agent program. Following is from the agent's debug log: > > ... > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION display=:0.0 > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > lc-ctype=en_US.UTF-8 > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > lc-messages=en_US.UTF-8 > > That are the options the agent supposedly gets. BUT, somebody is lying > here! Because this is what I can see if I strace the agent: > > 19760 read(0, "OPTION display=:0.0", 1002) = 19 > 19760 read(0, "OPTION lc-ctype=en_US.UTF-8", 1002) = 27 > 19760 read(0, "OPTION display=en_US.UTF-8", 1002) = 26 > > So, the first and second option are correct but the third one is garbage. > The debug output says it's "lc-ctype=en_US.UTF8" but what the agent gets is > "display=en_US.UTF8" which is completely bogus. And as a result pinentry > fails to open the display. Now the question is where does that bogus option > come from? Is it kmail which is talking to gpg-agent directly or is gpgme > involved? I have no idea how the chain of command works in kmail from KDE > 3.4.1. Forget that last sentence, it's of course gpgsm which is screwing things up here. SUSE ships version 1.9.14. I'll have a look at it and see why it's talking garbage to the agent. Karsten. -- Living on Earth may be expensive, but it includes an annual free trip around the Sun. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20050602/ee5c727b/attachment.pgp From kuenne at rentec.com Fri Jun 3 00:12:09 2005 From: kuenne at rentec.com (Karsten =?utf-8?q?K=C3=BCnne?=) Date: Fri Jun 3 00:08:31 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <200506021655.35312.kuenne@rentec.com> References: <200505311437.53327.kuenne@rentec.com> <200506021642.15863.kuenne@rentec.com> <200506021655.35312.kuenne@rentec.com> Message-ID: <200506021812.14980.kuenne@rentec.com> On Thursday 02 June 2005 16:55, Karsten K?nne wrote: > On Thursday 02 June 2005 16:42, Karsten K?nne wrote: > > On Thursday 02 June 2005 06:08, Werner Koch wrote: > > > On Tue, 31 May 2005 14:37:44 -0400, Karsten K?nne said: > > > > The gpg-agent is running and GPG_AGENT_INFO is set correctly. Does > > > > anybody know what's going on here? > > > > > > It does not find pinentry for reasons I don't know. The easiest > > > workaround is to add a line like > > > > > > pinentry-program /usr/lib/pinentry/pinentry-gtk > > > > > > to gpg-agent.conf. Replace gtk by qt or gtk2 according on your taste. > > > Also try to run pinnetry using exactly the filename as given in that > > > line. > > > > The pinentry is not the issue, I configured it in gpg-agent.conf and it > > is found. I looked a bit deeper and apparently someone is talking garbage > > to the gpg-agent program. Following is from the agent's debug log: > > > > ... > > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > display=:0.0 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > lc-ctype=en_US.UTF-8 > > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > lc-messages=en_US.UTF-8 > > > > That are the options the agent supposedly gets. BUT, somebody is lying > > here! Because this is what I can see if I strace the agent: > > > > 19760 read(0, "OPTION display=:0.0", 1002) = 19 > > 19760 read(0, "OPTION lc-ctype=en_US.UTF-8", 1002) = 27 > > 19760 read(0, "OPTION display=en_US.UTF-8", 1002) = 26 > > > > So, the first and second option are correct but the third one is garbage. > > The debug output says it's "lc-ctype=en_US.UTF8" but what the agent gets > > is "display=en_US.UTF8" which is completely bogus. And as a result > > pinentry fails to open the display. Now the question is where does that > > bogus option come from? Is it kmail which is talking to gpg-agent > > directly or is gpgme involved? I have no idea how the chain of command > > works in kmail from KDE 3.4.1. > > Forget that last sentence, it's of course gpgsm which is screwing things up > here. SUSE ships version 1.9.14. I'll have a look at it and see why it's > talking garbage to the agent. > > O.k., I keep following up to myself. Looks like gnupg-1.9.14 has a "brown paper bag" bug in common/asshelp.c ;-). It's fixed in 1.9.15, SUSE apparently shipped a broken version of gpg2 in 9.3. Karsten. -- "Not Hercules could have knock'd out his brains, for he had none." -- Shakespeare -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20050602/5b9ecee2/attachment-0001.pgp From mario at codehack.org Fri Jun 3 14:16:42 2005 From: mario at codehack.org (Mario Fuerderer) Date: Fri Jun 3 14:12:50 2005 Subject: GPA and OpenPGP Cryptocard In-Reply-To: <87r7flvwht.fsf@wheatstone.g10code.de> References: <20050516232645.5651d46d.mario@codehack.org> <20050531160322.GE20045@intevation.de> <20050531190622.5927644b.mario@codehack.org> <87r7flvwht.fsf@wheatstone.g10code.de> Message-ID: <20050603141642.5844e60b.mario@codehack.org> Hi, On Thu, 02 Jun 2005 13:17:18 +0200 Werner Koch wrote: > cvs -d :pserver:anoncvs@cvs.gnupg.org:/cvs/gnupg co gpgme thanks, for the quick fix in the cvs, Werner! :-) GPA as well as Sylpheed are working like a charm now... greetings Mario -- Mario F?rderer From bernhard at intevation.de Fri Jun 3 15:17:08 2005 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri Jun 3 15:12:54 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <200506021812.14980.kuenne@rentec.com> References: <200505311437.53327.kuenne@rentec.com> <200506021642.15863.kuenne@rentec.com> <200506021655.35312.kuenne@rentec.com> <200506021812.14980.kuenne@rentec.com> Message-ID: <20050603131708.GD20444@intevation.de> On Thu, Jun 02, 2005 at 06:12:09PM -0400, Karsten K?nne wrote: > On Thursday 02 June 2005 16:55, Karsten K?nne wrote: > > On Thursday 02 June 2005 16:42, Karsten K?nne wrote: > O.k., I keep following up to myself. No problem, this is a lot better than to keep quiet and suffer. It is good to see the issue fixed. > Looks like gnupg-1.9.14 has a "brown > paper bag" bug in common/asshelp.c ;-). It's fixed in 1.9.15, SUSE apparently > shipped a broken version of gpg2 in 9.3. Note that the "gpg2" binary itself should not be used for production, only gpg-agent and gpgsm is good to use. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20050603/b7c0e23e/attachment.pgp From wk at gnupg.org Fri Jun 3 14:11:16 2005 From: wk at gnupg.org (Werner Koch) Date: Fri Jun 3 15:33:23 2005 Subject: S/MIME signing fails on a SUSE 9.3 system In-Reply-To: <200506021812.14980.kuenne@rentec.com> ( =?utf-8?q?Karsten_K=C3=BCnne's_message_of?= "Thu, 2 Jun 2005 18:12:09 -0400") References: <200505311437.53327.kuenne@rentec.com> <200506021642.15863.kuenne@rentec.com> <200506021655.35312.kuenne@rentec.com> <200506021812.14980.kuenne@rentec.com> Message-ID: <87br6nd4ij.fsf@wheatstone.g10code.de> On Thu, 2 Jun 2005 18:12:09 -0400, Karsten K?nne said: > O.k., I keep following up to myself. Looks like gnupg-1.9.14 has a "brown > paper bag" bug in common/asshelp.c ;-). It's fixed in 1.9.15, SUSE apparently > shipped a broken version of gpg2 in 9.3. Ah well: 2005-01-03 Werner Koch * asshelp.c (send_pinentry_environment): Fixed changed from 2004-12-18; cut+paste error for lc-messages. Shalom-Salam, Werner From peter_e at gmx.net Wed Jun 15 19:59:50 2005 From: peter_e at gmx.net (Peter Eisentraut) Date: Wed Jun 15 20:55:58 2005 Subject: pinentry-curses segfaults after confirm Message-ID: <200506151959.51220.peter_e@gmx.net> A Debian user reported (bug #311410) the following, which I can confirm: On my system i can make pinentry-curses segfault by doing the following: - start pinentry without options - request confirmation by sending a single line "confirm\n" to it - answer that confirmation request in any way From peter_e at gmx.net Wed Jun 15 20:02:15 2005 From: peter_e at gmx.net (Peter Eisentraut) Date: Wed Jun 15 20:58:19 2005 Subject: pinentry-qt hangs when pressing Menu key then Esc Message-ID: <200506152002.15949.peter_e@gmx.net> A Debian user reported (bug #303508) the following, which I can confirm: To reproduce this bug, you must have a keyboard with a Menu key (or some other key, I suppose) that is mapped to open a context menu. I believe this is the default mapping for this key, if you have it. (On my keyboard, the Menu key is between the right Logo key and the right Ctrl key.) 1. from a terminal, run pinentry-qt 2. type getpin (a pin entry dialog box should appear) 3. in the dialog box, press the Menu key (a context menu should appear) 4. press Esc At this point, the dialog box will dissappear, but no response will be returned to the terminal. (If you omit step 3, you will get the response "ERR 111 canceled", which is what we want.) This bug manifested itself to me as kmail hanging after I accidentally mistyped my passphrase (by hitting the Menu key instead of Shift, which is right above it) and then hitting Esc to get a fresh start. At this point the context menu was showing, and it hung as described, and kmail hung too because it was still waiting for a response. (Note that if you get the context menu for the line edit using the right mouse button instead of the Menu key, this bug does not appear.) Also, other apps that use a line edit do not behave this way; for example, to see the expected behaviour, do this: 1. run kdialog --inputbox test 2. follow steps 3-4 above From kloecker at kde.org Wed Jun 15 22:22:36 2005 From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=) Date: Wed Jun 15 22:59:24 2005 Subject: pinentry-qt hangs when pressing Menu key then Esc In-Reply-To: <200506152002.15949.peter_e@gmx.net> References: <200506152002.15949.peter_e@gmx.net> Message-ID: <200506152222.44276@erwin.ingo-kloecker.de> On Wednesday 15 June 2005 20:02, Peter Eisentraut wrote: > A Debian user reported (bug #303508) the following, which I can > confirm: > > To reproduce this bug, you must have a keyboard with a Menu key (or > some other key, I suppose) that is mapped to open a context menu. I > believe this is the default mapping for this key, if you have it. > (On my keyboard, the Menu key is between the right Logo key and the > right Ctrl key.) > > 1. from a terminal, run pinentry-qt > 2. type getpin (a pin entry dialog box should appear) > 3. in the dialog box, press the Menu key (a context menu should > appear) 4. press Esc > > At this point, the dialog box will dissappear, but no response will > be returned to the terminal. (If you omit step 3, you will get the > response "ERR 111 canceled", which is what we want.) > > This bug manifested itself to me as kmail hanging after I > accidentally mistyped my passphrase (by hitting the Menu key instead > of Shift, which is right above it) and then hitting Esc to get a > fresh start. At this point the context menu was showing, and it hung > as described, and kmail hung too because it was still waiting for a > response. > > (Note that if you get the context menu for the line edit using the > right mouse button instead of the Menu key, this bug does not > appear.) > > Also, other apps that use a line edit do not behave this way; for > example, to see the expected behaviour, do this: > 1. run kdialog --inputbox test > 2. follow steps 3-4 above This problem is very likely due to pinentry-qt grabbing the keyboard (in order to prevent what exactly?). I had to add some hacks to KMail to prevent it from decrypting a message when a context menu was shown because otherwise X would hang and the only way to fix it is to kill pinentry-qt by remotely logging in. Obviously the context menu and pinentry-qt both tried to grab the keyboard and deadlocked or whatever. Regards, Ingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20050615/61e06a28/attachment.pgp From marcus.brinkmann at ruhr-uni-bochum.de Thu Jun 16 02:08:13 2005 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Thu Jun 16 02:05:26 2005 Subject: pinentry-curses segfaults after confirm In-Reply-To: <200506151959.51220.peter_e@gmx.net> References: <200506151959.51220.peter_e@gmx.net> Message-ID: <871x73cgeq.wl@ulysses.g10code.de> At Wed, 15 Jun 2005 19:59:50 +0200, Peter Eisentraut wrote: > > A Debian user reported (bug #311410) the following, which I can confirm: > > On my system i can make pinentry-curses segfault by doing the following: > - start pinentry without options > - request confirmation by sending a single line "confirm\n" to it > - answer that confirmation request in any way Thanks for the report. This is now fixed in CVS: 2005-06-16 Marcus Brinkmann * pinentry/pinentry-curses.c (dialog_run): Only convert pin if a pin actually exists. Marcus From marcus.brinkmann at ruhr-uni-bochum.de Thu Jun 16 02:18:47 2005 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Thu Jun 16 02:15:22 2005 Subject: pinentry-qt hangs when pressing Menu key then Esc In-Reply-To: <200506152222.44276@erwin.ingo-kloecker.de> References: <200506152002.15949.peter_e@gmx.net> <200506152222.44276@erwin.ingo-kloecker.de> Message-ID: <87zmtrb1co.wl@ulysses.g10code.de> At Wed, 15 Jun 2005 22:22:36 +0200, Ingo Kl?cker wrote: > > [1 ] > [1.1 ] > On Wednesday 15 June 2005 20:02, Peter Eisentraut wrote: > > A Debian user reported (bug #303508) the following, which I can > > confirm: > > > > To reproduce this bug, you must have a keyboard with a Menu key (or > > some other key, I suppose) that is mapped to open a context menu. I > > believe this is the default mapping for this key, if you have it. > > (On my keyboard, the Menu key is between the right Logo key and the > > right Ctrl key.) > > > > 1. from a terminal, run pinentry-qt > > 2. type getpin (a pin entry dialog box should appear) > > 3. in the dialog box, press the Menu key (a context menu should > > appear) 4. press Esc > > > > At this point, the dialog box will dissappear, but no response will > > be returned to the terminal. (If you omit step 3, you will get the > > response "ERR 111 canceled", which is what we want.) Oh, well. > This problem is very likely due to pinentry-qt grabbing the keyboard (in > order to prevent what exactly?). pinentries like to grab keyboard and mouse to prevent you from accidentially typing your PIN or passphrase into a terminal window or your IRC input line :) If you don't like it, there is a --no-grab option. pinentry doesn't parse any config files, but the option is passed through by gpg-agent if you put it into .gnupg/gpg-agent.conf, I think. This would also be a work around for the menu key problem, I'd guess. > I had to add some hacks to KMail to > prevent it from decrypting a message when a context menu was shown > because otherwise X would hang and the only way to fix it is to kill > pinentry-qt by remotely logging in. Obviously the context menu and > pinentry-qt both tried to grab the keyboard and deadlocked or whatever. Can we disable this conflicting grab in pinentry-qt somehow? Mmh. Marcus From wk at gnupg.org Thu Jun 16 10:40:16 2005 From: wk at gnupg.org (Werner Koch) Date: Thu Jun 16 10:41:11 2005 Subject: pinentry-qt hangs when pressing Menu key then Esc In-Reply-To: <87zmtrb1co.wl@ulysses.g10code.de> (Marcus Brinkmann's message of "Thu, 16 Jun 2005 02:18:47 +0200") References: <200506152002.15949.peter_e@gmx.net> <200506152222.44276@erwin.ingo-kloecker.de> <87zmtrb1co.wl@ulysses.g10code.de> Message-ID: <87oea6k83z.fsf@wheatstone.g10code.de> On Thu, 16 Jun 2005 02:18:47 +0200, Marcus Brinkmann said: > pinentries like to grab keyboard and mouse to prevent you from > accidentially typing your PIN or passphrase into a terminal window or > your IRC input line :) and to make it harder for other applications to snoop the PIN by grabbing the keyboard. Only one application may grab it and thus the hang is actually on purpose. This is the usual countermeasure on X to avoid such attacks. In the dark old times of xhost it used to be popular to read what co-workers typed on their keyboards. Shalom-Salam, Werner From lofi at freebsd.org Wed Jun 29 13:54:04 2005 From: lofi at freebsd.org (Michael Nottebrock) Date: Wed Jun 29 13:49:45 2005 Subject: [Announce] GnuPG 1.9.17 (S/MIME and gpg-agent) released In-Reply-To: <87ll5494wv.fsf@wheatstone.g10code.de> References: <87ll5494wv.fsf@wheatstone.g10code.de> Message-ID: <200506291354.08168.lofi@freebsd.org> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : /pipermail/attachments/20050629/44871ca7/attachment-0001.pgp From wk at gnupg.org Wed Jun 29 15:49:46 2005 From: wk at gnupg.org (Werner Koch) Date: Wed Jun 29 15:46:15 2005 Subject: [Announce] GnuPG 1.9.17 (S/MIME and gpg-agent) released In-Reply-To: <200506291354.08168.lofi@freebsd.org> (Michael Nottebrock's message of "Wed, 29 Jun 2005 13:54:04 +0200") References: <87ll5494wv.fsf@wheatstone.g10code.de> <200506291354.08168.lofi@freebsd.org> Message-ID: <87ll4t9ssl.fsf@wheatstone.g10code.de> On Wed, 29 Jun 2005 13:54:04 +0200, Michael Nottebrock said: > gcry_mpi_t sig_value = NULL; > - unsigned char *sig_blob = NULL;; > + unsigned char *sig_blob = NULL; This is indeed an error. Mixing declaration and statements (the empty one here) is not allowed by C-89. Anyone knows whether gcc 4.0 has an option to detect this again? Thanks, Werner From lofi at freebsd.org Mon Jun 27 15:42:46 2005 From: lofi at freebsd.org (Michael Nottebrock) Date: Thu Jun 30 05:31:47 2005 Subject: [Announce] GnuPG 1.9.17 (S/MIME and gpg-agent) released In-Reply-To: <87ll5494wv.fsf@wheatstone.g10code.de> References: <87ll5494wv.fsf@wheatstone.g10code.de> Message-ID: <200506271542.46841.lofi@freebsd.org> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : /pipermail/attachments/20050627/e34eaee0/attachment.pgp From peter_e at gmx.net Thu Jun 30 13:05:50 2005 From: peter_e at gmx.net (Peter Eisentraut) Date: Thu Jun 30 14:03:55 2005 Subject: dirmngr: PO file corrections Message-ID: <200506301305.51105.peter_e@gmx.net> A Debian user submitted the attached corrections to the German PO file of dirmngr. Please include them in your code. -------------- next part -------------- A non-text attachment was scrubbed... Name: dirmngr_0.9.1-2_de.po.diff.gz Type: application/x-gzip Size: 1788 bytes Desc: not available Url : /pipermail/attachments/20050630/bc817cc8/dirmngr_0.9.1-2_de.po.diff.bin From lofi at freebsd.org Thu Jun 30 15:41:15 2005 From: lofi at freebsd.org (Michael Nottebrock) Date: Thu Jun 30 15:37:05 2005 Subject: dirmngr: PO file corrections In-Reply-To: <200506301305.51105.peter_e@gmx.net> References: <200506301305.51105.peter_e@gmx.net> Message-ID: <200506301541.28178.lofi@freebsd.org> On Thursday, 30. June 2005 13:05, Peter Eisentraut wrote: > A Debian user submitted the attached corrections to the German PO file of > dirmngr. Please include them in your code. I doubt that "gecacht" is better german than "gecachet" - if it's german at all ... how about "Zertifikat wurde zwischengespeichert"? :-) -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : /pipermail/attachments/20050630/5064b6c1/attachment.pgp