Bug #11587 Updated: SSL'd fsockopen would be nice

ID: 11587 Updated by: wez Reported By: mitja@doticni.net Status: Duplicate Bug Type: Feature/Change Request Operating System: PHP Version: 4.0.5 Old Assigned To: Assigned To: wez New Comment: When we have streams, this will be there. (it's in the pipeline). --Wez. Previous Comments: ------------------------------------------------------------------------ [2001-08-12 15:28:52] sebastian@php.net This extends Bug #5865. ------------------------------------------------------------------------ [2001-06-20 14:18:10] mitja@doticni.net While working on #5865, you could also add generic SSL socket support to fsockopen, something like fsockopen("ssl://example.com", ...) don't forget to add support for client certificates/keys, including passing the password to unlock 'em (ok, this would probably require a completely new function). for connecting to a single server, one solution is running a stunnel daemon: stunnel -c -d 127.0.0.1:1000 -r example.com:123 -p /certs/blah.pem and then fsockopen()ing to that port; however, this is both a security problem (anyone on the machine can connect to that port) and useless, if one wishes to connect to a host that is not known in advance. another option would be to allow php to talk to exec'd processes (hopefully stunnel works this way; it doesn't when piped), but this requires an extra process per request which is a resource hog. and, well, this is all in openssl already, so ... ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=11587&edit=1