Sensitive info in VBox.log?

[mightyiam]

I would like to share a VBox.log with the developers.

What sensitive information can the VBox.log file possibly contain, besides the obvious, directory paths?

[loukingjr]

You can look at the vbox.log and see what it contains.

[Perryg]

I suggest you read the log and see. No one can determine what you deem sensitive. For what it's worth the DEVs really don't care about your data or file structure. Unless you are doing something illegal it really does not matter.

[mightyiam]

I'm sure they don't care which country I'm spying on and I know I can read the file.

But it is 1626 lines long and this is a relevant question so perhaps an official answer will help me and the next guy.

[loukingjr]

The important bit of Perry's post…

No one can determine what you deem sensitive.

[Perryg]

I quote myself.

No one can determine what you deem sensitive

As far as I am concerned there is nothing that sensitive that prevents posting the log file. Plenty people post here daily.

[mightyiam]

Alright. Thank you.

[scottgus1]

About the only thing I've seen folks get in "trouble" over by posting a log file is when they're trying to run a Mac guest on a Windows host...

[mpack]

To be specific: the log doesn't include your bank details or your mother's maiden name, nor which porn sites you recently visited. It does include host paths to VDI files etc, from which we can guess what your username is on that host - but not your password (if any). We can tell what the host OS version is, and what guest OS you are trying to to run. Other than that it's a lot of mundane statistics about the simulated hardware and resources such as RAM available and used.

[mightyiam]

And may I also add that the name of the guest VM may also contain your project name, which is usually the case with Vagrant, for example.

[mpack]

Any discussion of what third party software (e.g. Vagrant) does is out of place here. We can only tell you what VirtualBox does.