[Vserver] Commercial virtual server sofware

2004-01-08 Thread Gregory (Grisha) Trubetskoy
Sorry, this is a bit off-topic: I've seen quite a few mentions of Virtuozzo and Ensim VPS solutions. Virtuozzo seems to be particularly keen on how they are so super advanced, no open source thing comes even close. Anyone here have any experience with those and can give the skinny on what those

[Vserver] freevps extends linux-vserver functionality...

2004-01-08 Thread Joey Esquibal
Had anyone tried to use freevps? FreeVPS extends the original Linux VServer. You might want to try http://www.freevps.com Cheers! Joey Esquibal ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Vserver and Security

2004-01-08 Thread Enrico Scholz
[EMAIL PROTECTED] ("Gregory (Grisha) Trubetskoy") writes: >> it 'seems' that the poster was worried about the >> ability to sniff network packets from other vservers >> on the same host, when inside a vserver. > > Could he have been referring to CAP_NET_RAW? Regarding tasks which are requiring CA

Re: [Vserver] Vserver and Security

2004-01-08 Thread Simon Garner
On Friday, January 09, 2004 12:37 PM NZT, Herbert Poetzl <[EMAIL PROTECTED]> wrote: > > some tools (traceroute or tracepath) make use of udp > instead of icmp, which is no big deal in a vserver, > only ping 'requires' the insecure icmp/raw access ... > I was thinking that, but traceroute doesn't

Re: [Vserver] Vserver and Security

2004-01-08 Thread Herbert Poetzl
On Thu, Jan 08, 2004 at 06:24:49PM -0500, Gregory (Grisha) Trubetskoy wrote: > > > On Thu, 8 Jan 2004, Herbert Poetzl wrote: > > > recently (end of december last year) somebody posted > > a mystic message to one of the german webhosting lists > > stating, that vserver is insecure, and that he wo

Re: [Vserver] Vserver and Security

2004-01-08 Thread Gregory (Grisha) Trubetskoy
On Thu, 8 Jan 2004, Herbert Poetzl wrote: > recently (end of december last year) somebody posted > a mystic message to one of the german webhosting lists > stating, that vserver is insecure, and that he would > suggest not to use it (no details where given) ... > > it 'seems' that the poster was

Re: [Vserver] Demo...

2004-01-08 Thread Bodo Eggert
On Thu, 8 Jan 2004, Dariush Pietrzak wrote: > On Wed, 7 Jan 2004, Bodo Eggert wrote: [X outside vserver was considered to be insecure, I told X is insecure anyway] > Hmm, this is supposed to be a 'demo', not a public kiosk. ACK, therefore there is no need to jail the X-Server itself. So if it d

[Vserver] vserver

2004-01-08 Thread info2004
InfoQOFCNRKTKVSEOSFN <>

[Vserver] [Advisory] procfs in vserver

2004-01-08 Thread Herbert Poetzl
Dear Vserver Community! we discovered that there is a security issue in all vserver versions, which will be solved soon, but for now it would be best to mount the procfs read only on your vserver host. this can be done with: mount -o remount,ro /proc if access to the procfs is required on the

Kernel capabilties (Was: [Vserver] Vserver and Security)

2004-01-08 Thread Frank Matthieß
Thanks for this short abstact Herbert. [...] > CAP_SYS_ADMIN > this list would be too long, it basically > alows to do everything else, not mentioned > in another capability. [...] For all who are not aware of it: The full story ist readable in /include/linux/capability.h. Fra

Re: [Vserver] Multiple NICs and the v_*'s

2004-01-08 Thread Roderick A. Anderson
On Thu, 8 Jan 2004, Herbert Poetzl wrote: > as Cathy says, this is an option, but if you do so, > make sure not to use the v_sshd wrapper at all ... And since I've been "getting a 'vserver' clue" I'm getting closer and closer to not using the v_* stuff at all. An early setup on a long functionin

[Vserver] Vserver and Security

2004-01-08 Thread Herbert Poetzl
Hi Community! recently (end of december last year) somebody posted a mystic message to one of the german webhosting lists stating, that vserver is insecure, and that he would suggest not to use it (no details where given) ... it 'seems' that the poster was worried about the ability to sniff net

Re: [Vserver] 1.3.1: save_s_context: fork: Resource temporarily unavailable [was: Re: 1.3.1 with quota/limit patches]

2004-01-08 Thread Herbert Poetzl
On Thu, Jan 08, 2004 at 08:36:19PM +1100, Alec Thomas wrote: > Hi, > > I am seeing this same behaviour with 2.4.24-vs1.3.4: > > [EMAIL PROTECTED]:~]vserver swapoff enter > -su: fork: Resource temporarily unavailable > -su-2.05b# > > The same config worked fine with vs1.22. yes, I can confirm th

Re: [Vserver] [Release] vs1.00, vs1.22 and vs1.3.3 for 2.4.24

2004-01-08 Thread Alexander Goeres
Hi Chistian! Thanks a lot, merci beaucoup, vielen Dank, mange tak!! It really works! Looks as if it's nessesary to read the kernel-source-docs even if one never intends to become a kernel hacker.. So bashing foreign admins is no longer needed, what a relief..:-) Greetings Alexander Am Mittwoch,

Re: [Vserver] 1.3.1: save_s_context: fork: Resource temporarily unavailable [was: Re: 1.3.1 with quota/limit patches]

2004-01-08 Thread Alec Thomas
Hi, I am seeing this same behaviour with 2.4.24-vs1.3.4: [EMAIL PROTECTED]:~]vserver swapoff enter -su: fork: Resource temporarily unavailable -su-2.05b# The same config worked fine with vs1.22. Regards, Alec > supported in 1.3.x. So I didn't tested it extensive. > A vanilla 2.4.23 with patch-

Re: [Vserver] Demo...

2004-01-08 Thread Dariush Pietrzak
On Wed, 7 Jan 2004, Bodo Eggert wrote: > X needs too much privileges to be any good on a secure machine. You might > reduce some risks, but I doubt you can get something you may actually > call "secure". Instead, you should run a P90 as X-Server and connect > using ethernet. Hmm, this is supposed