#19121 [Bgs]: fsockopen("tls:// .... fails without reason.

ID: 19121 Updated by: rasmus@php.net Reported By: mbabcock-php@fibrespeed.net Status: Bogus Bug Type: Sockets related Operating System: Linux 2.2.14 PHP Version: 4.2.2 New Comment: 4.2.2 was a security-fix release. No new features. The tls:// stuff is a new feature in 4.3 as documented. Previous Comments: ------------------------------------------------------------------------ [2002-08-27 18:21:25] mbabcock-php@fibrespeed.net Thanks for the version check comment; for some reason I assumed that since I'd updated to the latest publically available version of php the day before starting this test that the feature was available. Obviously, that is not true. It would be nice if someone encouraged derick@php.net to read the fine manuals himself instead of immediately pulling a 'user error -> bogus'. ------------------------------------------------------------------------ [2002-08-27 09:40:05] wez@php.net The docs for fsockopen state: As of PHP 4.3.0, if you have compiled in OpenSSL support, you may prefix the hostname with either 'ssl://' or 'tls://' to use an SSL or TLS client connection over TCP/IP to connect to the remote host. Your version of PHP is not PHP 4.3, so this won't work. ------------------------------------------------------------------------ [2002-08-27 09:32:51] derick@php.net Never mind that, just lose the tls:// and you can connect fine, but of course you need to send encrypted packets yourself. fsockopen opens a _socket_, not an URL. User error -> bogus ------------------------------------------------------------------------ [2002-08-27 09:30:50] derick@php.net Where did you read PHP supports tls:// ? Derick ------------------------------------------------------------------------ [2002-08-27 09:24:09] mbabcock-php@fibrespeed.net I'm doing the following: $fp = fsockopen("tls://hostname.domain.com", 2080, $errno, $errstr, 30); if (!$fp) die ("Unable to connect: $errstr ($errno)"); ... its giving me "Unable to connect: (0)" every time (hostname.domain.com is a valid Internet host I administer). I'm running a "tcpdump -n port 2080" on the web server and there are no packets showing up at all. There are no messages in /var/log/(messages|daemon|kern) or in the Apache error_log. Any ideas? Feel free to connect to https://www.fibrespeed.net/phpinfo.php for information on my configuration. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19121&edit=1