Bug#311360: gnupg: introduces unnecessary dependence on USB dev support (i.e. not sug./rec.)

2005-06-01 Thread Werner Koch
On Tue, 31 May 2005 18:55:19 +0200, Georg Bauhaus said: > If there is a really convincing argument that a tool like > /usr/bin/gpg invented for signing and encrypting files must be aware Yes there is one: gpg supports smartcards and thus needs access to smartcard readers. It comes with an includ

Bug#310978: Please add support for ELG_E

2005-05-29 Thread Werner Koch
On Fri, 27 May 2005 06:57:23 -0500, Stephen R Marenka said: > This one line patch enables default support for Elgamal E. Maybe there's > a smarter way to do it, but it escaped me. There is no need for it. Although some algorithm numbers are taken from OpenPGP, this does not mean that we will cont

Bug#310805: gnupg: fully exportable armored homedir is completely impossible now!

2005-05-26 Thread Werner Koch
On Thu, 26 May 2005 02:22:06 -0700, t takahashi said: > another example of unnecessary accessing of homedir is when you want > to compress a file. when you do gpg --store, homedir access is unnecessary > but gpg tries to access it (perhaps to find preferences?). however, there is > no way to tur

Bug#310328: Bug #310328,Upgrading gnupg with open enigmail causes serious problem

2005-05-23 Thread Werner Koch
[Patrick, there seems to be a problem with gpg and enigmail when using large keyrings: gpg goes too sleep for a long time. Not sure whether you can clarify things.] On Mon, 23 May 2005 19:48:06 +0200, martin f krafft said: > What happens if you just leave it, go an play outside for a while, > c

Bug#299814: Bug#300859: gnupg RC bugs

2005-05-05 Thread Werner Koch
On Wed, 04 May 2005 14:08:05 +, Brian M Carlson said: > * Update to 1.4.1. I'd really prefer that. 1.4.1 has been released more than 6 weeks ago and fixes quite some bugs we figured out in 1.4.0. The case with 1.4.0 was that people don't care anymore about RC releases and start complaining o

Bug#307276: gnupg: Error importing Wouter's keys

2005-05-02 Thread Werner Koch
On Mon, 02 May 2005 12:28:15 +0300, Lars Wirzenius said: > I've no idea what happened. The is supposed to have key id AF79D29E > and importing it from the key server I use works fine. There is a bad formatted signature in the key: :signature packet: algo 17, keyid 432843E0AF3C67EA versio

Bug#304579: gpgme[-dev]

2005-04-13 Thread Werner Koch
On Thu, 14 Apr 2005 07:53:37 +0200, folkert said: > The gpgme in the Debian distribution is very much behind. The current > version of gpgme is 1.0.2. Quiet a bit has changed since the Debian- 0.3 is the old API used by some old software (e.g. sylpheed). You should use the libgpgme11 package whi

Bug#302905: gnupg: pop_filter(): filter function not found

2005-04-04 Thread Werner Koch
On Mon, 04 Apr 2005 08:07:13 +0100, Oliver Elphick said: > Since I can decrypt stuff, I assume that would be the public keyring? > If so, how can I clean it up? Restore it from a backup. I think it is better to continue such a discussion on the gnupg users mailing list. You need to figure out h

Bug#302905: gnupg: pop_filter(): filter function not found

2005-04-03 Thread Werner Koch
On Sun, 03 Apr 2005 19:13:33 +0100, Oliver Elphick said: > This appears to be related to the contents of my .gnupg, because the Would you mind to tell us what is special about your gpg.conf? If you don't want to see this in the BTS, please send it to me by PM. My guess is that your keyring is c

Bug#301627: gnupg: Default key signing level change causes confusion

2005-03-29 Thread Werner Koch
On Sun, 27 Mar 2005 12:13:19 +0200, RÃmi Denis-Courmont said: > I think the "ask-cert-level" option should really be re-enabled by > default. We changed this on purpose. The cert levels have never been used in the past and due to the different intepretation people assign to them, their meaning i

Bug#299814: GnuPG 1.2.5 selects wrong encryption keys

2005-03-23 Thread Werner Koch
On Wed, 23 Mar 2005 00:40:23 -0800, Steve Langasek said: > Given that this bug is marked "grave", should gnupg 1.4.0-3 be pushed into > testing, or is there another fix we should prefer here? Although I'd prefer to see 1.4.1 in testing, updating to 1.2.7 would solve this bug. Shalom-Salam,

Bug#300743: gnupg: Should not depend on libusb

2005-03-21 Thread Werner Koch
On Mon, 21 Mar 2005 15:55:31 +0100, Frans Pop said: > I feel it is not very nice packaging, especially for something like gnupg > that is very general purpose and that is priority standard, to depend on > a hardware specific library. libusb is by design not hardware dependedn. If USB is not su

Bug#297253: /usr/bin/gpg: missing dependencies

2005-03-02 Thread Werner Koch
On Mon, 28 Feb 2005 10:12:27 +0100, Sythos said: > missing libpcsclite1 dependencies Note, that is not a hard dependency because libpcsclite is dlopened and even not needed if a CCID reader has been setup properly. Shalom-Salam, Werner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#296128: localicing don't work properly

2005-02-21 Thread Werner Koch
On Mon, 21 Feb 2005 13:13:25 +0100, Klaus Ethgen said: > Hmm... But the possition seems to be correct as I looked to the source. > But what do this "fuzzy" mean concretely in this case? That is a term from the GNU gettext system. If it dedects changed or new strings it tries a fuzzy macth to ma

Bug#296128: localicing don't work properly

2005-02-21 Thread Werner Koch
On Sun, 20 Feb 2005 15:13:44 +0100, Klaus Ethgen said: > The following text is not localiced (to german) even thought it is in > the de.po file. But marked as fuzzy. There are a lot of outdated translations. I don't think that it is a good idea to file a bug for every outdated language. For de

Bug#295718: gnupg: sha1 is broken

2005-02-18 Thread Werner Koch
On Thu, 17 Feb 2005 17:43:51 +0100, Markus Schaber said: > GnuPG should be changed to give strong warings whenever SHA-1 is used, and > maybe disable the usage of SHA-1 for new signatures altogether. No. Broken is used by Bruce in a way cryptographers use it. IT is far far away from any practic

Bug#275188: decrypt-saving still deleting messages?

2005-01-17 Thread Werner Koch
On Sun, 16 Jan 2005 13:03:47 +0100, Thomas Roessler said: > The problem here is that PGP exit values are nontrivial. To give > just one example, gpg will return exit status 1 when it encounters a > bad signature; I'm not sure right now whether this includes a Don't rely on that. 1 is usually us

<    1   2   3   4   5