Date: Sat, 15 Feb 2020 21:41:04 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 231480] sysutils/grub2-bhyve: "(host)" filesystem is a potential security issue Message-ID: <bug-231480-7788-i7Onz37186@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231480-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-231480-7788@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=3D231480 Conrad Meyer <cem@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ports-bugs@FreeBSD.org |cem@freebsd.org CC|cem@freebsd.org |grehan@FreeBSD.org --- Comment #3 from Conrad Meyer <cem@freebsd.org> --- bhyveload(1) uses the '-h hostdir' flag for this. This is similar to '-r h= ost -d hostdir' in grub-bhyve syntax; however, '-r host' is the default in grub-bhyve. '-h' is available in grub-bhyve, but I would avoid using it for anything ot= her than '--help'. We could treat explicit '-r host' similar to explicit '-h hostdir' in grub-bhyve. That is, do not allow host filesystem access _at all_ unless '= -r host' was specifically provided as a parameter. This would retain compatibility with vm-bhyve's use of '-r host', while denying host filesyst= em access by default. Thoughts? I'll propose a patch via github eventually but I view this as orthogonal to the privdrop proposal above, and will wait until that is resolved. --=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-231480-7788-i7Onz37186>