notfred wrote:Yup, RDP or VNC and you can potentially throw the VNC through an SSH forwarded port to get it through firewalls and add security.
just brew it! wrote:notfred wrote:Yup, RDP or VNC and you can potentially throw the VNC through an SSH forwarded port to get it through firewalls and add security.
TBH I would not expose *either* protocol directly to the Internet, given MS's security track record and the inherently rather weak security of the base VNC protocol. I prefer to run both of them through an encrypted tunnel (typically a SSH forwarded port, as you suggest).
bthylafh wrote:I put my SSH and RDP daemons on random high TCP ports instead of the default. If nothing else that will stop the bots.
Haven't tried running RDP though an SSH tunnel.
Flying Fox wrote:RDP is pretty decent (they started out with 40-bit encryption right off the bat and upgraded to 128-bit fairly early, around early 2000s once the export control was relaxed), except for the latest security bulletin that they patched.
just brew it! wrote:Yup, doing what you're trying to do has been made difficult on purpose. The currently logged in session effectively "owns" the desktop; allowing background processes from other users to arbitrarily open up new windows would be a rather large security hole!
Users browsing this forum: Google [Bot], Yahoo [Bot] and 1 guest