Bug 1297473
| Summary: | unprivileged users unable to use 'rpm-ostree status' | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Micah Abbott <miabbott> |
| Component: | rpm-ostree | Assignee: | Colin Walters <walters> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | jkrieger, mattdm, mbarnes, miabbott, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 17:47:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Micah Abbott
2016-01-11 15:39:43 UTC
This sounds like the regression in ostree that I fixed upstream last month: https://git.gnome.org/browse/ostree/commit/?id=1f1bfbf711221168f1a3fc6e18cde2929c0ac1d7 Which was an unintended side-effect of: https://bugzilla.gnome.org/show_bug.cgi?id=757611 But AFAICT, there hasn't been an upstream release since before that regression was introduced and fixed. The latest release was 2015.11 on Dec 4th, and Alex didn't commit those changes until Dec 14th. What's your ostree package version? Disregard my above comment. This is something else. Right now the rpm-ostree daemon uses a blanket security policy of letting only the root user call a method. That is, any method -- even harmless ones. We need to poke some holes in that. For this particular case, the client is merely calling Sysroot.GetOS() to find out what osname to use. Anyone should be allowed to do that. Above pull request got merged, so this should be fixed upstream now. Micah - can you take a peek and verify for us? :) Made use of 'ostree admin unlock' and tested this functionality with the new rpm-ostree-2016.1-2.fc23.x86_64 package. [cloud-user@micah-f23-ah-vm1 ~]$ id uid=1001(cloud-user) gid=1001(cloud-user) groups=1001(cloud-user) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [cloud-user@micah-f23-ah-vm1 ~]$ rpm-ostree --version rpm-ostree 2016.1 +compose [cloud-user@micah-f23-ah-vm1 ~]$ rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC * 2016-03-26 15:08:22 23.92 2f80c5d591 fedora-atomic fedora-atomic:fedora-atomic/f23/x86_64/testing/docker-host 2016-03-07 03:45:47 23.79 1a68c7b9c0 fedora-atomic fedora-atomic:fedora-atomic/f23/x86_64/docker-host This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |