| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
* ~/.viminfo
* ~/.lesshst
* ~/.python_history
|
| | |
|
| |
|
|
| |
The files holds credentials to WebDAV servers in plaintext
hence it's probably a good idea to limit access to them.
|
| | |
|
| |
|
|
|
|
| |
* Add .pythonrc.py to disable-common.inc
* Move .pythonrc.py to more appropriate section
|
| | |
|
| |\
| |
| |
| | |
lockdis_ipc_fixes
|
| | | |
|
| | |
| |
| |
| |
| | |
Since nss 3.42, '$HOME/.local/share/pki' is supported dir for storing certs
https://hg.mozilla.org/projects/nss/rev/da45424cb9a0b4d8e45e5040e2e3b574d994e254
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
c083a7b737050c532977b46fac6400f1dbc24ff6
|
| |
|
|
|
|
|
|
|
|
| |
setting the KDE_FORK_SLAVES environment variable removes all inconsistencies
that arise from slaves running outside the sandbox or in a different sandbox;
it also makes it slightly more difficult to abuse KIO in general and helps to
mitigate security problems due to thumbnailing, which now always happens inside
the same sandbox. The trade-off is more concurrently running slave processes.
closes #2285
|
| | |
|
| |
|
|
|
|
|
| |
read-write and read-only are applied in sequence, don't
override read-only restrictions in ~/.local/share
issue #2200
|
| | |
|
| |
|
|
| |
search for the file.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- Change some links in README to HTTPS
- Fixup some typos in firejail-profile manpage
- Cleanup dash from private-etc
- Fixup gradio
- Synchronize server profile with default profile
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Configuration for cloud providers is sensitive information; it should be
in the default block list. I didn't see profiles for gcloud or awscli,
so haven't added any exclusions.
boto and kubectl are not provider-specific, but also store credentials for
whichever platforms they happen to be being used with.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
While it is believed that blacklisting these files is a safe default,
it has the effect that untrusted certificates have to be acknowledged every
time they are encountered (with whitelisting it is possible to accept
them for the duration of an application session).
Where this causes usability issues, it will be necessary to noblacklist
these paths.
|
| |
|
|
|
|
|
|
| |
while it is essential to deny manipulation of these files,
the information contained therein should be only of secondary value
by changing blacklist to read-only, notification functionality is
restored
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
and whitelist some kio settings, because we don't know if slave processes will run inside or outside the sandbox.
also prevents weird bugs that depend on sequence in which applications were started.
|
| |
|
|
| |
further to 8aec7694cb4c7c0d07b333b689ab19faacb519f9
|
| | |
|
| | |
|
| |
|
| |
hardcoded since 1e7045b55cc1e189dba6d9ed21c05c90663f3736
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
disable-common.inc blacklists whole .ssh, but some profiles (e.g. idea.sh)
unblacklists it to allow git over ssh with public key auth.
But this creates security hole, since firejailed app could modify
~/.ssh/authorized_keys and allow arbitrary code execution on the host with sshd
installed (e.g. ssh localhost and run any program) or even open backdoor for
remote attacker.
This commits disallows write access to ~/.ssh/authorized_keys even if .ssh was
unblacklisted.
Signed-off-by: Alexander GQ Gerasiov <gq@cs.msu.su>
|
| |
|
|
|
| |
homesick is dotfiles manager. It keeps dotfiles (e.g. .bashrc) in repository
under ~/.homesick and puts symlinks into home directory.
|
| | |
|
rusty-snake
Jose Riha
Senemu
smitsohu
Fred-Barclay
Lockdis
Vincent43
Tad
rusty-snake
glitsj16
Glenn Washburn
curiosity-seeker
netblue30
1dnrr
ಚಿರಾಗ್ ನಟರಾಜ್
James Elford
startx2017
joelazar
Alexander GQ Gerasiov