Bug 32574 – access to dn.regex ACLs must not be $$ terminated.

Bug 32574 - access to dn.regex ACLs must not be $$ terminated.


Summary:	access to dn.regex ACLs must not be $$ terminated.

Status:	REOPENED

Product:	UCS@school
Classification:	Unclassified
Component:	LDAP
Version:	UCS@school 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:	interim-3

Depends on:	29421
Blocks:
	Show dependency tree / graph

Reported:	2013-09-12 13:54 CEST by Arvid Requate
Modified:	2019-02-05 22:11 CET (History)
CC List:	3 users (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):	Troubleshooting
Max CVSS v3 score:

Flags:	best: Patch_Available+

Attachments
syntax-fix_univention-ldap-acls.patch (4.98 KB, patch) 2013-09-12 13:54 CEST, Arvid Requate	Details \| Diff
syntax-fix_ucs-school-ldap-acls-master.patch (16.92 KB, patch) 2013-09-12 13:55 CEST, Arvid Requate	Details \| Diff
View All 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 Arvid Requate

2013-09-12 13:54:28 CEST

Created attachment 5427 [details]
syntax-fix_univention-ldap-acls.patch

I guess during working on Bug 29421 I violated a rule in the slapd.access manpage:

ACLs <what> statements with regex rules like
  access to dn.regex=
must not be $$ terminated. Only the following "by dn.regex" need this.

Patch attached.

Comment 1 Arvid Requate

2013-09-12 13:55:06 CEST

Created attachment 5428 [details]
syntax-fix_ucs-school-ldap-acls-master.patch

And for UCS@school

Comment 2 Arvid Requate

2013-10-16 17:42:53 CEST

The first patch has already been applied while fixing Bug #31305. So the remaining issue is UCS@school related.

Comment 3 Sönke Schwardt-Krummrich

2019-02-05 21:27:17 CET

This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x 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.