New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[firejail] Updated upstream to 0.9.72 Fixes JB#59121 #17
Conversation
rpm/0001-Preserve-process-effective-group-for-privileged-grou.patch
Outdated
Show resolved
Hide resolved
4a8b4ae
to
98ac8d9
Compare
|
dsuni ***@***.***> writes:
@dsuni commented on this pull request.
> @@ -48,6 +50,7 @@ Requires: %{name} = %{version}-%{release}
%make_install
rm -rf %{buildroot}%{_datadir}/bash-completion
rm -rf %{buildroot}%{_datadir}/zsh/site-functions/_firejail
+install %{buildroot}/etc/firejail/firecfg.config %{buildroot}/usr/lib64/firejail/
Not sure how relevant the file is to our usecase, but at least src/firecfg/main.c still contains code for parsing this file...
Not exactly sure but it could be that only the file in /usr/lib is
needed and the file in /etc is optional in case the settings needs to be
adjusted by the user of the device (user as in the system administrator on a regular
desktop system).
In our case we skip the file in etc in this case.
|
98ac8d9
to
badeddd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Went through the privileged data patch and wrote some comments about the things I'd change. I think the simpler patches are good as they are. The remaining two big patches are such messy (as changes to patch files can be sometimes), that I'd need to have a separate look at them.
rpm/0002-Implement-Sailfish-OS-specific-privileged-data-optio.patch
Outdated
Show resolved
Hide resolved
rpm/0002-Implement-Sailfish-OS-specific-privileged-data-optio.patch
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that INVALID_GID return value and adding that FIXME comment about those new groups would be something to do still. (The comment being something like // FIXME: Add missing debian specific groups, see JB#xxxxx.) I checked the rest of the patches and I think they are fine.
|
Tomi Leppänen ***@***.***> writes:
@Tomin1 commented on this pull request.
I think that `INVALID_GID` return value and adding that FIXME comment about those new groups would be something to do still. (The comment being something like `// FIXME: Add missing debian specific groups, see JB#xxxxx`.) I checked the rest of the patches and I think they are fine.
We don't use the Debian Groups, the other groups used here should be
replaced by systemd uaccess permissions.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use the Debian Groups, the other groups used here should be
replaced by systemd uaccess permissions.
I don't really care if the comment says, that is it about debian or that we should use some other mechanism, as long as it makes clear that we dropped code that is not relevant for us and we have it documented somewhere. So in short, some comment, some bug reference and I'm happy.
Something else strange that I noticed: This is built on top of commit 48a57d6 and not master (5b4cdb3). There is not real difference between those as it's just a merge commit that it's missing, so it can be just rebased there without changes. Also those new commits should be squashed of course.
a8552a5
to
6704180
Compare
|
This is still on top of 48a57d6 and not master / 5b4cdb3 / 0.9.66+git3. Otherwise I think it's good. |
6704180
to
e12d153
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
No description provided.