Comment 6 for bug 925657

I have also just added a --certificate-name option for the case where the user is using an IP address instead of the correct name. I think it's better than doing a DNS resolve since the user must explicitly add this as a command-line argument, instead of doing something automatic. For instance, if freerdp.com has a valid certificate but I'm using it's IP address to connect to it, validation would succeed if I passed --certificate-name freerdp.com as an argument.

Anything else?