[GH-ISSUE #1309] Pushing changes/limitations upstream #892

New issue

Closed

opened 2026-05-05 07:04:39 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:04:39 -06:00

Owner

Originally created by @breznak on GitHub (May 25, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1309

I'd like to ask about your experience with pushing the improvements (esp. dropped capabilities) from the profiles here into the upstream packages?

Ideally, there would be no need for this (awesome) tool.

I suppose even binary packages can be (tried) contacted
and for open-source, opening an issue or even a PR with (some) enhancements could certainly be possible.

Originally created by @breznak on GitHub (May 25, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1309 I'd like to ask about your experience with pushing the improvements (esp. dropped capabilities) from the profiles here into the upstream packages? Ideally, there would be no need for this (awesome) tool. - I suppose even binary packages can be (tried) contacted - and for open-source, opening an issue or even a PR with (some) enhancements could certainly be possible.

gitea-mirror

2026-05-05 07:04:39 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 07:04:47 -06:00

Author

Owner

@reinerh commented on GitHub (May 25, 2017):

Pushing security improvements to upstream projects is of course a good idea.
But it's not possible to put every feature offered by firejail into individual projects, especially as some functionalities require root permissions.

@reinerh commented on GitHub (May 25, 2017): Pushing security improvements to upstream projects is of course a good idea. But it's not possible to put every feature offered by firejail into individual projects, especially as some functionalities require root permissions.

gitea-mirror commented

2026-05-05 07:04:51 -06:00

Author

Owner

@SYN-cook commented on GitHub (May 26, 2017):

About experience: I had a conversation with KDE people regarding Baloo a while ago, and I was told that any work for implementing e.g. a seccomp filter is indeed very welcome. I actually would have done it myself, but I unfortunately don't speak C++.

My guess is: Especially if you are willing to contribute code and time, you will be welcome mostly everywhere.

@SYN-cook commented on GitHub (May 26, 2017): About experience: I had a conversation with KDE people regarding Baloo a while ago, and I was told that any work for implementing e.g. a seccomp filter is indeed very welcome. I actually would have done it myself, but I unfortunately don't speak C++. My guess is: Especially if you are willing to contribute code and time, you will be welcome mostly everywhere.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#892

No description provided.

Rows
Columns