[Phpmyadmin-devel] SSL connections broken under PHP 5.5.17 (PHP's bug)
Hi, this is just for informational purposes -- our code is fine. PHP 5.5.17 seems to break mysqlnd when connecting via SSL. You can see the bug report[1] if you're interested. I know we do some PHP (and MySQL) version tests, but is it appropriate in this case to catch version 5.5.17 and warn the user about this bug? Thanks to IRC user deuterium for figuring out the problem. 1 - https://bugs.php.net/bug.php?id=68046
Isaac Bennetch a écrit :
Hi, this is just for informational purposes -- our code is fine.
PHP 5.5.17 seems to break mysqlnd when connecting via SSL. You can see the bug report[1] if you're interested.
I know we do some PHP (and MySQL) version tests, but is it appropriate in this case to catch version 5.5.17 and warn the user about this bug?
Thanks to IRC user deuterium for figuring out the problem.
Hi Isaac, taking into account that phpMyAdmin 4.2.10 will probably be released in two weeks, I suggest to wait a bit and see if there is a PHP 5.5.18 out at this point. -- Marc Delisle (phpMyAdmin)
Marc Delisle a écrit :
Isaac Bennetch a écrit :
Hi, this is just for informational purposes -- our code is fine.
PHP 5.5.17 seems to break mysqlnd when connecting via SSL. You can see the bug report[1] if you're interested.
I know we do some PHP (and MySQL) version tests, but is it appropriate in this case to catch version 5.5.17 and warn the user about this bug?
Thanks to IRC user deuterium for figuring out the problem.
Hi Isaac, taking into account that phpMyAdmin 4.2.10 will probably be released in two weeks, I suggest to wait a bit and see if there is a PHP 5.5.18 out at this point.
PHP 5.5.18 has been released on Oct 16 with a fix for this regression. -- Marc Delisle (phpMyAdmin)
Le 01/10/2014 20:03, Isaac Bennetch a écrit :
Hi, this is just for informational purposes -- our code is fine.
PHP 5.5.17 seems to break mysqlnd when connecting via SSL. You can see the bug report[1] if you're interested.
I know we do some PHP (and MySQL) version tests, but is it appropriate in this case to catch version 5.5.17 and warn the user about this bug?
Thanks to IRC user deuterium for figuring out the problem.
FYI, this regression affects 5.4.33 and 5.5.17 (not 5.6.0) The changes have be reverted in 5.5.18 (in 2 weeks) and 5.6.1 (today) so should work as previously (I have no date yet for a 5.4.34) The changes are still available in all branches and another patch is waiting for test (so, perhaps for 5.5.19 / 5.6.2) So if someone, affected by this issue, is able to test the patch attached to 41631 [1], feedback is very welcome (changes have be reverted (partially) because of lack of feedback, but the changes also fix some annoying bugs, which need to be fixed...). Regards, Remi. [1] https://bugs.php.net/patch-display.php?bug=41631&patch=bug41631.patch&revisi... (simple to test against 5.6.1RC1 which have "all" the others changes, while 5.5.17 have only some of them)
participants (3)
-
Isaac Bennetch -
Marc Delisle -
Remi Collet