| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.1.14 |
| Request #7321 | Please Add SSL support | ||
|---|---|---|---|
| Submitted: | 2006-04-06 06:45 UTC | ||
| From: | wuxipaopao at gmail dot com | Assigned: | garrettw |
| Status: | Closed | Package: | Net_SmartIRC (version 1.0.0) |
| PHP Version: | 5.0.4 | OS: | win XP |
| Roadmaps: | 1.1.4 | ||
[2006-04-06 06:45 UTC] wuxipaopao at gmail dot com
(paopao)
Description:
------------
Please Add SSL support,so SmartIRC could connect to the server use SSL like mIRC
Comments
[2006-04-06 07:27 UTC] wuxipaopao at gmail dot com
I have found the solution.
setUseSockets( FALSE );
connect( 'ssl://the.server', 'the.ssl.port' );
[2014-10-27 10:35 UTC] garrettw
(Garrett Whitehorn)
True, but you shouldn't have to change whether you use sockets or not.
Soon I will remove the need for "real" sockets entirely by replacing all the socket
function calls with stream_socket_* stuff, and that will make it more straight-forward.
[2014-11-03 01:02 UTC] garrettw
(Garrett Whitehorn)
-Status: Feedback
+Status: Closed
-Assigned To:
+Assigned To: garrettw
This bug has been fixed in SVN.
If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.
Ok, you don't need to use setUseSockets() anymore.
Now there are a few ways to connect with SSL:
connect('ssl://server.domain.name', portNumber);
connect('ssl://server.ip', portNumber);
connect('ssl://server.ip.or.domain.name:portNumber');
and you can replace "ssl" with "tls" if your server supports it, and if you want to use an IPv6 address, that works too -- just surround the address portion with brackets, like 'ssl://[fe80::1]:6667' or something.