wildcard SSL certificates *.domainname.com not properly supported
|Reported by:||Pierre Grandmaison||Owned by:|
|Keywords:||wildcard SSL certificate||Cc:|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows XP, Vista, 7|
1) We have a rapidSSL wildcard SSL certificate such as *.domainname.com and when I connect to something.domainname.com, filezilla still gives me the warning, even though it is a valid SSL certificate which is recognized without warning by both firefox and internet explorer over regular https.
Once we accept the certificate once, we never have the issue again (as long as we select to save our answer so it doesn't ask again)
however, it would be nice if filezilla could authenticate wildcard certs similar to what IE and firefox do over regular https for wildcard certs.
2) There is no way to see the downloaded SSL certificates so that you can review the list / clear it if necessary to force an full SSL cert check again at the next connection. (If there is a way, I couldn't find it).