[GH-ISSUE #2072] Nvida drivers using firejail #1400

Closed
opened 2026-05-05 08:03:46 -06:00 by gitea-mirror · 11 comments
Owner

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?

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?
Author
Owner

@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.

<!-- gh-comment-id:408641501 --> @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.
Author
Owner

@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:

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.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2072#issuecomment-408641501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79Bmx4JpPkMkgz4a6_j8Gzwlp7zc5pks5uLPUOgaJpZM4VlOB-
.

<!-- gh-comment-id:408641547 --> @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: > 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. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2072#issuecomment-408641501>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79Bmx4JpPkMkgz4a6_j8Gzwlp7zc5pks5uLPUOgaJpZM4VlOB-> > . >
Author
Owner

@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-driver package. Other distributions have similar ones.

<!-- gh-comment-id:408641741 --> @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-driver` package. Other distributions have similar ones.
Author
Owner

@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:

Most distributions have a way to install the Nvidia driver through their
package system. For example, Debian has the nvidia-driver package. Other
distributions have similar ones.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2072#issuecomment-408641741,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BlPeVd5M20YS9nB0KtpC7Na0oM4iks5uLPZQgaJpZM4VlOB-
.

<!-- gh-comment-id:408642281 --> @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: > Most distributions have a way to install the Nvidia driver through their > package system. For example, Debian has the nvidia-driver package. Other > distributions have similar ones. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2072#issuecomment-408641741>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BlPeVd5M20YS9nB0KtpC7Na0oM4iks5uLPZQgaJpZM4VlOB-> > . >
Author
Owner

@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.

<!-- gh-comment-id:408642705 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:408642735 --> @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.
Author
Owner

@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:

Closed #2072 https://github.com/netblue30/firejail/issues/2072.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2072#event-1758722496, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ab79Bka4Az7uAN1VFANjlz67XV7IKg7nks5uLQ4-gaJpZM4VlOB-
.

<!-- gh-comment-id:408653151 --> @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: > Closed #2072 <https://github.com/netblue30/firejail/issues/2072>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2072#event-1758722496>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/Ab79Bka4Az7uAN1VFANjlz67XV7IKg7nks5uLQ4-gaJpZM4VlOB-> > . >
Author
Owner

@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.

<!-- gh-comment-id:408666634 --> @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.
Author
Owner

@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:

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.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2072#issuecomment-408666634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BmzWz098zwL5yrYPxWAvKsIUhIjZks5uLYzqgaJpZM4VlOB-
.

<!-- gh-comment-id:408675252 --> @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: > 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. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2072#issuecomment-408666634>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BmzWz098zwL5yrYPxWAvKsIUhIjZks5uLYzqgaJpZM4VlOB-> > . >
Author
Owner

@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

<!-- gh-comment-id:408675378 --> @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
Author
Owner

@Raj2032 commented on GitHub (Jul 29, 2018):

Oh

On Sun, Jul 29, 2018 at 10:43 PM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

Nope, not that I'm aware of.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2072#issuecomment-408675378,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BugoHpI9GbWrTlqqZ7d5i-moWFzRks5uLa32gaJpZM4VlOB-
.

<!-- gh-comment-id:408675755 --> @Raj2032 commented on GitHub (Jul 29, 2018): Oh On Sun, Jul 29, 2018 at 10:43 PM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > Nope, not that I'm aware of. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2072#issuecomment-408675378>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BugoHpI9GbWrTlqqZ7d5i-moWFzRks5uLa32gaJpZM4VlOB-> > . >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1400
No description provided.