Bug 56056 - Import naming scheme can lead into not working usernames (in Windows machines) f.e. con.*
Summary: Import naming scheme can lead into not working usernames (in Windows machines...
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Users
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL: https://git.knut.univention.de/univen...
Keywords:
Depends on: 53519 56152
Blocks:
  Show dependency tree / graph
 
Reported: 2023-05-11 16:20 CEST by Florian Best
Modified: 2023-06-16 12:15 CEST (History)
8 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021061521000105
Bug group (optional):
Customer ID:
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 Florian Best univentionstaff 2023-05-11 16:20:38 CEST 
We should disallow the conflicting usernames in UDM.

+++ This bug was initially created as a clone of Bug #53519 +++

In Windows, there are some names that are reserved for special use (https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file).
With our freely definable scheme in our import, we allow user names that can lead to such names. If this happens, no check takes place and diffuse errors occur under Windows.
Most reserved names should be rare to non-existent, with con.* I can think of several names that can lead to such user names; as in the attached ticket.