Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Oct 2008 00:12:54 +0000
From:      Desmond Chapman <que_deseja@hotmail.com>
To:        <vbox-users@virtualbox.org>, <freebsd-questions@freebsd.org>, <freebsd-ports@freebsd.org>
Subject:   virtualbox kBuild security
Message-ID:  <BLU126-W22857E9484003814C2F47DED300@phx.gbl>

next in thread | raw e-mail | index | archive | help






http://www.virtualbox.org/ticket/1499

http://wiki.archlinux.org/index.php/VirtualBox#Getting_USB_to_work_in_the_g=
uest_machine

Even though these issues relate to Linux hosts=2C I have had the same resul=
ts while trying to build on FreeBSD. That which applies the PUEL release al=
so applies to the OSE release.




This problem still exists for FreeBSD amd64 when building VBox current.
kBuild is still a security risk due to it changing permissions without the =
users consent.=20
The developers have not stated if the qemu code used in vbox is current wit=
h that used in FreeBSD nor if the networking and image options- qemu relate=
d- needed to work on FreeBSD amd64 current have been added.=20

Please do not reply to this message.










_________________________________________________________________
Want to do more with Windows Live? Learn =9310 hidden secrets=94 from Jamie=
.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!5=
50F681DAD532637!5295.entry?ocid=3DTXT_TAGLM_WL_domore_092008=



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