Bug 30205 – slapd.conf permission warning while updating ucs

Bug 30205 - slapd.conf permission warning while updating ucs


Summary:	slapd.conf permission warning while updating ucs

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-01-30 10:02 CET by Erik Damrose
Modified:	2019-01-03 07:15 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
updater.log with warning (deleted) 2013-01-30 10:02 CET, Erik Damrose	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 Erik Damrose

2013-01-30 10:02:01 CET

Created attachment 5018 [details]
updater.log with warning

I updated a fresh UCS install and got the following warning: 

...
Multifile: /etc/ldap/slapd.conf

WARNING!
Check file permissions!
...

# ls -l /etc/ldap/slapd.conf 
-rw-r--r-- 1 root root 13646 30. Jan 09:35 /etc/ldap/slapd.conf

updater.log attached

Comment 1 Janis Meybohm

2015-09-15 12:55:55 CEST

2015091521000157

The message is really annoying to customers as it suggests there is something to do.

Comment 2 Stefan Gohmann

2019-01-03 07:15:54 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

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