VRDP: How to use RDP 5.2

[belhaven]

I am interested in making use of VRDP to connect to a virtual machine over the internet. I have the following working:

• VRDP using "Null" setting, accessed via client (rdesktop and Remote Desktop Connection)
  VRDP using "External" setting, accessed via client (rdesktop and Remote Desktop Connection)

My question pertains to Chapter 7 of the User's Manual, in the "RDP Encryption" section. In that section, the following statement is made:

RDP5.2 authentication is based on TLS 1.0 with customer-supplied certificates. The server supplies a certificate to the client which must be signed by a certificate authority (CA) that the client trusts (for the Microsoft RDP Client 5.2, the CA has to be added to the Windows Trusted Root Certificate Authorities database). VirtualBox allows you to supply your own CA and server certificate and uses OpenSSL for encryption.

I cannot find in the documentation, or my online searches, a source which gives some instruction on how to set up the bolded feature above. I am a little worried because the next line of the User's Manual states the following:

While VirtualBox supports all of the above, only RDP5.2 authentication should be used in environments where security is a concern. As the client that connects to the server determines what type of encryption will be used, with rdesktop, the Linux RDP viewer, use the -4 or -5 options.

If I use rdesktop with the default "-5" option, don't I still need some way to provide the certificate from the server, in this case, VirtualBox? Doesn't the RDP 5.2 authentication require a certificate to be passed from the server to the client, to ensure that the transmission has not been intercepted somewhere along the way?

How do I go about setting up this type of authentication for VirtualBox?

I am quite new to this subject, so I apologize if I am missing something obvious. Thanks.

[frank]

Sorry, that information in the manual was just wrong. VirtualBox up to version 4.0.10 does NOT support RDP 5.2. Although the upcoming 4.1 release will support it.