mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2072] Nvida drivers using firejail #1400
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#1400
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 @Raj2032 on GitHub (Jul 28, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2072
If I installed Nvidia drivers through firejail and I completly block Nvidia from having access to any of my files and other stuff, would Nvidia work still and would it be impossible for Nvidia to collect any additional information about my computer?
@chiraag-nataraj commented on GitHub (Jul 28, 2018):
It wouldn't be able to send anything to Nvidia during the install, but that says nothing about whether the modules send anything back when they're loaded or running. And no, you can't use firejail to sandbox kernel modules.
That being said, I would just use your distribution packages to install the driver — it's generally much less of a headache.
@Raj2032 commented on GitHub (Jul 28, 2018):
" distribution packages to install the driver " What is that exactly?
On Sun, Jul 29, 2018 at 9:34 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:
@chiraag-nataraj commented on GitHub (Jul 28, 2018):
Most distributions have a way to install the Nvidia driver through their package system. For example, Debian has the
nvidia-driverpackage. Other distributions have similar ones.@Raj2032 commented on GitHub (Jul 28, 2018):
And how would I know a kernal module won't invade a person's privacy,
especially since this is closed source?
On Sun, Jul 29, 2018 at 9:40 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:
@chiraag-nataraj commented on GitHub (Jul 29, 2018):
You don't know that. But firejail won't protect you against that because it's meant to sandbox programs. All of the kernel-based systems it uses are meant to sandbox userspace programs. They don't work on kernel modules.
@chiraag-nataraj commented on GitHub (Jul 29, 2018):
The only thing you can protect in this case is the installation method. And in that sense, I trust the distribution's package manager more than some binary installer.
@Raj2032 commented on GitHub (Jul 29, 2018):
" All of the kernel-based systems it uses are meant to sandbox userspace
programs" Sorry I didn't understand this, are you saying that the package
manager system we use where we install Nvidia drivers already sandboxes
these drivers?
On Sun, Jul 29, 2018 at 11:22 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:
@chiraag-nataraj commented on GitHub (Jul 29, 2018):
No. What I'm saying is that sandboxing kernel modules is entirely out of the scope of firejail because the kernel technologies it uses (seccomp-bpf filters, capabilities, namespaces) are all designed to sandbox programs, not modules.
@Raj2032 commented on GitHub (Jul 29, 2018):
Is there a way to sandbox kernel modules?
On Sun, Jul 29, 2018 at 8:22 PM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:
@chiraag-nataraj commented on GitHub (Jul 29, 2018):
Nope, not that I'm aware of. See this: https://unix.stackexchange.com/questions/266131/are-there-sandboxing-concepts-for-proprietary-binary-kernel-modules-in-linux#266385
@Raj2032 commented on GitHub (Jul 29, 2018):
Oh
On Sun, Jul 29, 2018 at 10:43 PM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote: