27 Oct
2014
27 Oct
'14
3:54 p.m.
@Aleksey, yes it's vulnerable just the same. Git, MSYS, cygwin, doesn't
matter.
@Colin, if the BuildBot slave is running as a service, then that's
likely the reason.
Looks like VBoxManage fails to communicate with the RPC server due to
session 0 isolation. A quick try from a psexec command prompt fails for
me too.
One option to solve this seems to be the "VBoxVmService" project:
http://sourceforge.net/projects/vboxvmservice/
Unfortunately I don't have any experience with this so I don't know how
well it works or if there's a better way.
On 2014-10-27 16:07, Aleksey Bragin wrote:
Speaking of which, I wonder, if bash for windows
contained that famous
vulnerability?
Regards,
Aleksey
On 27.10.2014 18:04, Colin Finck wrote:
> Hi all,
>
> As you can see in project-tools SVN, I've improved our Bash scripts for
> Buildslaves. They're now also usable under Windows (in a Cygwin
> environment) and I'm already doing this on our new Windows Buildslave
> Carrier-Win7.
> Bash on Windows may look hacky at first, but it's definitely more
> comfortable than Batch! Moreover, we now only have a single version of
> build scripts to maintain for all our Buildslaves!
> This also involved some naming changes on the existing slaves to
> maintain a consistent scheme. Tell me if anything broke.
> Bringing all desired Windows builders back will still take some time.
> I've only started with a RosBE-Windows based one right now and I need
> your help here:
>
> For some reason, VirtualBox 4.3.18 (used for reg-testing) doesn't want
> to run headless. I can do a 'runas /user:buildbot VBoxManage controlvm
> "ReactOS Testbot" poweroff' in a CMD and it will work well. The very
> same command executed through BuildBot ends with:
>
> ====================================================================
> VBoxManage.exe: error: Failed to create the VirtualBox object!
> VBoxManage.exe: error: Code E_ACCESSDENIED (0x80070005) - General access
> denied error (extended info not available)
> VBoxManage.exe: error: Most likely, the VirtualBox COM server is not
> running or failed to start.
> ====================================================================
>
> See
>
http://build.reactos.org/builders/Carrier-Win7%20VBox-Testbot/builds/6/step…
> VBoxSVC.log isn't touched when BuildBot tries this command, so I have no
> additional information.
>
> Haven't found a solution yet, so I'm asking here if any of the VBox
> experts know what could be going wrong.
>
> Cheers,
>
> Colin