what about a autotest in the QA to prevent the same as on 2011-08-18 happen 3 years later?
what is that difficult to write a simple script connection to mysql over TCP with SSL and run it before propose a release and why does nobody care about such a major regression?
My setup: roundcube-1.0.2 + nginx-1.6.2 in a FreeBSD-10 jail. RC will connect to a recent dovecot server in another jail at the same host.
Recompiling every port involved and restarting both involved jails hasn't been successful. Only, reverting back to php 5.4.32 made RC work again.
Is anyone running into this as well?
Yes, we know about this. It was addressed on the mailing list within a couple of hours of the 5.5.17 and 5.4.33 releases. People *do* care about a regression like this.
Part of the problem is that the streams API has exactly zero test cases and the openssl streams have very few. So when we try to fix one bug there is always the potential to cause another that isn't prevented by preexisting tests.
There are volunteers working to improve these aspects of the php-src codebase to help avoid these issues going forward, but it just takes time.
This is actually not a mysqli issue -- it's an openssl streams issue and has to do with feof() never reporting as true when it should (which causes the script to hang indefinitely). However, any test cases you feel would help can certainly be added. Please submit pull requests via the git account and I will happily merge them.
how often do i need to post how to test this?
what do you do with a pull-request of a code using our own rwapper around mysqli?
Please submit a PR if you think you have something useful to contribute to the project instead of trying to push it off on other people. Complaining is being part of the problem. Contributing is being part of the solution. Thanks for your time.
One line fixes are super easy to PR.
Any I idea when 5.5.18 will be release to fix this issue please?
So do I have to live with a broken version of PHP or will we get 5.5.18 any time soon?
Looking forward to 5.5.18 and 5.4.34 fixing this bug as it basically breaks encrypted (SSL) communication to a MySQL server. Thanks.
Hi any news on a live fix for this? Is 5.5.18 any time soon?
What is keeping you to roll back to 5.5.16?
5.5.17 was not a security release.
"What is keeping you to roll back to 5.5.16?"
This is the behaviour, that makes one change from php to other languages.
In the future, please test your software at least basically before deploying it widely, thanks!
So I am not allowed the other bug fixes on 5.5.17 is that what you are saying?
I have not put this into production but I would really like to.
There are people who are keen on a timely bugfix (this is absolutely ok) and there are people who prefer name calling over contributing (which surprisingly  doesn't encourage enthusiasm).
> So I am not allowed the other bug fixes on 5.5.17 is that what you are saying?
Just remember for a minute that each release takes ton of donated time from people willing to contribute to the project, all you're contributing by spamming this bug report is noise.
You know where to get the source code, if you ever feel _one_ bug is a show stopper, feel free to grab the tag from git, revert the offending commit(s) and compile your own package so you _can_  benefit from all of the other bug fixes.
But since you've waited so long without doing that, you could just go and grab https://github.com/php/php-src/tree/PHP-5.5.18 and build that instead.
5.5.18 (and 5.4.34) should be released fixing this issue.
Brilliant thank you very much tyrael. Very much appreciated.
Just to clear up a few things I was really not trying to annoy anyone here. I was however feeling very frustrated that no one was replying to anybodies questions about when this fix would be public. Hence why I felt I needed to "spam" the bug report in order to get any sort of answers from any one.
Again I would like to say a big thank you for getting 5.5.18 and 5.4.34  released and I would like to apologise if my "spamming" came across in any way rude or unhelpful.
5.5.18 and 5.4.34 planned to be released on this thursday.
btw. if anybody feels that there a bug is not getting enough attention, feel free to drop an email to the internals@ mailing list or poke the RMs for the affected version(for 5.4 it is Stas, for 5.5 that is Julien and for issues with 5.6 you should contact me).
usually that helps more than posting some passive-aggressive/rude comments to the bugreport(not pointing fingers, but that is a common thing when reporters feel ignored).
Please post a new report if similar behavior is observed going forward (it shouldn't be).