From: grossjohann@amaunet.cs.uni-dortmund.de
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: pgnus-0.33: multipart/mixed: usage of filename?
Date: 02 Oct 1998 12:48:53 +0200 [thread overview]
Message-ID: <861zor6xyi.fsf@slowfox.do.uunet.de> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Thu, 1 Oct 1998 14:33:17 -0400"
>>>>> Excerpts from mail: (01-Oct-98) Re: pgnus-0.33: multipart/mixed: usage of filename? by Lars Magne Ingebrigtsen
Lars> Doing so would make sense, but if the file name characters are
Lars> properly translated and quoted, wouldn't it be nice to have
Lars> the full real names of the files available in the external
Lars> viewer?
>>>>> On Thu, 1 Oct 1998, Edward J Sabol said:
EJS> I would much rather have the real file name!
Well, rather than saving /etc/passwd in /tmp/emmXYZZY/passwd, saving
/etc/passwd in /tmp/emmXYZZY/%etc%passwd would also be a possibility.
Which is what Lars is suggesting, I think. There's no security risk
and you get the absolute pathname information.
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next prev parent reply other threads:[~1998-10-02 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-25 9:29 Kai Grossjohann
1998-09-25 9:31 ` Kai Grossjohann
1998-09-28 9:14 ` Robert Bihlmeyer
1998-09-29 10:40 ` Lars Magne Ingebrigtsen
1998-09-29 12:59 ` Jan Vroonhof
1998-10-01 2:40 ` Lars Magne Ingebrigtsen
1998-10-01 9:02 ` Jan Vroonhof
1998-10-01 14:18 ` Lars Magne Ingebrigtsen
1998-10-01 18:33 ` Edward J. Sabol
1998-10-02 2:47 ` Lars Magne Ingebrigtsen
1998-10-02 10:48 ` grossjohann [this message]
1998-10-02 12:29 ` Simon Josefsson
1998-10-10 21:45 ` Lars Magne Ingebrigtsen
1998-10-02 9:01 ` Jan Vroonhof
1998-10-10 21:41 ` Lars Magne Ingebrigtsen
1998-10-10 23:28 ` Kai Grossjohann
1998-10-11 0:17 ` Lars Magne Ingebrigtsen
1998-10-12 9:52 ` Jan Vroonhof
1998-10-12 13:10 ` 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=861zor6xyi.fsf@slowfox.do.uunet.de \
--to=grossjohann@amaunet.cs.uni-dortmund.de \
--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).