Fontaine
June 12th, 2008, 03:57 PM
I configured so that when I load my DNS site (e.g. https://myname@dyndns.org), it loads the ssl explorer site. When I log in I have various applications for ssl exp. that I've installed. One of them is remote desktop for windows. When I click it, it loads the ssl explorer agent and then the remote desktop application which takes me directly to the pc I have it configured to connect with. All of this is done via port 443 (https) instead of traditional remote desktop port 3389. My reasoning for doing it this way is so I can load up RD through 443 and stay off any ports where I would be tagged by my work (not that they really care).
If anyone is using this software, would appreciate your input or any advice on useful tweaks. I'd like to continue using it for RD for the most part, but mostly to mask my traffic as https so it blends in with other 443 traffic. Other than having a keylogger on my system, is there a way for network admins to actually view the connection I have when I log in to my remote pc?
If anyone is using this software, would appreciate your input or any advice on useful tweaks. I'd like to continue using it for RD for the most part, but mostly to mask my traffic as https so it blends in with other 443 traffic. Other than having a keylogger on my system, is there a way for network admins to actually view the connection I have when I log in to my remote pc?