proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-04-29 00:07:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

cluster: migration: use back-ticked insecure when referring to the setting

Browse Source 
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2021-11-17 14:05:01 +01:00 committed by Thomas Lamprecht
parent 8e0e0bcf35
commit da0c67934c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pvecm.adoc
View File

@ -1273,7 +1273,7 @@ Migration Type
The migration type defines if the migration data should be sent over an The migration type defines if the migration data should be sent over an
encrypted (`secure`) channel or an unencrypted (`insecure`) one. encrypted (`secure`) channel or an unencrypted (`insecure`) one.
Setting the migration type to insecure means that the RAM content of a Setting the migration type to `insecure` means that the RAM content of a
virtual guest is also transferred unencrypted, which can lead to virtual guest is also transferred unencrypted, which can lead to
information disclosure of critical data from inside the guest (for information disclosure of critical data from inside the guest (for
example, passwords or encryption keys). example, passwords or encryption keys).
@ -1286,7 +1286,7 @@ NOTE: Storage migration does not follow this setting. Currently, it
always sends the storage content over a secure channel. always sends the storage content over a secure channel.
Encryption requires a lot of computing power, so this setting is often Encryption requires a lot of computing power, so this setting is often
changed to "unsafe" to achieve better performance. The impact on changed to `insecure` to achieve better performance. The impact on
modern systems is lower because they implement AES encryption in modern systems is lower because they implement AES encryption in
hardware. The performance impact is particularly evident in fast hardware. The performance impact is particularly evident in fast
networks, where you can transfer 10 Gbps or more. networks, where you can transfer 10 Gbps or more.