From: Colin Walters <walters@debian.org>
Subject: Re: many packages write to `temporary-file-directory' insecurely
Date: 17 Mar 2002 17:08:01 -0500 [thread overview]
Message-ID: <1016402881.5455.24.camel@space-ghost> (raw)
In-Reply-To: <200203110901.g2B91Ej04386@wijiji.santafe.edu>
On Mon, 2002-03-11 at 04:01, Richard Stallman wrote:
> > One way to solve this problem is by having Emacs installation create
> > the desired files under /var/games/emacs, make them world-writable,
> > and make /var/games/emacs read-only.
>
> The problem I see with this is that we can't use `rename-file', and thus
> we lose atomicity of score file updates. If multiple users are
> concurrently reading and writing the same file, it will eventually be
> corrupted.
>
> You are right.
>
> How do other game programs handle this?
Well, from a selection of the games I looked at in the Debian "games"
section, none of them seem to make any attempt to handle it at all. In
the "xjewel" source, in "hscore.c", there are empty methods like:
void File_Lock()
{
}
void File_Unlock()
{
}
...which apparently the author was going to fill in later. The
"conquest" game mmap()s the score file, which has the same problems.
And the "lbreakout2" game just uses read and write.
Really, I can't see a way to solve this without using some locking
mechanism. But that has its own problems, e.g. what to do if a
malicious user locks the file and never unlocks it?
My gut feeling is that it really would be best to go with
~/.emacs.d/games or so.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-17 22:08 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 [this message]
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=1016402881.5455.24.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).