public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Chris Wright <chrisw@osdl.org>
Cc: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Filesystem linking protections
Date: Mon, 07 Feb 2005 21:10:15 -0500	[thread overview]
Message-ID: <42081F87.4040707@comcast.net> (raw)
In-Reply-To: <20050207144734.C469@build.pdx.osdl.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Chris Wright wrote:
> * John Richard Moser (nigelenki@comcast.net) wrote:
> 
>>Yes, mkdtemp() and mkstemp().
>>
>>Of course we can't always rely on programmers to get it right, so the
>>idea here is to make sure we ask broken code to behave nicely, and stab
>>it in the face if it doesn't.  Please try to examine this in that scope.
> 
> 
> It's fine for hardened distro.  But still inappropriate for mainline.
> 

Perhaps in mainline as an option?  The [*] notations next to things are
really nice, they let you turn kernel stuff on and off :)  It's
appropriate for mainline to support added security isn't it?  I think
following the path of supporting-but-not-forcing is the best route,
because it encourages people to account for systems which may take
advantage of such options, and thus leads to a software base in which
it's quite sane to actually enable those options globally.

That's just how I think though.

> thanks,
> -chris

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCCB+GhDd4aOud5P8RAlD9AJ45JTY20WY6qHe0h0ZIcFasgxJDtACbB1aB
i4hytMAy6Cs1AUNXC296JOk=
=oLVs
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-02-08  2:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 18:57 [PATCH] Filesystem linking protections Lorenzo Hernández García-Hierro
2005-02-07 19:12 ` Chris Wright
2005-02-07 19:40   ` Lorenzo Hernández García-Hierro
2005-02-07 20:00     ` Chris Wright
2005-02-07 19:43   ` John Richard Moser
2005-02-07 20:05     ` Chris Wright
2005-02-07 22:29       ` John Richard Moser
2005-02-07 22:47         ` Chris Wright
2005-02-08  2:10           ` John Richard Moser [this message]
2005-02-07 19:14 ` Valdis.Kletnieks
2005-02-07 19:34   ` Lorenzo Hernández García-Hierro
2005-02-07 21:45     ` Valdis.Kletnieks
2005-02-07 22:00       ` Lorenzo Hernández García-Hierro
2005-02-07 22:13         ` Valdis.Kletnieks

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=42081F87.4040707@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@gnu.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