From: Erik Andersen <andersen@codepoet.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Andrew Morton <akpm@osdl.org>,
Neale Banks <neale@lowendale.com.au>,
paul@clubi.ie, linux-kernel@vger.kernel.org
Subject: Re: chmod of active swap file blocks
Date: Thu, 1 Jan 2004 14:40:51 -0700 [thread overview]
Message-ID: <20040101214051.GA19390@codepoet.org> (raw)
In-Reply-To: <20040101151027.A2411@pclin040.win.tue.nl>
On Thu Jan 01, 2004 at 03:10:27PM +0100, Andries Brouwer wrote:
> On Thu, Jan 01, 2004 at 02:12:41AM -0800, Andrew Morton wrote:
> > Neale Banks <neale@lowendale.com.au> wrote:
> > >
> > > How much of the original problem goes away if swapon(8) were to refuse to
> > > activate a file/device which has ownership/mode which it doesn't like?
> >
> > I think swapon(8) should at least warn when the swapfile has inappropriate
> > permissions. It's an obvious and outright security hole.
>
> swapon had this warning for a while, but that generated lots of complaints.
> Now this message is printed only when the -v (verbose) flag is given.
Perhaps swapon should automagically do a chmod and chown on all
swapfiles, unless specifically asked to be wildly insecure
(perhaps with a -W option -- wildly insecure swapfile permissions
are considered acceptable)....
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2004-01-01 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 4:55 chmod of active swap file blocks Paul Jakma
2003-12-29 5:16 ` Paul Jakma
2003-12-29 9:30 ` Andrew Morton
2003-12-29 17:25 ` Paul Jakma
2004-01-01 8:19 ` Neale Banks
2004-01-01 10:12 ` Andrew Morton
2004-01-01 14:10 ` Andries Brouwer
2004-01-01 21:40 ` Erik Andersen [this message]
2004-01-02 0:43 ` Paul Jakma
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=20040101214051.GA19390@codepoet.org \
--to=andersen@codepoet.org \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neale@lowendale.com.au \
--cc=paul@clubi.ie \
/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