From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: vhost-net todo list Date: Thu, 17 Sep 2009 14:14:06 +0200 Message-ID: <200909171414.06527.arnd@arndb.de> References: <20090916100438.GA30036@redhat.com> <200909171330.01414.arnd@arndb.de> <20090917114739.GD18916@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: anthony@codemonkey.ws, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, Rusty Russell To: "Michael S. Tsirkin" Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:59633 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751500AbZIQMOW (ORCPT ); Thu, 17 Sep 2009 08:14:22 -0400 In-Reply-To: <20090917114739.GD18916@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thursday 17 September 2009, Michael S. Tsirkin wrote: > On Thu, Sep 17, 2009 at 01:30:00PM +0200, Arnd Bergmann wrote: > > On Wednesday 16 September 2009, Michael S. Tsirkin wrote: > > > > Also, I might not want to allow the user to open a > > > > random random raw socket, but only one on a specific downstream > > > > port of a macvlan interface, so I can filter out the data from > > > > that respective MAC address in an external switch. > > > > > > I agree. Maybe we can fix that for raw sockets, want me to > > > add it to the list? :) > > > > So far, I could not find any theoretical solution how to fix this, > > What if socket had a LOCKBIND ioctl after which you can not bind it to > any other device? Then someone with RAW capability can open the socket, > bind to device and hand it to you. You can send packets but not > switch to another device. Could work, though I was hoping for a solution that does not depend on a priviledged task at run time to open the socket, as you have with persistant tap devices or chardevs like macvtap that can have their persissions set by udev. Arnd <><