Set virtualbox vrde-property #5823
Merged
+3
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With version 7.1.0 VirtualBox changed the default behavior of RDP encryption if a user hasn't created own certificates.
See the VirtualBox changelog:
Old default:
VirtualBox used hard wired internal certificates or even no encryption.
Since the self-signed certificates are not known by the host the first RDP connection to a VM starts with a warning like this (provided by a volunteer from LHC@home):
The VirtualBox manual gives a hint how the old behavior can be enabled:
https://www.virtualbox.org/manual/topics/remotevm.html#vrde-crypt
Vboxwrapper should configure VMs using standard RDP instead of TLS to avoid the warning message being presented for each fresh VM.