i have a script that works well under non-ssl socket on port 80 to get something. but failed with ssl on port 443
what i do: i simply added a "-e" option to sockopen and modified the port to 443
expected: everything works as on 80, and the server certificate is authorized.
problem:
mIRC warn me that the certificate is invalidate or its name does not match the server name.
i have to press accept button. but the connection is lost when i /sockwrite 1 byte to it
reproduce:
/sockopen -e test1 sourceforge.net 443
/sockopen -e test2 sourceforge.net 443
ssl is enabled because:
/server -m irc +6668 <- no problem (note1)
/server -m sourceforge.net +443 <- no problem (note1)
note1:
both /sockopen and /server warn me that mIRC is "unable to get local issuer ceritifiate". this is somehow ok for /server but unacceptable for /sockopen
can anyone else test it before i post this thread to bug report?
