diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-04-11 06:58:44 +0200 |
---|---|---|
committer | Neels Hofmeyr <neels@hofmeyr.de> | 2019-04-12 01:00:16 +0200 |
commit | b480b74192a7c00c4ea077286b921b96e42efabc (patch) | |
tree | 89829b89409dab7121d1dce89c0c455e7879cfa9 /tests/logging/logging_test.err | |
parent | ecef7ec3c36805e70e3da88ea694aeaf526e751d (diff) |
add identifier sanitation for setting FSM instance ids
We often compose FSM instance IDs from context information, for example placing
an MSISDN string or IP:port information in the FSM instance id, using
osmo_fsm_inst_update_id_f(). This fails if any characters are contained that
don't pass osmo_identifier_valid(). Hence it is the task of the caller to make
sure only characters allowed in an FSM id are applied.
Provide API to trivially allow this by replacing illegal chars:
- osmo_identifier_sanitize_buf(), with access to the same set of illegal
characters defined in utils.c,
- osmo_fsm_inst_update_id_f_sanitize() implicitly replaces non-identifier
chars.
This makes it easy to add strings like '192.168.0.1:2342' or '+4987654321' to
an FSM instance id, without adding string mangling to each place that sets an
id; e.g. replacing with '-' to yield '192-168-0-1:2342' or '-4987654321'.
Change-Id: Ia40a6f3b2243c95fe428a080b938e11d8ab771a7
Diffstat (limited to 'tests/logging/logging_test.err')
0 files changed, 0 insertions, 0 deletions