View Issue Details

IDProjectCategoryView StatusLast Update
0011471Talerdeployment and operationspublic2026-06-04 14:42
Reportervecirex Assigned Tovecirex Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityurgentSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0011471: mytops: test phone numbers prod config accepts
DescriptionApparently phone no. for fixed lines still get accepted by account creation... shouldn't be allowed by merchant's regex for phone no.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

vecirex

2026-06-04 14:04

administrator   ~0028780

Last edited: 2026-06-04 14:09

Ehm, yeah, PHONE_REGEX is too liberal and just accepts any kind of number which looks like a Swiss no., purely formwise -- my fault closing 0011105 like this:

cat /etc/taler-merchant/merchant-overrides.conf | grep -A 1 11105
# cf. #​11105, enable regex checks in phone no.
PHONE_REGEX = ^\+41 ?[1-9][0-9]( ?[0-9]{3})( ?[0-9]{2})( ?[0-9]{2})$


Fix underway...

vecirex

2026-06-04 14:31

administrator   ~0028781

Last edited: 2026-06-04 14:32

Regex tested to work in stage, only allowed mobile phone numbers starting w/ +417X, X from [5,9]:

# cf. #​11105, enable regex checks in phone no.
# cf. #​11471, revised and fixed
PHONE_REGEX = ^\+41 ?7[5-9]( ?[0-9]{3})( ?[0-9]{2})( ?[0-9]{2})$

vecirex

2026-06-04 14:42

administrator   ~0028782

Fixed also in prod.

Issue History

Date ModifiedUsernameFieldChange
2026-06-04 13:57vecirexNew Issue
2026-06-04 13:58vecirexAssigned To => vecirex
2026-06-04 13:58vecirexStatusnew => assigned
2026-06-04 14:04vecirexNote Added: 0028780
2026-06-04 14:09vecirexNote Edited: 0028780
2026-06-04 14:31vecirexNote Added: 0028781
2026-06-04 14:32vecirexNote Edited: 0028781
2026-06-04 14:42vecirexNote Added: 0028782
2026-06-04 14:42vecirexStatusassigned => closed
2026-06-04 14:42vecirexResolutionopen => fixed