From: Colin Walters <walters@debian.org>
Subject: Re: many packages write to `temporary-file-directory' insecurely
Date: 05 Apr 2002 02:30:36 -0500 [thread overview]
Message-ID: <1017991836.27236.40.camel@space-ghost> (raw)
In-Reply-To: <200203310124.g2V1Ot110614@aztec.santafe.edu>
On Sat, 2002-03-30 at 20:24, Richard Stallman wrote:
> My concern is that since Emacs is often used on large, multiuser
> systems, many of which use disk quotas, a setgid program without any
> limits on the files it creates would be a way for users to get around
> their disk quotas.
>
> One solution for that is to limit the format of the data
> that goes in the file so as to specialize it for game scores.
Well, I guess what bugs me about this is presumably people will want to
have at least their names and/or email addresses in there, and I don't
see how to restrict the "format" of the data such that its total size is
limited.
On the other hand, I've realized it's a good idea to put the actual
username (or at least the uid) into the score lines, so if someone is
using it to store a substantial amount of data, then it will be
blatantly obvious who is doing it.
By the way, I'm almost done with the autoconf magic necessary to support
this; it's been a bit more painful than I thought.
next prev parent reply other threads:[~2002-04-05 7:30 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
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 [this message]
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=1017991836.27236.40.camel@space-ghost \
--to=walters@debian.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).