Re:Orphaning bcachefs-tools in Debian
by JackSlateur on Saturday August 31, 2024 @08:43AM
(#41408502)
And if my kernel crashes ?
And if whatever library bugged, oh well, random people can access my systems ?
And if my bgpd bugged, oh well, we just inject random routes et forward data randomly ?
Makes no sense.
Your kernel has no external library dependencies.
Relaxing library requirements can introduce security issues when the dependency behaviour changes, so I'm not sure what the argument is.
If your bgp is bugged, yeah it sucks, but it's recoverable. We're using encrypted traffic these days to ensure that even captured traffic is safe.
The difference here is that data corruption is not recoverable.
Re:Orphaning bcachefs-tools in Debian
by JackSlateur on Saturday August 31, 2024 @09:18AM
(#41408683)
Linux uses at least libc
Linux kernel doesn't use libc. Libc provides the interface for userspace to call the kernel.
Re:Orphaning bcachefs-tools in Debian
by JackSlateur on Saturday August 31, 2024 @09:32AM
(#41408764)
It does includes its headers (stdlib.h, at least), in various subsystems.
In user space tools and tests only. The kernel part does not include stdlib.h anywhere. Nowhere where it matters in the context of "And if my kernel crashes?"
Re:Orphaning bcachefs-tools in Debian
by JackSlateur on Saturday August 31, 2024 @10:44AM
(#41409245)
You are right, thank you for the insight
Oh well, it was probably just a crash in my Internet connected software where users can just sent inputs to be processed on my machine.
RCE would have been worse than file system bugs, as it leads directly to a superset of problems including potentially losing all your files.
It's similar to why restic (backup software) has official, static, reproducible binaries in their releases.