How to encrypt the traffic that goes through RDP from the provider?

There is a server (not mine) in another country with my Internet, I connect to it through the built-in rdp wn.
You want to hide from your ISP traffic, if he sees it when I go there I go: on any page go to the browser, etc.
Is it possible to achieve this by setting themselves further and VPN connections to remote desktop? Or are there any other ways?
July 8th 19 at 15:42
4 answers
July 8th 19 at 15:44
Solution
so, afaik, rdp is able to encrypt the traffic out of the box.
July 8th 19 at 15:46
Solution
Like the option of using an ssh tunnel.
The principle is this,
One network - 192.168.0.X
rdp server is 192.168.0.2
ssh server - 192.168.0.10
In some cases, routers can be the ssh server
client outside connects to ssh server and creates a tunnel 192.168.0.2:3389 to local port 44444
then installed rdp to 127.0.0.1:44444
traffic goes through the tunnel.

To encrypt the traffic using a VPN, in this case it is possible to configure so that the client computer will be part of a network, with all the consequences....

Config for sshd with keys
user@ssh:~$ cat /etc/ssh/sshd_config
# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 999
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow [11~client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

PermitTunnel yes
PermitOpen 192.168.0.2:3389 192.168.0.20:3389


Maybe a bunch of extra (comments have been removed.) if there's something critical - tell me...
Thanks for the time in the config. =)
With the standard config by default and encrypted traffic, and tunnels can be opened in any direction. - Carli commented on July 8th 19 at 15:49
July 8th 19 at 15:48
Solution
Use RDP version 6.0 and above.

https://en.wikipedia.org/wiki/Remote_Desktop_Proto...
128-bit encryption, using the RC4 encryption algorithm, as of Version 6.
Support for Transport Layer Security (TLS) 1.0 on both server and client ends (can be negotiated if both parties agree, but not mandatory in a default configuration of any version of Windows).


The provider will see that You have connected to this server via RDP, but will not know what you do, where You click, etc.
If you want to hide from the provider the fact of connection of RDP. in principle, connect to RDP over VPN.
July 8th 19 at 15:50
Solution
1. Encryption, in fact, two sides configure.
2. RDP is encrypted.
3. How do you imagine someone is looking for you, there are pictures and not text is transmitted.

Find more questions by tags RDPVPNSSH