From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <4158a19ee9e8f2af3ca8c77c1fd842ac@quanstro.net> References: <20090417063313.8DBC95B1B@mail.bitblocks.com> <4158a19ee9e8f2af3ca8c77c1fd842ac@quanstro.net> Date: Fri, 17 Apr 2009 08:14:12 -0400 Message-ID: <9ab217670904170514u621d72bfwc2ddab44c58b80c1@mail.gmail.com> From: "Devon H. O'Dell" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] security questions Topicbox-Message-UUID: e0e950f8-ead4-11e9-9d60-3106f5b1d025 2009/4/17 erik quanstrom : >> What if each user can have a separate IP stack, separate >> (virtualized) interfaces and so on? > > already possible, but you do need 1 physical ethernet > per ip stack if you want to talk to the outside world. I'm sure it wouldn't be hard to add a virtual ``physical'' interface, even though that seems a little bit pervasive, given the already semi-virtual nature due to namespaces. Not sure how much of a hassle it would be to make multiple stacks bindable to a single interface... but perhaps that's the better way to go? >> But you'd have to implement some sort of limits on >> oversubcribing (ratio of virtual to real resources). Unlike >> securitization in the hedge fund world. > > this would add a lot of code and result in the same problem > as today =97 you can be run out of a criticial resource. Oversubscribing is the root of the problem. In fact, even if it was already done, on a terminal server, imagmem is also set to kpages. So if someone found a way to blow up the kernel's draw buffer, boom. I don't know how far reaching that is, as I've never really seen the draw code. Unfortunately, that's what you have to do unless you can afford to invest in more hardware, or have a small userbase. Or find some middle ground -- and maybe that's what the `virtualization' would address. > - erik --dho