Virtual OS that only works on a PC: is it possible with new versions of VirtualBox?

[giannino1995]

Can I create a virtual operating system that only works on a PC? I do not want that a user can have a virtual operating system on 1000 different computer copying VirtualBox files into others PC.
New versions of VirtualBox have a function for my purpose?
Thank you and I am sorry for my English

[mpack]

I assume you mean can you node lock the VM to a particular PC.

Basically, no. VirtualBox has no way to prevent the user copying files to another host. You might be able to detect if the CPU is different, but everything else about the VM would be the same. Minor timing differences could also be detected, but IMO these differences would be within the normal variability of a VM on the same host.

[scottgus1]

Virtualbox does not have anything to prevent copying its virtual machines. But Virtualbox has guest encryption, which won't allow anyone to run the virtual machine unless they know the password(s).

Of course anyone who knows the password can give it and the virtual machine to someone else, which would then allow copying a virtual machine and running on other PCs.

For encryption, see the manual, section 9.31. Be very careful with encrypted VMs. Keep an unencrypted backup of your data. See this tutorial Moving a VM and re-interpret it as "Backing Up a VM". Remember that the virtual disk file by itself is not enough to run the guest, you need the .vbox file and the other items in the guest folder too. The .vbox file has the encryption key that works with the password you type in to run the guest. Loos that .vbox file, and your data is gone. Also, don't remove the virtual disk from the guest while it's encrypted - that will also delete the encryption key in the .vbox file and render your encrypted guest unusable.

[giannino1995]

Minor timing differences could also be detected, but IMO these differences would be within the normal variability of a VM on the same host.

Thanks for your answer I understand that I can not do that I would want but I find hard to understand your second sentence, my English is surely too poor.

[mpack]

It's a technical elaboration, but nothing important. The first two words of my previous response (para 2) gives the true answer.

[scottgus1]

When a command is run in the processor, it takes a certain amount of time to run. In a virtual machine it takes more time to run. Some programs can figure out how long the time to run a command takes, and can raise a warning if the command takes too long.

It may be possible to use the timings to tell if the operating system is running on a physical machine or a virtual machine, but not to tell if the operating system is in the original virtual machine or a copy on a different physical computer.

[giannino1995]

Virtualbox does not have anything to prevent copying its virtual machines. But Virtualbox has guest encryption, which won't allow anyone to run the virtual machine unless they know the password(s).

Of course anyone who knows the password can give it and the virtual machine to someone else, which would then allow copying a virtual machine and running on other PCs.

For encryption, see the manual, section 9.31. Be very careful with encrypted VMs. Keep an unencrypted backup of your data. See this tutorial Moving a VM and re-interpret it as "Backing Up a VM". Remember that the virtual disk file by itself is not enough to run the guest, you need the .vbox file and the other items in the guest folder too. The .vbox file has the encryption key that works with the password you type in to run the guest. Loos that .vbox file, and your data is gone. Also, don't remove the virtual disk from the guest while it's encrypted - that will also delete the encryption key in the .vbox file and render your encrypted guest unusable.

Thanks for your answer!
This thing you write seems to be very interesting but I would like to investigate by asking some questions:
1) The password to encrypt the image must be known by the user that uses VirtualBox, by VirtualBox installer (myself) or by both?
2) Encrypted image requires powerful hardware?
3) There are some very simple guides in Italian that I can use to do what I want?

[giannino1995]

It's a technical elaboration, but nothing important. The first two words of my previous response (para 2) gives the true answer.

Thanks

[scottgus1]

1. The user has the password. Virtualbox has a "counter-password" stored in the guest's .vbox "recipe" file that works with the user's password to decrypt the guest for running.

2. The stronger the hardware the better, I think. I haven't tried encrypted guests on a slow machine, but I think slower computer = slower encrypted guest.

3. I don't know if the Virtualbox manual comes in Italian.

Please feel free to post in Italian, and we can try Google Translate.

1. L'utente ha la password. Virtualbox ha un "contro-password" memorizzata nel file .vbox "ricetta" del cliente che funziona con la password dell'utente per decifrare l'ospite per l'esecuzione.

2. La più forte l'hardware il meglio, credo. Non ho provato ospiti crittografati su una macchina lenta, ma penso che più lento del computer = ospite più lento criptato.

3. Non so se il manuale di VirtualBox è disponibile in italiano.

Non esitate a postare in italiano, e siamo in grado di provare Google Translate.

[giannino1995]

When a command is run in the processor, it takes a certain amount of time to run. In a virtual machine it takes more time to run. Some programs can figure out how long the time to run a command takes, and can raise a warning if the command takes too long.

It may be possible to use the timings to tell if the operating system is running on a physical machine or a virtual machine, but not to tell if the operating system is in the original virtual machine or a copy on a different physical computer.

However, I not think that it is a good approach to evaluate the processing time to figure out where an OS works.
Thanks for your answer too

[giannino1995]

1. The user has the password. Virtualbox has a "counter-password" stored in the guest's .vbox "recipe" file that works with the user's password to decrypt the guest for running.

2. The stronger the hardware the better, I think. I haven't tried encrypted guests on a slow machine, but I think slower computer = slower encrypted guest.

3. I don't know if the Virtualbox manual comes in Italian.

Please feel free to post in Italian, and we can try Google Translate.

1. L'utente ha la password. Virtualbox ha un "contro-password" memorizzata nel file .vbox "ricetta" del cliente che funziona con la password dell'utente per decifrare l'ospite per l'esecuzione.

2. La più forte l'hardware il meglio, credo. Non ho provato ospiti crittografati su una macchina lenta, ma penso che più lento del computer = ospite più lento criptato.

3. Non so se il manuale di VirtualBox è disponibile in italiano.

Non esitate a postare in italiano, e siamo in grado di provare Google Translate.

1) I'm sorry but I do not understand. I would understand if the effect of virtualbox password is identical to the operating system password. If I put a password on the operating system I have to give the password to the user so this system is not a solution. If the user uses encrypted image without to know it then your solution is good. You write that the user has the password so I do not think that your solution solves my problems. The use must not move virtualbox image, I only need to be able to do it.

[socratis]

VirtualBox VMs are files on your computer.
If a user can move/copy files on the computer, they can move/copy the VirtualBox VM.
If the user knows the password to a VM (not the OS, the VM), they can use the VM.
You have to find another way to lock your VM. VirtualBox has limited ways to do it.

[giannino1995]

Can I use a cross platform criptography software?

I have seen these programs:

FileDecoder, PixelCryptor, ProtectFile e Drag’n Crypt ULTRA

but they force the user to type the password to read the VM files.

[scottgus1]

We don't know from nothing but Virtualbox, and Virtualbox can't do what you want.