Bug 40202 – univention-config-registry backend strips blanks

Bug 40202 - univention-config-registry backend strips blanks


Summary:	univention-config-registry backend strips blanks

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UCR
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	UCS 4.x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-12-09 10:20 CET by Philipp Hahn
Modified:	2019-01-03 07:19 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2015-12-09 10:20:58 CET

While it is possible to store a value consisting only of white space characters in UCR, they are returned as the empty string:

univention-config-registry/python/univention/config_registry/backend.py:330
330 »···»···»···key, value = line.split(': ', 1)
331 »···»···»···value = value.strip()                                                                               
332 »···»···»···if len(value) == 0:  # if variable was set without an value
333 »···»···»···»···value = ''

Please note, that the last two lines are completely useless.

Comment 1 Stefan Gohmann

2019-01-03 07:19:34 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.