VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/vmencryption-limitations.dita@ 105515

Last change on this file since 105515 was 105335, checked in by vboxsync, 9 months ago

FE/Qt: bugref:10705. Merging r6149 from doc team's repo.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id Revision
File size: 1.3 KB
Line 
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
3<topic xml:lang="en-us" id="vmencryption-limitations">
4 <title>Limitations of VM Encryption</title>
5
6 <body>
7 <p>There are some limitations the user needs to be aware of when using this feature: </p>
8 <ul>
9 <li>
10 <p>Exporting appliances containing an encrypted VM is not possible, because the OVF specification does not
11 support this. The VM is therefore decrypted during export. </p>
12 </li>
13 <li>
14 <p>The DEK is kept in memory while the VM is running to be able to encrypt and decrypt VM data. While this
15 should be obvious the user needs to be aware of this because an attacker might be able to extract the key on a
16 compromised host and decrypt the data. </p>
17 </li>
18 <li>
19 <p>When encrypting or decrypting the VM, the password is passed in clear text using the <ph
20 conkeyref="vbox-conkeyref-phrases/product-name"/> API. This needs to be kept in mind, especially when using
21 third party API clients which make use of the web service where the password might be transmitted over the
22 network. The use of HTTPS is mandatory in such a case. </p>
23 </li>
24 </ul>
25 </body>
26
27</topic>
Note: See TracBrowser for help on using the repository browser.

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette