linux-kernel - Re: [RFC] Unify KVM kernel-space and user-space code into a single project

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: <4BAA3EB3.2070101@redhat.com>
Date:	Wed, 24 Mar 2010 18:32:51 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joro@...tes.org>
CC:	"Daniel P. Berrange" <berrange@...hat.com>,
	Anthony Liguori <anthony@...emonkey.ws>,
	Ingo Molnar <mingo@...e.hu>,
	Pekka Enberg <penberg@...helsinki.fi>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Sheng Yang <sheng@...ux.intel.com>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Jes Sorensen <Jes.Sorensen@...hat.com>,
	Gleb Natapov <gleb@...hat.com>, ziteng.huang@...el.com,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Fr?d?ric Weisbecker <fweisbec@...il.com>,
	Gregory Haskins <ghaskins@...ell.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
 project

On 03/24/2010 06:31 PM, Joerg Roedel wrote:
> On Wed, Mar 24, 2010 at 06:20:38PM +0200, Avi Kivity wrote:
>    
>> On 03/24/2010 06:17 PM, Joerg Roedel wrote:
>>      
>>> But is this not only one entity more for
>>> sVirt to handle? I would leave that decision to the sVirt developers.
>>> Does attaching the same label as for the VM resources mean that root
>>> could not access it anymore?
>>>
>>>        
>> IIUC processes run under a context, and there's a policy somewhere that
>> tells you which context can access which label (and with what
>> permissions).  There was a server on the Internet once that gave you
>> root access and invited you to attack it.  No idea if anyone succeeded
>> or not (I got bored after about a minute).
>>
>> So it depends on the policy.  If you attach the same label, that means
>> all files with the same label have the same access permissions.  I think.
>>      
> So if this is true we can introduce a 'trace' label and add all contexts
> that should be allowed to trace to it.
> But we probably should leave the details to the security experts ;-)
>    

That's just what I want to do.  Leave it in userspace and then they can 
deal with it without telling us about it.

-- 
error compiling committee.c: too many arguments to function

--
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/