Bug 676604 - Instance creation wrongly updates the group permissions of /var/run/dirsrv , though the instance creation fails
Summary: Instance creation wrongly updates the group permissions of /var/run/dirsrv , ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: 389
Classification: Retired
Component: Install/Uninstall
Version: 1.3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nathan Kinder
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: 512820 690319
TreeView+ depends on / blocked
 
Reported: 2011-02-10 11:50 UTC by Sankar Ramalingam
Modified: 2015-11-19 19:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-19 19:50:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Sankar Ramalingam 2011-02-10 11:50:17 UTC
Description of problem: Creation of an instance as a different group than the existing instance group, breaks the existing instances.


Version-Release number of selected component (if applicable): 389-ds-base

How to reproduce:

1. Install 389-ds-base/ds8.2.4 build.
2. Create a shared group and few users for the same group.
      groupadd group1
      useradd -g group1 user1             - inst1
      useradd -g group1 user2             - inst2
      useradd -g group1 user3             - inst3
3. Create three instances using these group/user names as inst1, inst2 and inst3.
4. Check the file permissions for /var/run/dirsrv - user1/group1
5. Create a group called - group2: groupadd group2
6. Create an user(user4) and add it to group2: useradd -g group2 user4
7. Create an instance(inst4) using user as user4 and group as group2.
8. Instance creation succeeds for inst4
9. Check the file permissions for /var/run/dirsrv - user1/group2

10. The group permission keeps changing based on the new instance created.

Actual results:
Due to the change in the file(group) permissions, instances inst2 and inst3 fails to start.

Expected results:

DS should not allow the user to create an instance as an unprivileged DS group.
Group permission for this directory should not be altered.

Comment 1 Martin Kosek 2012-01-04 13:28:15 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/64

Comment 3 Noriko Hosoi 2015-11-19 19:50:13 UTC
Closing this bug since we moved to the ticket system:
https://fedorahosted.org/389/ticket/64


Note You need to log in before you can comment on or make changes to this bug.