mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3323] Can't open links from hexchat #2086
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#2086
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 @ibahnasy on GitHub (Apr 6, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3323
When running hexchat with firejail, it's not possible to launch links directly.
@rusty-snake commented on GitHub (Apr 6, 2020):
#1718
https://github.com/netblue30/firejail/issues/1770#issuecomment-364498100
@rusty-snake commented on GitHub (Apr 6, 2020):
@other_collaborator, we must document the "open links from foo does not work". Or we must answer it for the rest of our live.
#3308
#2228
#2047
#1955
#3311
#…
@ghost commented on GitHub (Apr 6, 2020):
@rusty-snake Very true. IMO the best we can do is to actually implement a
secureway for users to open links from foo in browsers, regardless of documentation. Something along the lines of what I tried to convey here. Although the stuff linked in that comment is outdated, I have been using a few very simple shell scripts and geckodriver to implement basic URL inter-sandbox communication with mozilla-based web browsers for a long time now. Recently I have improved these scripts toavoidhaving to rely onD-Busalltogether, in both the scripts and firejail profiles. A bit swamped at the moment to start a WIP PR for it, but reading your message here reminded me I must bite the bullet and go public soonish and see what the firejail community thinks about it...@rusty-snake commented on GitHub (Apr 7, 2020):
@glitsj16 with #3265 a
dbus-user.talk org.mozilla.firefox.*rule is enough.Problem1: profiles with
private-binProblem2: /usr/bin/firefox is a shell script in Ubuntu/Fedora/Arch/… and adding bash to private-bin relaxes the sandbox.
@ghost commented on GitHub (Apr 7, 2020):
@rusty-snake Yes, the new D-Bus filters definately improve the situation. The scripts I'm refering to are doing there job outside the sandbox, apllications inside are agnostic to their existence. A wrapper for /usr/bin/firefox intercepts calls to it and dispenses a drop file containing the URL request. Not much different than what the GNOME portal system is doing actually. The work done by @kris7t in this regard is the best thing happening for firejail in a long while! Nevertheless I wouldn't mind D-Bus succumbing to a corona infection, being the security nightmare it is 😀.
@rusty-snake commented on GitHub (May 6, 2020):
I'm closing here due to inactivity, please fell free to reopen if you have more questions.