David Malone wrote:
On Sun, May 28, 2006 at 03:46:06PM +0200, Anatoli Klassen wrote:
if security.bsd.see_other_uids is set to 0, users from the main system
can still see processes from jails if they have (by accident) the save uid.
For me it's wrong behavior because the main system
Hi All,
if security.bsd.see_other_uids is set to 0, users from the main system
can still see processes from jails if they have (by accident) the save uid.
For me it's wrong behavior because the main system and the jail are two
different systems where uids are independent.
Could somebody
[EMAIL PROTECTED] wrote:
On Sun, May 28, 2006 at 03:46:06PM +0200, Anatoli Klassen wrote:
Hi All,
if security.bsd.see_other_uids is set to 0, users from the main system
can still see processes from jails if they have (by accident) the save uid.
For me it's wrong behavior because the main
Hanspeter Roth wrote:
Fdisk shows sysid 165 (0xa5) for partition 3. This is where FreeBSD
is installed. And Fdisk shows sysid 169 (0xa9) for partition 4. This
is where NetBSD is installed.
In /dev there are ad0s3 and ad0s3[a-g] but there is only a ad0s4.
So how can filesystems of my NetBSD in
Hi All,
I have written patches to allow to run ntpd as ordinal user and/or from
jail.
The idea is to disable build-in kernel security checks by setting some
sysctl's and then plug in a MAC module (actually it is the same approach
as in mac_portacl to bind to low ports).
There are four new
5 matches
Mail list logo
