Bug#983746: firejail: with --private=, an existing "bin" directory is read-only

2021-03-01 Thread Vincent Lefevre
On 2021-03-02 01:29:19 +0100, Reiner Herrmann wrote: > I've raised the question upstream what the intended behaviour of ${HOME} > is, whether is should apply to the private home as well or not. > I can imagine that one would also be interested in having ${HOME} rules > apply to the private

Bug#983746: firejail: with --private=, an existing "bin" directory is read-only

2021-03-01 Thread Reiner Herrmann
Control: forward -1 https://github.com/netblue30/firejail/issues/4026 Control: severity -1 normal Hi Vincent, On Tue, Mar 02, 2021 at 12:22:09AM +0100, Vincent Lefevre wrote: > This is misused in the case of a private home directory. This rule > should apply against the original home directory,

Bug#983746: firejail: with --private=, an existing "bin" directory is read-only

2021-03-01 Thread Vincent Lefevre
On 2021-03-01 19:25:22 +0100, Reiner Herrmann wrote: > Hi Vincent, > > On Mon, Mar 01, 2021 at 02:49:32AM +0100, Vincent Lefevre wrote: > > When using --private=, an existing "bin" directory in > > is read-only. This is silly: this means that one cannot restart > > a firejail session: > > >

Bug#983746: firejail: with --private=, an existing "bin" directory is read-only

2021-03-01 Thread Reiner Herrmann
Hi Vincent, On Mon, Mar 01, 2021 at 02:49:32AM +0100, Vincent Lefevre wrote: > When using --private=, an existing "bin" directory in > is read-only. This is silly: this means that one cannot restart > a firejail session: > [...] > > I don't see the point to have "bin" read-only in this case,

Bug#983746: firejail: with --private=, an existing "bin" directory is read-only

2021-02-28 Thread Vincent Lefevre
Package: firejail Version: 0.9.64.4-2 Severity: important When using --private=, an existing "bin" directory in is read-only. This is silly: this means that one cannot restart a firejail session: zira:~> firejail --private=$HOME/fj-test zsh Reading profile /etc/firejail/default.profile Reading