netdev - Re: AF_VSOCK and the LSMs

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: <888679886.3769933.1361573683299.JavaMail.root@vmware.com>
Date:	Fri, 22 Feb 2013 14:54:43 -0800 (PST)
From:	Andy King <acking@...are.com>
To:	Paul Moore <pmoore@...hat.com>
Cc:	netdev@...r.kernel.org, linux-security-module@...r.kernel.org,
	selinux@...ho.nsa.gov, Gerd Hoffmann <kraxel@...hat.com>,
	Eric Paris <eparis@...hat.com>
Subject: Re: AF_VSOCK and the LSMs

Hi Paul,

> to see if anyone had any strong feelings on this approach (either good or
> bad).  Here is what I am proposing, and currently working on ...
> 
> * Add a LSM secid/blob to the vmci_datagram struct

I think perhaps this is the wrong layer at which to embed this.  Think
of that structure as an ethernet header, with VMCI being ethernet; it's
what the device (and the hypervisor and peer) understand.  So this
really cannot be changed.

It's also not entirely clear to me how this will work in a heterogeneous
environments.  What if there's a Linux guest running on a Windows host,
or vice-versa?

I'll take a closer read at the rest of your mail, but I think we need to
address the above first.

Thanks!
- Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html