• Arbitrations
• a20180622.1

• Case Number: a20180622.1
• Status: init
• Claimant: Wytze
• Respondent: CAcert

• initial Case Manager: BernhardFröhlich

• Case Manager: N.N.
• Arbitrator: N.N.
• Date of arbitration start: 201Y-MM-DD
• Date of ruling: 201Y-MM-DD
• Case closed: 201Y-MM-DD
• Complaint: Possible problems with recent new CAcert accounts
• Relief: TBD

Before: Arbitrator name arbitrator (A), Respondent: name respondent (R), Claimant: name claimant (C), Case: a20180622.1

History Log

• 2018-06-22 (issue.c.o): case [s20180622.38]
• 2018-11-06 (iCM): added to wiki, request for CM / A

• Link to Arbitration case a20180622.1 (Private Part), Access for (CM) + (A) only

EOT Private Part

Original Dispute

On 19 June 2018, a problem was found with the handling of umlauts in names
when creating a new account on the test server. A quick test confirmed
that the same problem occurred on the CAcert webdb production server.
After some searching, the problem was identified on 22 June 2018 as an
issue caused by an OS upgrade involving the change of a default in the
PHP5 settings. This was corrected immediately on production and test servers.

See report to cacert-systemlog mailinglist:

   https://lists.cacert.org/wws/arc/cacert-systemlog/2018-06/msg00002.html

and bug report on bugs.cacert.org:

   https://bugs.cacert.org/view.php?id=1441

We conclude that any new accounts created between 16 April 16 2018
(introduction of new PHP version in CAcert chroot environment on
production server) and 22 June 2018 (implementation of bug fix)
which contained non-latin characters may have been affected by this.
From the data in https://www.cacert.org/stats.php we estimate that
less than 2500 new accounts were created in this period.

Please investigate this case and declare whether we should investigate
all recently created accounts for anomalies from non-latin characters.

Regards,
-- wytze

Discovery

Elaboration

Ruling

Execution

Similiar Cases

• CategoryArbitration

• CategoryArbCaseSystemTasks