From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Saving attachments with a leading dot
Date: Wed, 24 Sep 2003 10:40:54 -0400 [thread overview]
Message-ID: <4n1xu6ckqx.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m31xu6jnrh.fsf@seneca.benny.turtle-trading.net> (Benjamin Riefenstahl's message of "Wed, 24 Sep 2003 15:53:54 +0200")
On Wed, 24 Sep 2003, Benjamin.Riefenstahl@epost.de wrote:
> Jesper Harder <harder@myrealbox.com> writes:
>> Any other nasty file names we should watch out for?
>
> Control characters in names. Especially \n could possibly be used
> for exploits.
Could that occur naturally in UTF-8 filenames? Does Gnus support
those? I have no idea if MIME supports them to begin with.
Ted
next prev parent reply other threads:[~2003-09-24 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 23:39 Jesper Harder
2003-09-24 10:38 ` Ted Zlatanov
2003-09-25 3:24 ` Jesper Harder
2003-09-25 4:22 ` Ted Zlatanov
2003-09-25 5:49 ` Jochen Küpper
2003-09-29 3:28 ` Jesper Harder
2003-10-02 18:07 ` Ted Zlatanov
2003-10-02 19:56 ` Jochen Küpper
2003-10-03 1:35 ` Jesper Harder
2003-10-03 14:04 ` Benjamin Riefenstahl
2003-10-02 18:10 ` Ted Zlatanov
2003-09-24 13:53 ` Benjamin Riefenstahl
2003-09-24 14:40 ` Ted Zlatanov [this message]
2003-09-24 15:11 ` Benjamin Riefenstahl
2003-09-24 16:03 ` Ted Zlatanov
2003-09-24 16:16 ` Benjamin Riefenstahl
2003-09-24 17:45 ` Ted Zlatanov
2003-09-24 15:48 ` Reiner Steib
2003-09-24 16:11 ` Benjamin Riefenstahl
2003-09-25 14:40 ` Reiner Steib
2003-09-25 3:23 ` Jesper Harder
2003-09-25 8:44 ` Hanak David
2003-09-29 3:20 ` Jesper Harder
2003-10-17 17:31 ` Lars Magne Ingebrigtsen
2003-10-18 16:43 ` Jesper Harder
2003-10-18 16:50 ` Lars Magne Ingebrigtsen
2003-10-18 20:04 ` Jesper Harder
2003-10-18 23:17 ` Jesper Harder
2003-10-19 11:14 ` Lars Magne Ingebrigtsen
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=4n1xu6ckqx.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).