Michal Čihař - Blog Archives for phpMyAdmin

Weekly phpMyAdmin contributions 2018-W02

Last week was equally spent on issues and infrastructure. There is quite serious regression in the 4.7.7 release which needs to be fixed (so far just the issue has been identified). In the same time our server is having hardware problems and we're preparing to migrate to new one (if everything goes well, the migration will be completed by the time you read this).

Handled issues:

Weekly phpMyAdmin contributions 2018-W01

First week of 2018 was a bit less intense on the code fixing side, but I've done some work on our infrastructure preparing for migration to the new server, which should be available as soon as Conservancy approves payments for it.

The new server will be located at Hetzner and you can check more details on the selection process in our wiki. The current server has been used for almost 10 years and is really showing it's age.

Handled issues:

Weekly phpMyAdmin contributions 2017-W50

Last week contributions were mostly focused on fixing bugs. It's a bit hard to pinpoint something out of these, but most of them were really old, but not easy to trigger.

For example there were some javascript errors which were not easily reproducible, but turned out to be affecting quite a lot of our users. It turned out to be affecting only some variants of TIMESTAMP fields, what none of the reports did mention.

I've also switched all our libraries to use ApiGen 4 for generating docs as ApiGen 5 is way slower and is looking for new maintainer in the same time.

Handled issues:

Weekly phpMyAdmin contributions 2017-W49

Last week was a bit calmer, the most visible part probably being release of the SQL parser with several fixes with improved SQL context handling.

Handled issues:

Weekly phpMyAdmin contributions 2017-W48

Looking at list of handled issues, last week was extremely productive. Many of that are issues where I've been working on them for long time and I've managed to complete them last week. For example the user preferences cleanup to store less things in cookies or common.inc.php cleanup.

I've also gone through open pull requests and merged the ones which made sense or were basically good to merge, but needed some cleanups.

There was also some fun with phpseclib 2.0.8 which was mistakenly released from master branch instead of 2.0, what lead to API breakage. Fortunately this was really just a mistake and 2.0.9 reverted these changes.

Handled issues:

Weekly phpMyAdmin contributions 2017-W47

Last week was mostly spent on improving two factor authentication support. It turned out that Firefox 57 behaves differently than Firefox 56 with U2F extension. Also it behaves differently than Chrome (which was broken as well by the way). Anyway all of these should work fine, but there still seem to be some issues with the two factor auth, but those will be certainly addressed in next weeks.

Handled issues:

Weekly phpMyAdmin contributions 2017-W46

Last week was equally spent on refactoring, bugfixing and infrastructure. We're looking for replacement our oldish server and it seems that rented server or virtual hosts seems to be best fit for us these days. Still there are quite some choices to consider.

I've done quite some development as well - I'm most happy with Util::linkOrButton refactoring which helped to cleanup the code quite a lot, but there were other fixes and improvements as well.

Handled issues:

Weekly phpMyAdmin contributions 2017-W44

Most of last week was spent on bringing U2F and 2FA to phpMyAdmin. Besides that it was really just minor bug fixing.

We've had one pull request for the 2FA already open, however it was not really in quality to be merged and the original author really didn't come back to address our concerns. I was thinking to start over from his work, but in the end I've decided to start from scratch and come with code which will make easier to implement additional second authentication factors in the future.

Anyway what is now there is support for HOTP/TOTP authentication (Google Authenticator and similar) and FIDO U2F hardware tokens. The latter has been tested with TREZOR, but should work with any compliant device.

phpMyAdmin with TREZOR

Handled issues: