mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1454] mutt crashes when using t-prot #977
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#977
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 @Boruch-Baum on GitHub (Aug 11, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1454
For firejail version 0.9.48 in debian:
mutt is an email-client that allows for great extensibility which isn't accounted for in the default firejail profiles. In my case, I encountered this because I use an add-on package called 't-prot' which is a message display filter built around a perl script. Commenting out the line
include /etc/firejail/disable-devel.incfrom the default mutt profile fixed the crash. My guess is that the reason is that the include file was blacklisting the perl shell.Because mutt is designed to be extended by any kind pf plugin, and because package
t-protis used by many mutt users, maybe the project should address this for the default mutt profile.As a more general matter, if I've correctly understood the problem:
1] This will be an issue for other blacklisted shells eg. ruby, python
2] Maybe the
disable-devel.incfile should be divided in two in order to account for run-time shell interpreters like perl. Another solution might be to keep thedisable-devel.incunchanged, but create a second include file to whitelist run-time shell interpreters.