At 8:48 PM -0500 8/4/03, Jonathan Angliss wrote:
> no-one wants to tackle this, I guess?
I think I missed the original message... so lets see...
apologies and thanks.
Did you make sure you installed PHP with OpenSSL support? If you don't,
the n the login will fail.
good question. OpenSSL is on the server but I don't recall
explicity integrating it.
MacOSX people often use Marc Liyanage's binaries, found
here:
http://www.entropy.ch/software/macosx/php/
I currently have an older version of his PHP, which is reflected
in the phpinfo you looked at here:
>> http://tools.whybark.com/phpinfo.php
Hrm... I don't see OpenSSL options enabled in there... are you sure you
compiled it correctly? You might want to verify that, and test again.
the new version's phpinfo looks like this:
http://www.entropy.ch/software/macosx/php/test.php
I'm likely to toss it on the server to see what happens. Do you
see the ssl flags you are looking for?
I noticed this:
'--with-openssl=/usr'
and
'--with-imap=../imap-2002d'
'--with-imap-ssl=/usr'
in the config dump
looking forward to hearing from you again.
>From the basic error message, it looks like we established a socket
connection, but it got closed again because of the failure to negotiate an
SSL transaction. The curious thing however is that your configuration
didn't complain about the lack of openssl compile, what do you have for
display_errors and error_reporting in your php.ini file? Did you enable
TLS/SSL in the configuration?
perhaps simply having openssl inplace and active on the server
shortcircuited that problem while PHP's lack of support for it led to
the timeouts.
traipsing this path seems more promising than the old stunnel
stuff ;)
[..]
off topic
logins and plaintext - sounds worth exploring a bit. maybe an
option to enable/disable plaintext and/or plaintext readback on error
in the config script? At any rate - looking forward to trying again,
and thanks for your help.
--
Mike Whybark - [EMAIL PROTECTED]
http://mike.whybark.com/
http://mike.whybark.com/
