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

Bug#188295: marked as done (kmail: display of gpg key userid borken for unicode userids)

Your message dated Thu, 11 May 2006 17:12:50 +0200
with message-id <20060511151250.GA29917@mad.intersec.fr>
and subject line kmail: display of gpg key userid borken for unicode userids
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kmail
Version: 4:3.1.1-1
Severity: minor

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I got a mail from Yenot (gpg key id 0x8DBD2310), and the userid is
displayed fine (except for a konsole bug) in the terminal, but comes as
garbage in kmails signature verification status display.

Dunno how 'reportbug' and bugs.debian.org handles unicode, but it looks
fine when I send this:

	userid of the key: СекÑ?еÑ?нÑ?й Ð?ноÑ? <yenot@sec.to>
	string in kmail: �¡�µ�º�\x8�µ�\x8�½�\x8�¹ �\x9�½�¾�\x8

(But I believe you can test this easily yourself).

The bug is not security relevant, as the keyid of the key is still
properly displayed.

cheers
- -- vbi

- -- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux altfrangg 2.4.19 #1 SMP Wed Sep 25 19:59:59 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8

Versions of packages kmail depends on:
ii  kdebase-kio-plugins        4:3.1.1-1     KDE I/O Slaves
ii  kdelibs4                   4:3.1.1-1     KDE core libraries
ii  libart-2.0-2               2.3.11-3      Library of functions for 2D graphi
ii  libc6                      2.3.1-16      GNU C Library: Shared libraries an
ii  libfam0c102                2.6.9-4       client library to control the FAM 
ii  libgcc1                    1:3.2.3-0pre6 GCC support library
ii  libjpeg62                  6b-7          The Independent JPEG Group's JPEG 
ii  libkdenetwork2             4:3.1.1-1     KDE Network (common libraries)
ii  libmimelib1                4:3.1.1-1     KDE network mime library
ii  libpng12-0                 1.2.5-10      PNG library - runtime
ii  libqt3c102-mt              3:3.1.1-7     Qt GUI Library (Threaded runtime v
ii  libstdc++5                 1:3.2.3-0pre6 The GNU Standard C++ Library v3
ii  xlibs                      4.2.1-3       X Window System client libraries
ii  zlib1g                     1:1.1.4-11    compression library - runtime

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: get my key from http://fortytwo.ch/gpg/92082481

iKcEARECAGcFAj6TwopgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjMmbWQ1c3VtPTE0Y2E2MTZmMTQ2ODJhODJj
YjljYzI1YzliMzRhMTBkAAoJEIukMYvlp/fWlnQAoJNuRztuKkc7/PjiWYWF/a5m
KXEOAJ9eTBlfBbrJxZGESU8z6TfUhSYOrQ==
=TZMx
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 4:3.5.0

On Wed, Apr 09, 2003 at 08:49:46AM +0200, vbi@fortytwo.ch wrote:
> Package: kmail
> Version: 4:3.1.1-1
> Severity: minor
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> I got a mail from Yenot (gpg key id 0x8DBD2310), and the userid is
> displayed fine (except for a konsole bug) in the terminal, but comes as
> garbage in kmails signature verification status display.
> 
> Dunno how 'reportbug' and bugs.debian.org handles unicode, but it looks
> fine when I send this:
> 
> 	userid of the key: Секретный Енот <yenot@sec.to>
> 	string in kmail: СекÑ\x8еÑ\x8нÑ\x8й Ð\x9ноÑ\x8
> 
> (But I believe you can test this easily yourself).
> 
> The bug is not security relevant, as the keyid of the key is still
> properly displayed.

  as of version 3.5 (at least) only email address is shown, which is
ascii-only.

  hence I consider it fixed now.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: