Skip to contentSkip to conversation

another kconfig target for building monolithic kernel (for security) ?

DISCUSSION [email protected] 2 participants 2 messages Apr 30, 2006

lore
Share & tools
lore
#0 lore raw

hello !

"Unfortunately, disabling /dev/mem will break many things, including X and potentially many other user-space programs" (-> http://lwn.net/2001/0419/security.php3 )

"The /dev/mem and /dev/kmem character special files provide access to a pseudo device driver that allows read and write access to system memory or I/O address space. Typically, these special files are used by operating system utilities and commands (such as sar, iostat, and vmstat) to obtain status and statistical information about the system" (ok, this is for AIX, does this apply for linux, too? -> http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/files/aixfiles/mem.htm )

mhhh - while studying this i`m getting unsure if disabling /dev/mem and /dev/kmem is a really good idea - i can live without X on my server, but what else also gets broken? i think i cannot live without important monitoring utilities like vmstat or sar on my server(s).

there is a nice article at LWN at http://lwn.net/Articles/147901/

maybe there is a more comprehensive list of applications which need /dev/{k}mem for proper operation or there is a method to determine this in a reliable way (e.g. by scanning all binaries on mystem somehow) ?

regards
roland

Quoted 35 lines

-----Ursprüngliche Nachricht-----
Von: Nix <[email protected]>
Gesendet: 30.04.06 12:57:49
An: Arjan van de Ven <[email protected]>
CC: [email protected], [email protected]
Betreff: Re: another kconfig target for building monolithic kernel (for security) ?

On 29 Apr 2006, Arjan van de Ven prattled cheerily:

Quoted 9 lines · Dave Jones
Quoted 6 lines · On Sat, Apr 29, 2006 at 03:03:55PM +0200, [email protected] wrote:
Quoted 2 lines

i want to harden a linux system (dedicated root server on the internet) by recompiling the kernel without support for lkm (to prevent installation of lkm based rootkits etc)

Loading modules via /dev/kmem is trivial thanks to a bunch of tutorials and examples on the web, so this alone doesn't make life that much more difficult for attackers.

/dev/kmem should be a config option too though

Yeah, but in practice this should work (somewhat old patch, should still apply):

diff -durN 2.6.14-seal-orig/include/linux/capability.h 2.6.14-seal/include/linux/capability.h

include/linux/capability.h +1 -1
@@ -311,7 +311,7 @@
 
 #define CAP_EMPTY_SET       to_cap_t(0)
 #define CAP_FULL_SET        to_cap_t(~0)
-#define CAP_INIT_EFF_SET    to_cap_t(~0 & ~CAP_TO_MASK(CAP_SETPCAP))
+#define CAP_INIT_EFF_SET    to_cap_t(~0 & ~CAP_TO_MASK(CAP_SETPCAP) & ~CAP_TO_MASK(CAP_SYS_RAWIO))
 #define CAP_INIT_INH_SET    to_cap_t(0)
 
 #define CAP_TO_MASK(x) (1 << (x))
Quoted 8 lines
Quoted 1 line

(and /dev/mem should get the filter patch that fedora has ;-)

Agreed.

Signature · 3 lines
`On a scale of 1-10, X's "brokenness rating" is 1.1, but that's only
 because bringing Windows into the picture rescaled "brokenness" by
 a factor of 10.' --- Peter da Silva

_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

#1 lore raw
Quoted 4 lines · On Sun, 2006-04-30 at 14:31 +0200, [email protected] wrote:

hello !

"Unfortunately, disabling /dev/mem will break many things, including X and potentially many other user-space programs" (-> http://lwn.net/2001/0419/security.php3 )

not if you do it carefully like we did for Fedora...

Quoted 2 lines

"The /dev/mem and /dev/kmem character special files provide access to a pseudo device driver that allows read and write access to system memory or I/O address space. Typically, these special files are used by operating system utilities and commands (such as sar, iostat, and vmstat) to obtain status and statistical information about the system" (ok, this is for AIX, does this apply for linux, too? -> http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/files/aixfiles/mem.htm )

/dev/kmem isn't used by much of anything except debugging, so having that a config option is reasonable. for /dev/mem it's enough to disable all access to 'what the kernel sees as RAM' with the lower 1Mb as exception..