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

Bug#234535: marked as done (xserver-xfree86: X server can be crashed by xfstt font server (DoS attack))



Your message dated Thu, 01 Feb 2007 21:49:38 +0100
with message-id <45C25262.90908@ens-lyon.org>
and subject line Bug#234535: xserver-xfree86: X server can be crashed by xfstt font server (DoS attack)
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: xserver-xfree86
Version: 4.2.1-12.1
Severity: important

I've tried to use UTF-8 recently. If I run localeconf,
then utf-8 locales are the only ones available.

But having LANG=no_NO.UTF-8 makes X crash when I run gimp
and quite a few other apps too.

It doen't matter what locale the xserver runs under, it
is the locale setting for gimp that cause the crash.
So "export LANG=no_NO.UTF-8 ; gimp" will kill X,
no matter wheter the X server runs with LANG=no_NO or
LANG=no_NO.UTF-8.

My only guess is that gimp tries to render some odd strings/characters when using UTF-8. This shouldn't
kill the x server though.  I first saw this with the
experimental xserver-xfree86-dri-trunk, but the same happens with the standard xserver in "testing".

This happens with several different hw drivers,
both radeon, matrox, and unaccelerated framebuffer.


I have also reported this bug against "locales", because
I don't know wheter it is a "locales" bug or a
"xserver-xfree86" bug.

I'm running both xfs and xfstt.

I used important severity because the effect is quite bad,
still the package isn't completely unuseable.  "rxvt"
seems to work fine without taking down X.

The easy workaround is to use LANG=no_NO  (without
the UTF-8 part) Nothing crashes in that case, but I'd like
to use UTF-8

I can do some further testing (if directed), and also provide an account
for further investigation.

Helge Hafting




--- End Message ---
--- Begin Message ---
Closing since the submitter did not see any problem recently.

Brice


--- End Message ---

Reply to: