Issue #390
closed
pulp-dev.sh doesn't apply the same permissions to /etc/pki/pulp/ as the RPM
Description
The RPM installs with these permissions:
$ ls lah /etc/pki/pulp/
total 28K
drwxr-xr-x. 5 root root 4.0K Dec 23 12:48 .
drwxr-xr-x. 14 root root 4.0K Dec 20 17:01 ..
-rw-r----. 1 root apache 1.1K Dec 23 12:48 ca.crt
rw-r----. 1 root apache 1.7K Dec 23 12:48 ca.key
drwxr-xr-x. 2 root root 4.0K Dec 20 16:47 consumer
drwxr-xr-x. 2 apache apache 4.0K Dec 23 13:29 content
drwxr-xr-x. 2 root root 4.0K Dec 23 12:48 nodes
The pulp-dev.sh script appears to do this:
drwxr-xr-x. 5 apache apache 4096 Jan 3 10:26 .
drwxr-xr-x. 10 root root 4096 Aug 8 11:00 ..
rw-r---- 1 root apache 1062 Jan 3 10:26 ca.crt
rw-r---- 1 root apache 1675 Jan 3 10:26 ca.key
drwxr-xr-x 2 root root 4096 Jan 3 10:26 consumer
drwxr-xr-x 2 root root 4096 Jan 3 10:26 content
drwxr-xr-x 2 root root 4096 Jan 3 10:26 nodes
+ This bug was cloned from Bugzilla Bug #1048297 +
I've made a pull request to address our immediate problem. However, it still won't make the /etc/pki/pulp folder be the same as the RPM, because our unit tests read the ca.crt and ca.key files for some unknown reason. Until those tests are fixed, we can't really finish this bug, but we can lower its priority once this pull request is merged.
https://github.com/pulp/pulp/pull/753
+ This comment was cloned from Bugzilla #1048297 comment 1 +
I have merged the pull request to address the immediate test failures.
The pulp-dev.sh script continues to diverge from the RPMs in the permissions it sets on the /etc/pki/pulp folder, so I am leaving this bug open until we can resolve that issue. Unfortunately, our unit tests read the CA certificate and key. We can't fix this bug until we refactor the tests.
+ This comment was cloned from Bugzilla #1048297 comment 2 +
- Severity changed from Medium to 2. Medium
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Also available in: Atom
PDF
.