Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Feb 2006 11:14:14 -0800 (PST)
From:      Jon Dama <jd@ugcs.caltech.edu>
To:        Ivan Kolosovskiy <agava-develop@yandex.ru>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: sharedmem in jail.
Message-ID:  <Pine.LNX.4.53.0602271111470.12692@barf.ugcs.caltech.edu>
In-Reply-To: <4402C964.4090904@yandex.ru>
References:  <4402C731.3030306@yandex.ru> <4402C964.4090904@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
There was some discussion about improving this situation a bit; i.e., by
permitting an option wherein sysvipc could be per jail.

Did this ever come to fruition?

Ivan: you should be aware that Kris's short disclaimer really means that
enabling the sysctl exposes sysvipc aware processes on the host to
malicious programs in the jails (and between jails...)



On Mon, 27 Feb 2006, Ivan Kolosovskiy wrote:

> Ivan Kolosovskiy wrote:
> > FreeBSD 6.0-p4. Sharedmem in jail doesnot works. I got "Function not
> > implemented".
> >
> Sorry, i found "security.jail.sysvipc_allowed" sysctl flag =)
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.53.0602271111470.12692>