gtOrenoPC is a Windows application that enables very secure remote desktop access over the Internet. If you have a Windows XP Professional or already installed a VNC (free remote desktop application), you can install gtOrenoPC onto your home PC in a few minutes and your PC is ready to be made accessible over the Internet in a very secure way.
On PCs that you will use to access your home PC, you don't need to install anything besides a standard Java 5 or later. Just point your browser to gtOrenoPC running on your PC and log in.
There are several tools that can be used for cracking into RDP systems. TSGrinder, and TSCrack are famous ones. These tools can be readily used to find the password for "Administrator".
By the way, when was the last time you typed Administrator's password on your Windows XP Professional? Oh, you don't have "Administrator" account on your Windows? You should have it unless you already renamed it. Windows XP just hides it not to confuse end users, but WITHOUT DISABLING IT. And because it has administrative privilege, "Administrator" can log in via Remote Desktop by default. "Administrator" is also immune to account lockout that results from excessive login attempts.
As of version 1.0, gtOrenoPC has become a shareware product from Orenosv.com.
Go to Orenosp Secure Reverse Proxy Download Page to download latest version of gtOrenoPC. You can purchase a license on the same page.
Windows XP SP2 Compatibility Issue: please see hereYour home PC
gtOrenoPC is developed and marketed by Kousec Software, Inc.. For the transfer from Orenosv.com in May, 2009, please see this notice.
| Without a centrally managed security gateway | With gtOrenoPC | |
| Firewall / Router Configuration | Each time a new PC is added for remote access, you need to configure your firwall to 1) open up a dedicated TCP port for the PC, 2) define a forward rule for the TCP port to a fixed IP address. | Simply open a single fixed TCP (usually 443) and forward it to the gtOrenoPC gateway PC, and you are done with FW. You do need to configure gtOrenoPC, but it can give you many flexible options. gtOrenoPC maps a "destination label" to a hostname and resolves the hostname into an IP address which may be assigned by DHCP. |
| User Authentication | Not centrally managed. End users may use a simple shared password. Also, how user authentication data is sent across over the Internet is very important. Even when session data is encrypted, generally the user authentication occurs before that. If your vendor says that only password hashes are sent and does't give more details, you should just ask for SSL/TLS for safety. | You can specify multiple users with their own passwords, all centrally managed on gtOrenoPC gateway. You can optionally use Windows passwords to validate users passwords. All user authentication data will be sent over SSL/TLS. |
| User Access Control | Once you configure your FW, the end user for the PC decides all. You can only enable or disable forwarding on FW. | You can specify a unique access control list for each remote desktop PC in the LAN, all centrally managed on gtOrenoPC gateway. Of course, the end user can additionally restrict access to their PC. |
| Encryption | Maybe proprietary "encryption". Generally, if your vendor says they have "N-bit encryption" or "Famous-Crypto-Algorithm-Name encryption" without giving you details about how enryption key are generated/exchanged, you should just ask for SSL/TLS support, or you may want to wrap it around with IPSec or SSL tunnels. See RDP encryption vulnerability |
Uses open-standards based SSL/TLS, which is proven by crypto and IT security experts |
| Audit Logging | Access records are accumulated on every remote-accessed PC. If the disk overflows, the end user may simply disable access logging or erase the access log. | Two kinds of access records are logged on gtOrenoPC gateway, one is in industry-standard Web server format (CLF), the other is for usage statistics (useful for accounting, etc). You can control how much access records will be retained. |
| VNC alone | VNC + gtOrenoPC | |
| User Authentication | Many VNC variants only have a simple single password protection, which isn't protected over the communication channel. | In addition to the VNC authentication, gtOrenoPC can enforce centrally managed user identification and authentication. |
| Encryption | Many VNC variants don't have any encryption. Many people use SSH tunneling, whose security is pretty good but lacks FW-friendly port aggregation and it's not suited to wide range of end users. | SSL/TLS. |
| Audit Logging | Some VNC variants have access logging. | Access log is centrally retained on gtOrenoPC gateway. |
| Windows Remote Desktop or Terminal Services alone | RDP + gtOrenoPC | |
| Firewall / Router | Open one TCP port on firewall and done. Windows Remote Desktop (or Terminal Services) Web Connection will not solve firewall or NAT issues. It's just like VNC Java applet client, that is, it is just a package to allow you to download necessary client files from IIS. After that, you are on your own. | gtOrenoPC will solve firewall, NAT and proxy issues both at server side and client side. |
| Encryption | A custom encryption protocol using RC4. | SSL/TLS. |
| Audit Logging | Does Windows Remote Desktop have a logging feature? I haven't even cared. Terminal Services, probably yes. | If you manage several Remote Desktop and Terminal Services PCs, you will need centralized access log management. See general comparison |