Page MenuHomePhabricator

test and deploy payments on Debian Stretch/PHP7.0
Closed, ResolvedPublic

Description

The plan is to reimage an unpooled payments server (either 1004 or a codfw hosts) and use that to live-test with internal test traffic, to validate payments-wiki with PHP 7.0 etc.

Event Timeline

Jgreen renamed this task from test payments-wiki on Stretch/PHP7.0 to test and deploy payments on Stretch/PHP7.0.Aug 20 2018, 4:11 PM
Jgreen renamed this task from test and deploy payments on Stretch/PHP7.0 to test and deploy payments on Debian Stretch/PHP7.0.
Jgreen updated the task description. (Show Details)

We've decided to use payments1004 for testing, noting that it also hosts scripts for some manual batch payment processing stuff, and we're ok with testing those on PHP 7.0 at the same time.

@Ejegg after adding missing php-mbstring I was able to to make a $3 credit card donation through the rebuilt payments1004, so it's ready for more testing.

Possibly-significant version changes from Jessie to Stretch:

mariadb 10.0.37 -> 10.1.37
memcached 1.4.21 -> 1.4.33
php5-memcache 3.0.8 -> 3.0.9
php5-memcached 2.2.0 -> 3.0.1

Looks like the php-memcache upgrades shouldn't matter. Our filters are using memcache via Mediawiki's BagOStuff interface, which has its own PHP class to talk directly to the daemon without using either of the PHP libs.

OK, I'm seeing the loading errors in Chrome now. It's more images inlined into CSS by ResourceLoader as data: urls. This time, it's from core MediaWiki.

So we can either pile some patches on top of Mediawiki Core to unminify them, or allow data: urls in image-src. I'm firmly in favor of allowing data: in image-src. It seems an especially improbable attack vector for a locked-down wiki like payments, and in any case is no less secure than the current zero-CSP situation.

OK, I'm seeing the loading errors in Chrome now. It's more images inlined into CSS by ResourceLoader as data: urls. This time, it's from core MediaWiki.

So we can either pile some patches on top of Mediawiki Core to unminify them, or allow data: urls in image-src. I'm firmly in favor of allowing data: in image-src. It seems an especially improbable attack vector for a locked-down wiki like payments, and in any case is no less secure than the current zero-CSP situation.

Let's try to connect with other folks working on this as related to Mediawiki. It seems to be largely an unsolved issue considering other Phabricator tasks (T28508, T135963), and maybe our use-case would be informative.

Ejegg closed subtask Restricted Task as Resolved.Feb 5 2019, 9:11 PM

We've worked out all the identified upgrade-related issues with the test cluster, and are ready to upgrade the main cluster.