On Fri, Jun 27, 2003 at 06:41:05AM +0300, Alex Lyashkov wrote: > On Thursday 26 June 2003 17:29, Herbert Poetzl wrote: > > On Tue, Jun 24, 2003 at 09:56:58PM +0300, Alex Lyashkov wrote: > > > On Tuesday 24 June 2003 21:17, Chris Murton wrote: > > > > vserver-1:/# hostname host-28 > > > > hostname: you must be root to change the host name > > > > vserver-1:/# whoami > > > > root > > > > > > > > Any thoughts? ;) > > > > > > Any original vserver have this bug. > > > I fix it in snapshot rh-vserver-1052304359.diff.gz (7 may). > > > > hrm, this is _not_ a bug ... > > > > you change the hostname by specifying S_HOSTNAME=<name> > > in the /etc/vservers/<name>.conf file ... > > > I think bug. set hostname/domain name have not security > compromising, but more correctly work.
I do not agreer. The hostname should not be modified from inside a virtual server ... IMHO this is a name given from the physical admin to identify the virtual server ... but I guess this isn't really a security issue, or am I wrong? > I think after move context process limits from task > limits struct to context struct can add CAP_SYS_RESOURCE > in vserver config file, and disable use it only for > file systems. hmm, and what about ... - Allow more than 64hz interrupts from the real-time clock - Override max number of consoles on console allocation - Override max number of keymaps best, Herbert > -- > With best regards, > Alex
