mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1636] Make Firejail available through composer by adding composer.json file (in all branches) #1099
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1099
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nuxwin on GitHub (Nov 7, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1636
@netblue30
Good morning,
One of our plugin make uses of your Firejail SUID program to create jailed environments. Because our plugin provides several jail builders (makejail, firejail...), we do not want source your program inside our plugin archive directly. Instead, our plugin make use of the PHP dependency manager (composer) to grab the Firejail package when it is needed:
For now, we've forked your repository and added the composer.json file to make your program available through packagist.org. However, it could be better to have the composer.json file hosted in upstream repository, that is, in your own repository. Of course, some could arg that the PHP dependency manager is for PHP dependencies only but in fact, it can be used for many purpose, hence our own usage.
Could it be possible?
Thank you.
See:
@reinerh commented on GitHub (Nov 7, 2017):
Why don't you just install firejail via the package manager provided by your distribution?
Is it possible to add this file also in a subdirectory in platform/ where packaging-related files for other package management systems are located?
Btw packagist.org asks for very fishy workflows on their frontpage:
@nuxwin commented on GitHub (Nov 8, 2017):
@reinerh
https://github.com/i-MSCP/imscp/blob/1.5.x/engine/PerlLib/iMSCP/Composer.pm#L147
@netblue30 commented on GitHub (Nov 9, 2017):
The biggest problem you have is firejail mainline branch is unstable. Most of the time it is a war zone. I would suggest in https://github.com/imscp-packages/firejail you bring in the latest release. Example:
The latest is 0.9.50.
Another option is to use the LTS branch: https://github.com/netblue30/firejail/tree/0.9.38-LTS
This branch is always stable, we make sure we test everything before checking in fixes - only fixes are going in, no new developments. We can also add your composer.json file on this branch if you send a pull request.
@nuxwin commented on GitHub (Nov 9, 2017):
@netblue30
You're totally right. Problem is that I cannot add earlier releases because the composer.json file was not present... So here, I've tagged current state of the 0.9.50-bugfixes branch as alpha release (0.9.50.1). But anyway, with that version, I'm encountering problems with the chroot feature (some files missing inside the /var/run/firejail/mnt directory and also my resolv.conf being rejected by firejail...) I need investigate a bit more before creating new issues here ;)
I stay you informed.
@netblue30 commented on GitHub (Nov 10, 2017):
Not a problem, I can port
ac0d75f943on 0.9.50-bugfixes if you need it. We keep this branch around mainly for reference and big problems fixed on mainline.When you build your chroot don't bother with resolv.conf. A simple empty file (touch chrootdir/etc/resolv.conf) will do it. Firejail will replace it with whatever you have in /etc/resolv.conf on the server in that moment.
@chiraag-nataraj commented on GitHub (Sep 30, 2018):
The last commit in that repository was on Nov 13, 2017. I'm going to close this for now, since it seems like we're not going to add composer.json. If someone wants to re-open (that is, if I misunderstood the thread and adding this is still on the table), feel free to do so.