From: Andreas Schwab <schwab@suse.de>
Cc: monnier+gnu/emacs@RUM.cs.yale.edu, Pavel@Janik.cz,
walters@verbum.org, emacs-devel@gnu.org
Subject: Re: many packages write to `temporary-file-directory' insecurely
Date: Tue, 05 Mar 2002 11:20:00 +0100 [thread overview]
Message-ID: <jebse3gvu7.fsf@sykes.suse.de> (raw)
In-Reply-To: <200203042340.g24NexL00497@aztec.santafe.edu> (Richard Stallman's message of "Mon, 4 Mar 2002 16:40:59 -0700 (MST)")
Richard Stallman <rms@gnu.org> writes:
|> If /var/games is treated just like /tmp, meaning anyone can create a
|> file in it, then it will raise the same security issues as /tmp. We
|> could perhaps use the code that Al Petrovsky sent, if that is correct.
The convention for /var/games is that it is writable for a special group
(game) only, and any program wanting to have access to it must be setgid
game.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-05 10:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 1:15 many packages write to `temporary-file-directory' insecurely Colin Walters
2002-03-02 11:52 ` Pavel Janík
2002-03-02 21:12 ` Colin Walters
2002-03-02 23:13 ` Pavel Janík
2002-03-03 17:18 ` Stefan Monnier
2002-03-03 20:36 ` Al Petrofsky
2002-03-04 0:07 ` Stefan Monnier
2002-03-04 23:41 ` Richard Stallman
2002-03-05 2:26 ` Al Petrofsky
2002-03-05 15:15 ` Stefan Monnier
2002-03-05 19:57 ` Al Petrofsky
2002-03-05 21:58 ` Richard Stallman
2002-03-04 23:40 ` Richard Stallman
2002-03-05 4:30 ` Colin Walters
2002-03-05 10:20 ` Andreas Schwab [this message]
2002-03-05 15:20 ` Stefan Monnier
2002-03-05 19:07 ` Richard Stallman
2002-03-06 4:40 ` Colin Walters
2002-03-06 7:35 ` Colin Walters
2002-03-06 16:59 ` Stefan Monnier
2002-03-07 2:40 ` Colin Walters
2002-03-07 6:00 ` Eli Zaretskii
2002-03-08 9:08 ` Richard Stallman
2002-03-08 9:08 ` Richard Stallman
2002-03-10 10:46 ` Colin Walters
2002-03-11 9:01 ` Richard Stallman
2002-03-17 22:08 ` Colin Walters
2002-03-18 20:06 ` Richard Stallman
2002-03-18 22:36 ` Colin Walters
2002-03-18 23:49 ` Steve Kemp
2002-03-19 0:31 ` Colin Walters
2002-03-19 6:22 ` Pavel Janík
2002-03-20 5:10 ` Richard Stallman
2002-03-27 23:46 ` Colin Walters
2002-03-31 1:24 ` Richard Stallman
2002-04-05 7:30 ` Colin Walters
2002-04-05 23:41 ` Richard Stallman
2002-03-06 16:59 ` Stefan Monnier
2002-03-06 19:05 ` Colin Walters
2002-03-08 9:07 ` Richard Stallman
2002-03-08 18:52 ` Colin Walters
2002-03-09 10:49 ` Richard Stallman
2002-03-03 14:39 ` Richard Stallman
2002-03-04 4:08 ` Richard Stallman
2002-03-04 4:08 ` Richard Stallman
2002-03-04 4:50 ` Colin Walters
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jebse3gvu7.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Pavel@Janik.cz \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@RUM.cs.yale.edu \
--cc=walters@verbum.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).