Mention filesystem fixes for 50-qubesbuilder.policy#109
Closed
aronowski wants to merge 1 commit into
Closed
Conversation
README.md had no information regarding the filesystem owner, group and permissions for the 50-qubesbuilder.policy file to be copied. Therefore, the procedure described resulted in the file being owned by `user:user` and having permission bits `644`, what resulted in qrexec-policy-daemon being unable to find any matching rule, e.g.: ``` $ journalctl --follow -u qubes-qrexec-policy-daemon [...] May 02 03:52:42 dom0 qrexec-policy-daemon[1526]: qrexec: admin.vm.CreateDisposable: work-qubesos -> qubes-builder-dvm: denied: no matching rule found ``` This fix adds the mentions, how to adjust the filesystem properties, so the policy works as intended. Signed-off-by: Kamil Aronowski <kamil.aronowski@yahoo.com>
Member
This is okay
qrexec-policy-daemon definitely can read such file. In fact, it's running as root, so it can read any file. The issue you hit must be somewhere else... |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #109 +/- ##
=======================================
Coverage 77.20% 77.20%
=======================================
Files 46 46
Lines 5002 5002
=======================================
Hits 3862 3862
Misses 1140 1140 ☔ View full report in Codecov by Sentry. |
Author
|
On 2024.05.02 06:11:08, Marek Marczykowski-Górecki wrote:
The issue you hit must be somewhere else...
I accounted for the fact that my production setup may already have some tweaks
that interfere, so I set up a fresh installation of Qubes OS 4.2.1 to confirm
that this just happens.
While there may be something else still interfering in a fresh system
installation, I think it may me worthwhile to keep this information as a
workaround until that's resolved. A separate issue to track that interference
may also come in handy - once I post it, I'll link to this pull request in it.
… --
Reply to this email directly or view it on GitHub:
#109 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Member
|
I'm pretty sure the issue you observe will be fixed with QubesOS/qubes-core-qrexec#170 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
README.md had no information regarding the filesystem owner, group and permissions for the 50-qubesbuilder.policy file to be copied. Therefore, the procedure described resulted in the file being owned by
user:userand having permission bits644, what resulted in qrexec-policy-daemon being unable to find any matching rule, e.g.:This fix adds the mentions, how to adjust the filesystem properties, so the policy works as intended.