D
David P. Lurie
What is the current encryption and authentication protocol used by RD (I
assume RD and RD Web Connection are the same), and is it equivalent to
current OpenSSH from Cygwin (3.7.1p2-2), using SSH2?
I usually use RD from home to office through a VPN tunnel, such that the
office router doesn't have to forward 3389 and/or 80. The coprocessors on
the VPN routers (linksys) are fast enough that performance degradation
through the VPN tunnel c/w direct isn't enough to risk opening 3389 on the
office router.
Future needs require office access from elsewhere via RD or RDWC, which will
require 3389 (and 80 for RDWC) forwarded on the office router.
If RD/RDWC is less secure than SSH2, RDWC with TCP port forwarding (80 and
3389) via an SSH2 tunnel with PuTTY from remote clients may be feasible.
However, I'm concerned that the overhead from the software-only SSH2 tunnel
will be higher.
Thanks,
David P. Lurie
assume RD and RD Web Connection are the same), and is it equivalent to
current OpenSSH from Cygwin (3.7.1p2-2), using SSH2?
I usually use RD from home to office through a VPN tunnel, such that the
office router doesn't have to forward 3389 and/or 80. The coprocessors on
the VPN routers (linksys) are fast enough that performance degradation
through the VPN tunnel c/w direct isn't enough to risk opening 3389 on the
office router.
Future needs require office access from elsewhere via RD or RDWC, which will
require 3389 (and 80 for RDWC) forwarded on the office router.
If RD/RDWC is less secure than SSH2, RDWC with TCP port forwarding (80 and
3389) via an SSH2 tunnel with PuTTY from remote clients may be feasible.
However, I'm concerned that the overhead from the software-only SSH2 tunnel
will be higher.
Thanks,
David P. Lurie