#50940 Permissions of some shipped directories may change over time
Closed: wontfix by mhonek. Opened by mhonek.

Issue Description

Some utilities (e.g. setup-ds.pl) alter permissions of some folders shipped by default to be more permissive. This is discoverable by running rpm -V 389-ds-base after using these. As the discrepancy between expected and actual permissions would indicate potential security issue, these should be fixed at install time.

/etc/dirsrv
SHOULD BE:  644
ACTUALLY IS:  775
---------------------------
/etc/dirsrv/config
SHOULD BE:  644
ACTUALLY IS:  755
---------------------------
/etc/dirsrv/schema
SHOULD BE:  644
ACTUALLY IS:  755
---------------------------
/var/lib/dirsrv
SHOULD BE:  755
ACTUALLY IS:  775
---------------------------
/var/lock/dirsrv
SHOULD BE:  755
ACTUALLY IS:  770
---------------------------

Package Version and Platform

1.3.x, 1.4.x


Metadata Update from @mhonek:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1700987

Merged PR #50941 as 811db9020a0ea737bb91281289903d350e862281 into branch 389-ds-base-1.3.10.

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.1 (was: 0.0 NEEDS_TRIAGE)

Commit 26c77a4b relates to this ticket

Commit 26c77a4 relates to this ticket

b97a2c1c5..e1e4ef524 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
4cc6a99cf..10c85d687 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

Metadata Update from @mhonek:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3993

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata
Related Pull Requests