Skip to content
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

Directory read-only even after noblacklist/whitelist #3173

Closed
q3cpma opened this issue Jan 20, 2020 · 9 comments
Closed

Directory read-only even after noblacklist/whitelist #3173

q3cpma opened this issue Jan 20, 2020 · 9 comments
Labels
question_old (Deprecated; use "needinfo" or "question" instead) Further information is requested

Comments

@q3cpma
Copy link

q3cpma commented Jan 20, 2020

Hello,

I'm trying to use emacs in qutebrowser, and to that end, I call qutebrowser that way:

exec firejail \
    --noblacklist=~/.config/mpv \
    --noblacklist=~/.emacs.d \
    --whitelist=~/.config/mpv \
    --whitelist=~/.emacs.d \
    --nodbus \
    qutebrowser "$@"

Everything works well until I try to close emacs, where it tells me that ~/.emacs.d/history is read-only. Using an eshell, I can't even touch a file inside ~/.emacs.d (I get /usr/bin/touch: cannot touch 'a': Read-only file system), but I can in my HOME. I tried adding a --read-write=~/.emacs.d to no avail.
What is even stranger is that ~/.config/mpv isn't RO.

This is on Gentoo with firejail 0.9.62

@reinerh
Copy link
Collaborator

reinerh commented Jan 20, 2020

The qutebrowser profile includes disable-common.inc, which has this line:

read-only ${HOME}/.emacs.d

Does it work if you call it with --ignore='read-only ${HOME}/.emacs.d'?

@q3cpma
Copy link
Author

q3cpma commented Jan 20, 2020 via email

@reinerh
Copy link
Collaborator

reinerh commented Jan 20, 2020

I can imagine the number of users of qutebrowser AND emacs AND firejail is quite small. :-)

@q3cpma
Copy link
Author

q3cpma commented Jan 20, 2020 via email

@reinerh
Copy link
Collaborator

reinerh commented Jan 20, 2020

Adding ignore read-only ${HOME}/.emacs.d into the profile does not work?

@rusty-snake
Copy link
Collaborator

Adding ignore read-only ${HOME}/.emacs.d before read-only ${HOME}/.emacs.d or read-write ${HOME}/.emacs.d after read-only ${HOME}/.emacs.d in the profile works.

To get this ordering on the command line you need to use --profile:

firejail '--noblacklist=${HOME}/.emacs.d' --profile=qutebrowser '--read-write=${HOME}/.emacs.d' qutebrowser

@q3cpma
Copy link
Author

q3cpma commented Jan 20, 2020 via email

@rusty-snake
Copy link
Collaborator

Maybe emacs supports it to places the history file in a temp-dir such as /tmp (with private-tmp) or ~/.cache (with private-cache).

@rusty-snake
Copy link
Collaborator

I'm closing here due to inactivity, please fell free to reopen if you have more questions.

@rusty-snake rusty-snake added the question_old (Deprecated; use "needinfo" or "question" instead) Further information is requested label Feb 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question_old (Deprecated; use "needinfo" or "question" instead) Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants