Bug 34283 - DN substring checks in scholldap.py are done case sensitive
DN substring checks in scholldap.py are done case sensitive
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Ucsschool-lib
UCS@school 4.4
Other Linux
: P5 normal (vote)
: UCS@school 4.1.x
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-07 11:29 CET by Florian Best
Modified: 2023-06-23 13:15 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
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): Cleanup
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2014-03-07 11:29:20 CET
A DN is case insensitive. Various functions in ucsschool-lib can fail.

For example:
486 »   def isStudent(self, userDN):
487 »   »   return userDN.endswith(self.students)
Comment 1 Philipp Hahn univentionstaff 2014-03-10 09:05:04 CET
(In reply to Florian Best from comment #0)
> A DN is case insensitive. Various functions in ucsschool-lib can fail.

No. this is generally not true:
A DN is a sequence of RDNs. An RDN is a sequence of Attribute-value 
pairs. Each attribute has its own schema definition with its own 
governing rules. Some attributes are case-sensitive, some are not. As 
such, a complete DN may have components that are case-sensitive as well 
as case-insensitive.
Comment 2 Florian Best univentionstaff 2016-09-21 18:24:51 CEST
We should use the new univention.uldap.access.compare_dn() function instead.
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:16:08 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
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.
Comment 4 Jan-Luca Kiok univentionstaff 2023-06-23 13:15:27 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed.

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