ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008881ClearOSapp-configuration-backup - Configuration Backuppublic2016-05-25 11:472016-05-26 13:30
Reporterbchambers 
Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version7.2.0 
Target VersionFixed in Version 
Summary0008881: LDAP permissions issue
DescriptionOn a v6 to v7 restore, slapd daemon wouldn't start.

Permissions looked like this:

[root@gateway openldap]# ls -l
total 24
drwxr-xr-x. 2 1000 1000 35 May 26 01:38 cacerts
drwxr-xr-x. 2 root root 77 May 26 2016 certs
-rw-r--r--. 1 root root 121 Dec 4 08:41 check_password.conf
-rw-r--r-- 1 root root 559 May 26 00:55 clearos_anonymous.conf
-rw-r--r-- 1 root root 647 May 26 00:55 clearos_password_protected.conf
-rw-r--r-- 1 1000 1000 182 May 11 2013 ldap.conf
drwxr-xr-x. 2 root root 4096 May 26 00:55 schema
-rw-r----- 1 1000 1000 3792 Aug 23 2013 slapd.conf

As soon as I chown root * and chgrp ldap slapd.conf, slapd started up fine.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0003301)
user2
2016-05-26 09:22

The UID of 1000 looks suspicious. It looks like the backup file was unpacked on a non-ClearOS system, and then packed back up again. The unknown "ldap" user during unpacking was then mapped to the UID 1000 (i.e. the first account on most Linux systems).
(0003311)
bchambers (administrator)
2016-05-26 09:31

>> It looks like the backup file was unpacked

Haha...caught red-handed...that's exactly what I did in order to remove some files I didn't want overwritten.

Could this have been avoided? (eg. is unpacking/packing possible?).

- Issue History
Date Modified Username Field Change
2016-05-25 11:47 bchambers New Issue
2016-05-26 09:22 user2 Note Added: 0003301
2016-05-26 09:23 user2 Status new => feedback
2016-05-26 09:31 bchambers Note Added: 0003311
2016-05-26 09:31 bchambers Status feedback => new
2016-05-26 13:30 bchambers Status new => closed
2016-05-26 13:30 bchambers Resolution open => no change required