[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#466930: marked as done (hkp search+import fails on keyids of more than 4 bytes)

Your message dated Sun, 12 Jul 2009 14:23:28 -0300
with message-id <200907121423.28383.perezmeyer@gmail.com>
and subject line Closing
has caused the Debian Bug report #466930,
regarding hkp search+import fails on keyids of more than 4 bytes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
466930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466930
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kgpg
Version: 4:3.5.8-1
Severity: normal

--- Please enter the report below this line. ---

When working with e.g. the keyserver onak 0.3.5-1 available in Debian,
kgpg fails to parse the keyids of a search because onak returns
40-nibble keyids instead of the more usual 8-nibble keyids.

Kgpg then extracts the 8 *first* nibbles of the long keyid
instead of either leaving the long keyid as such or (less preferable)
to extract the 8 *last* nibbles of the long keyid.

Note that other keyservers could return a 16-nibble keyid as it's also
a valid value for a keyid for gpg.

I guess the best patch is to leave the full keyid as returned
by the keyserver

Example:
onak returns this string:
1024 bit DSA key 440A3A9E56E9D90E99D763A87A135F579AD7E3DB, created:
2002-05-05
while e.g. wwwkeys.pgp.net returns
1024 bit DSA key 9AD7E3DB, created: 2002-05-05

The problem is that kgpg considers in the first case that
the keyid is 440A3A9E instead of 9AD7E3DB

The faulty code is the following:

kservers.cpp line 317:
    QString kid=subkey.section(" key ",1,1);
    kid=kid.stripWhiteSpace();
=>  kid=kid.left(8);
    kitem->setText(3,kid);
    QString creation=subkey.section("created",1,1);

I'm sorry but I don't master qt or c++ so I cannot provide a patch
but in regex we need:
/^([a-zA-Z0-9]{8})+/
or if you really want to get only 8, 16 and 40-nibble keyids
(but which server would return other values??):
/^(([a-zA-Z0-9]{24})?[a-zA-Z0-9]{8})?[a-zA-Z0-9]{8}/

Phil

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.22-3-vserver-686

Debian Release: lenny/sid
  990 testing         ftp.kulnet.kuleuven.ac.be
  500 unstable        ftp.kulnet.kuleuven.ac.be

--- Package information. ---
Depends              (Version) | Installed
==============================-+-===============
kdelibs4c2a     (>= 4:3.5.7-1) | 4:3.5.8.dfsg.1-7
libc6             (>= 2.6.1-1) | 2.7-6
libgcc1           (>= 1:4.2.1) | 1:4.3-20080202-1
libqt3-mt         (>= 3:3.3.7) | 3:3.3.7-9
libstdc++6          (>= 4.2.1) | 4.3-20080202-1
gnupg                          | 1.4.6-2+b1

--- End Message ---
--- Begin Message --- 
The user says the bugs seems fixed in 4.2.2-1, so I am closing this bug.

Regards, Lisandro.
-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: