Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Sep 1997 10:49:05 -0700 (PDT)
From:      Sean Eric Fagan <sef@Kithrup.COM>
To:        brian@firehouse.net
Cc:        security@freebsd.org
Subject:   Re: procfs take II
Message-ID:  <199709061749.KAA25203@kithrup.com>
In-Reply-To: <Pine.NEB.3.96.970906024915.163A-100000.kithrup.freebsd.security@apocalypse.saturn.net>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.NEB.3.96.970906024915.163A-100000.kithrup.freebsd.security@apocalypse.saturn.net> you write:
>Here is a simple patch, it disallows writes to pid 1's mem node if
>securelevel is > 0 (diff is based on 2.2.1 box with the securelevel fix
>applied):

Insufficient -- PTRACE_ATTACH allows the same hole.

Also, the only place that kind of change really needs to go is in
procfs_open(), when the file is originally opened.  If securelevel > 0, then
init should be read-only (or not even readable at all).  A more general way
of doing this should be provided, I think, rather than special-casing pid 1.

Sean.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709061749.KAA25203>