ID: 21642
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: Sockets related
PHP Version: 4.3.0
New Comment:
Hi Wez,
i know this prolly no faq here but im sticky since days on it and i
didnt get help anywhere yet, so excuse my last question in this thread
please.
example:
<?PHP
$sock = fsockopen($server, $port, $errno, $errstr, timeout);
fgets($sock....);
if TLS then {
frwite (ftp, "AUTH", "TLS"))
//to use php_stream_api or streams and options
//and swtich into ssl mode ? like php.ftp it does ?
// ctx = SSL_CTX_new(SSLv23_client_method()); ?????
//or a simple stream wrapper from php
frwite(ftp, "PBSZ")
.
...and so on.....
}
?>
a simple "yes" or "no" from your side would be enough, so
ill try to figure it out by myself.
Maybe theres something easie php-trick i dont know,
to solve this problem.
Also theres no help available on the web to it.
Im sorry to waste your time in here , but its realy importand to
realize it in php.
Toppi
Previous Comments:
------------------------------------------------------------------------
[2003-01-15 07:23:13] [EMAIL PROTECTED]
fsockopen is intended to open *only* a raw socket and not implement
some protocol level stuff -> that is what the URL wrappers are for in
fopen().
Please try one of the alternative methods for working with secure ftp.
If you find a problem with those, then open a new bug report.
------------------------------------------------------------------------
[2003-01-15 05:51:31] [EMAIL PROTECTED]
Please add rfc2228 handle to fsockopen();
:-)
------------------------------------------------------------------------
[2003-01-15 05:41:13] [EMAIL PROTECTED]
Just info when using fopen();
it retruns
Warning: fopen(ftps://...@ip:port) [function.fopen]: failed to create
stream: Operation not permitted in .....
------------------------------------------------------------------------
[2003-01-15 05:12:21] [EMAIL PROTECTED]
TLS becomes more a standard instead of FTP.
I cant recognize the reason why fsockopen() doesnt handle tls/ssl
similare to fopen().
Why not starting (like fopen() it does) in clear mode, then switch to
tls/ssl if this all is FLASE return fail ?
Atm i have to run a TLSwrapper in background to connect FTP+TLS cause
fsock yes but ssl...
The use of Curl or fopen instead ? Sounds a bit crazy for me tho :)
A Create a socket function should handle all streams.
Im looking forward to fsockopen supports ftp+tls :)
Greetings
Toppi
------------------------------------------------------------------------
[2003-01-14 16:41:05] [EMAIL PROTECTED]
this is expected behaviour; fsockopen("tls://") opens the socket with
TLS turned on.
By default, TLS-enabled ftp servers start "in the clear" - with crypto
turned off.
If you want to use TLS over ftp, consider using fopen("ftps://")
instead (which will attempt TLS negotiation according to the relevant
rfcs), or if that is not sufficient, try using the curl functions.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21642
--
Edit this bug report at http://bugs.php.net/?id=21642&edit=1
