Hi,
The term "opening a port" has gotten a lot of bad press in recent years. All this really means is:
1) Some piece of software is "listening" for connections on some TCP port number
2) You [possibly] open your firewall to allow those connections to reach your PC
You do not have to do #2, if you do not want, in which case the fact that PhoneMyPC is listening doesn't matter at all. You can use PhoneMyPC without the direct-connect port.
But, the security risk comes in the software that listens on that port. It used to be the case that, for example, Microsoft IIS started an FTP server on port 21. This meant that anybody savvy to this fact could connect to your FTP server and possibly use an anonymous account to access (or upload) files, or even attempt to hack a real account.
This is where firewalls come in. If you have a firewall and configure it to allow "nothing" to reach your PC, then it doesn't matter what programs on your PC are listening for because they'll never receive a connection.
In this regard, PhoneMyPC is pretty safe. Once the software receives a connection, it sits in "sand-box" mode waiting for a proper authentication sequence, and it is a very good authentication method. If it does not receive the proper sequence, or if it receives even one byte that isn't correct, it drops the connection and goes back to listening.
What this means is that if you have the direct-connect port open in your firewall, anybody could write software that would connect a socket to your computer. But, once connected, they can neither send nor receive data, except for the proper and expected authentication sequence. That is only possible if the program knows two things:
1) The proper protocol to use (this could be learned by watching your network traffic and reverse engineering it)
2) Your user name and password (this can NOT be learned by watching your network traffic)
On the update front, here is a quick status update:
* SSL -- working
* Login -- working
* Unlock -- working
* Auto-Update (for the PC) -- working
There is just one little glitch left to hammer out: occasionally, when you log-in, the portion of code that gathers screen data is running in the wrong desktop and cannot access that data. This won't take long to fix--perhaps even today.
By the way: did you know there are literally hundreds of permutations of 'ways a login can occur?' I think we've got them all down now