linux-kernel - Re: [TOMOYO #7 30/30] Hooks for SAKURA and TOMOYO.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804172058.BHI60408.OtFFMOJHOLQVSF@I-love.SAKURA.ne.jp>
Date:	Thu, 17 Apr 2008 20:58:12 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	pavel@....cz
Cc:	casey@...aufler-ca.com, sds@...ho.nsa.gov,
	crispin@...spincowan.com, serue@...ibm.com, matthew@....cx,
	paul.moore@...com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, takedakn@...data.co.jp,
	linux-fsdevel@...r.kernel.org
Subject: Re: [TOMOYO #7 30/30] Hooks for SAKURA and TOMOYO.


Pavel Machek wrote:
> > It is true that namespace may differ between processes,
> > but I think that that is the matter of how to restrict namespace manipulation operations.
> > As I said, a system can't survive if namespace is madly manipulated.
> > To keep the system workable, /bin/ must be the directory for binary programs,
> > /etc/ must be the directory for configuration files, and so on in all namespaces.
> 
> Ehm? Where did you get those ideas?
> 
> I'm free to name my directories any way I want, and keep config files
> in /pavlix_config, thank you... There is even distro that does
> something like that, IIRC...
> 
We can make processes have different namespace by using clone() with CLONE_NEWNS.
But even if some process got a different namespace, it need to follow conventional rules.
Optional files (e.g. /pavlix_config) need not to follow conventional rules.
What I'm talking about is essetial files (e.g. /bin/sh and /etc/passwd).
Can your system continue running even if essetial files are not in place
(like /bin/sh moved to /etc/sh and /etc/passwd moved to /bin/passwd) ?
I don't think so...

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/