From: Eli Zaretskii <eliz@gnu.org>
To: nisse@lysator.liu.se (Niels Möller)
Cc: 15984@debbugs.gnu.org
Subject: bug#15984: 24.3; Problem with combining characters in attachment filename
Date: Thu, 28 Nov 2013 22:25:01 +0200 [thread overview]
Message-ID: <83iovc8eaq.fsf@gnu.org> (raw)
In-Reply-To: <nnob5554o9.fsf@bacon.lysator.liu.se>
> From: nisse@lysator.liu.se (Niels Möller)
> Date: Thu, 28 Nov 2013 09:08:54 +0100
>
> I'm reading email with Gnus. I received an email with an attachment
> containing the headers
>
> Content-Type: application/pdf;
> name="Brev =?UTF-8?B?YWt0aWVhzIhnYXIgMTMxMTI3LnBkZg==?="
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
> filename*0*=UTF-8''%42%72%65%76%20%61%6B%74%69%65%61%CC%88%67%61%72%20%31;
> filename*1*=%33%31%31%32%37%2E%70%64%66
>
> Apparently sent by a Mac user,
>
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
>
> The attachement was displayed in the *Article* buffer as
>
> [2. application/pdf; Brev aktiea?gar 131127.pdf]...
>
> I was running emacs-24.3 in a tty, in a latin-1 locale, on a sparc
> Solaris system. (In a latin-1 tty, emacs ought to display "ä" instead of
> "a?", but that's a less severe and possibly unrelated problem).
If ä was supposed to be produced by character compositions, then Emacs
cannot do that on a TTY, because compositions require drawing one
glyph over the other (with certain offsets).
If you expected Emacs to perform normalization in this case, then I
don't think we do this automatically (or at all).
> When I tried to save the attachment by pressing "o" on that button
> (gnus-mime-save-part), emacs immediately crashed with a segmentation
> violation signal. Since emacs very rarely crashes, I was a bit
> surprised. I just restarted emacs and Gnus and tried again, and it
> crashed again. So at least for me, the problem is reproducible.
Can you send that message as a binary attachment?
> And a crash triggered by untrusted data in a received email is always
> scary. After fixing the bug, exploit possibilities ought to be analyzed.
I suggest to try a recent development trunk, several similar crashes
were fixed a few months ago. If that doesn't help, please reproduce
the problem in a non-optimized non-stripped build, and show the
variables from char_table_ref that are involved in the crash. (I'm
guessing char_table_ref got a bogus character code.)
next prev parent reply other threads:[~2013-11-28 20:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 8:08 bug#15984: 24.3; Problem with combining characters in attachment filename Niels Möller
2013-11-28 20:25 ` Eli Zaretskii [this message]
2013-11-28 22:17 ` Niels Möller
2013-11-28 22:46 ` Niels Möller
2013-11-29 7:16 ` Eli Zaretskii
2013-11-29 8:49 ` Niels Möller
2013-11-29 9:00 ` Eli Zaretskii
2013-11-29 10:43 ` Niels Möller
2013-11-29 11:26 ` Eli Zaretskii
2013-11-29 12:41 ` Niels Möller
2013-11-29 14:50 ` Eli Zaretskii
2013-11-29 16:18 ` Eli Zaretskii
2013-11-30 13:20 ` Eli Zaretskii
2013-11-30 14:25 ` Kenichi Handa
2013-11-30 16:09 ` Eli Zaretskii
2013-11-30 15:50 ` Niels Möller
2013-11-29 15:04 ` Stefan Monnier
2013-11-29 15:27 ` Eli Zaretskii
2013-11-30 8:53 ` Niels Möller
2013-11-29 13:11 ` Kenichi Handa
[not found] ` <87eh574qmm.fsf@gnu.org>
2014-01-17 13:30 ` K. Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83iovc8eaq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15984@debbugs.gnu.org \
--cc=nisse@lysator.liu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.