Bug 32850 – asterisk (*) is not working as wildcard character for umcOperationHosts

Bug 32850 - asterisk (*) is not working as wildcard character for umcOperationHosts


Summary:	asterisk (*) is not working as wildcard character for umcOperationHosts

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.1-1-errata
Assigned To:	Alexander Kläser
QA Contact:	Florian Best

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-10-11 16:39 CEST by Daniel Orrego
Modified:	2013-10-28 14:57 CET (History)
CC List:	4 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):
Max CVSS v3 score:

Attachments
Possible patch (untested) (586 bytes, patch) 2013-10-14 10:24 CEST, Alexander Kläser	Details \| Diff
ACL testscript adaption (418 bytes, text/plain) 2013-10-15 14:49 CEST, Florian Best	Details
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 Daniel Orrego

2013-10-11 16:39:49 CEST

Wildcards on hostnames are not working anymore (LDAP ACL policies are not effective anymore)

[LDAP base]->univention->UMC->operations
rick click, Edit -> Custom

My tests on the 'UMC hosts' field:

de0711s00007 OK Works

de0711* DON'T (used to work)

de0711s0000* DON'T
de0711s0000? DON'T
de0711s00007.co.gc-gruppe.net DON'T (?!)
10.200* DON'T
10.200.30.* DON'T
10.200.30.217 DON'T

Some how it stopped working after an Update (Errata177 ?)

Comment 1 Ingo Steuwer

2013-10-11 17:02:00 CEST

reported by 2013041721001101

Comment 2 Alexander Kläser

2013-10-14 10:24:24 CEST

Created attachment 5517 [details]
Possible patch (untested)

This problem could be triggered through optimization work from Bug 28059. As LDAP lookups had been removed, the wildcard seems not to be evaluated anymore. I attached a patch which could solve the problem (not tested, though).

Comment 3 Daniel Orrego

2013-10-14 13:11:00 CEST

Thanks Alex. I tested the patch and the wildcard works again.

How can we get a bug fix of this?

Comment 4 Florian Best

2013-10-15 14:49:23 CEST

Created attachment 5519 [details]
ACL testscript adaption

Comment 5 Alexander Kläser

2013-10-15 17:57:17 CEST

Fixed. Adjusted changelog for UCS 3.2.

YAML file: 2013-10-15-univention-management-console.yaml


 univention-management-console (5.0.62-8) unstable; urgency=low
 .
   * Bug #32850: allow host matching with wildcards for UMC ACLs


 univention-management-console (6.0.17-1) unstable; urgency=low
 .
   * Bug #32850: allow host matching with wildcards for UMC ACLs

Comment 6 Florian Best

2013-10-23 09:06:58 CEST

The fix is OK.

I would adapt the YAML entry to "The wildcard evaluation of »hostnames in« UMC ACLs has been re-enabled."

Comment 7 Florian Best

2013-10-23 09:08:46 CEST

(In reply to Florian Best from comment #6)
> The fix is OK.
> 
> I would adapt the YAML entry to "The wildcard evaluation of »hostnames in«
> UMC ACLs has been re-enabled."
I adapted the YAML file.

→ VERIFIED

Comment 8 Janek Walkenhorst

2013-10-28 14:57:57 CET

http://errata.univention.de/ucs/3.1/191.html