| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
I had trouble getting programs.firejail.wrappedBinaries to have any effect on my
system (#152852), because I did not realise that "put[ting] the actual
application binary in the global environment" included adding the program
package to environment.systemPackages, and I thought that the package must be
present for this option to take effect. I have added a clarifying parenthetical
statement explicitly mentioning environment.systemPackages in this caveat.
|
| | |
|
| |
|
|
|
| |
This is slightly more verbose and inconvenient, but it forces you
to think about what the wrapper ownership and permissions will be.
|
| | |
|
| |
|
|
|
|
|
|
| |
Also:
- use `runtimeShell`; and
- remove unused `makeWrapper` input; and
- `exec()` to shed wrapping shell
|
| |
|
|
|
| |
this way the man page etc. becomes available if we enable firejail with
`programs.firejail.enable = true`
|
| | |
|
| | |
|
|
|
Also add support for wrapping binaries with firejail.
|