Date: Mon, 08 Aug 2016 15:37:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 211580] deny system message buffer access from jails Message-ID: <bug-211580-9824-BrNYW9ThxT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211580-9824@https.bugs.freebsd.org/bugzilla/> References: <bug-211580-9824@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211580 --- Comment #5 from Joe Barbish <qjail1@a1poweruser.com> --- I have been thinking about this more and I remember having this discussion = some time a few years ago in the past. There is nothing wrong with the dmesg com= mand issued from within a non-vimage jail showing the in kernel message info. Th= is also happens with the ifconfig command when issued from within a non-vimage jail.=20 The intent was not to give a compromised jail attacker any indication he was not on the host, but in a jailed environment. Turning off dmesg or ifconfig when issued from a jail would indeed be such an indication. In a vnet/vimage this would also be true for the dmesg command. This is not a bug, but done by design with intent.=20 This pr should be closed. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211580-9824-BrNYW9ThxT>