4 ms·
The generally accepted (but not well tested) legal position is that it's ok to have a proprietary kernel module that is dynamically loaded. You can, for instan
by rkangel 2y ago
The generally accepted (but not well tested) legal position is that it's ok to have a proprietary kernel module that is dynamically loaded.
You can, for instance, ask a running kernel if it is "tainted" by having loaded a non-GPL module.
- immibis 2y agoGPL exported symbols are the ones that are thought to be so tightly coupled to the kernel implementation that if you are using them, you are writing a derivative work of the kernel.
- simfoo 2y agoYeah that was also my understanding, and I can't imagine a av module able to intercept filesystem and syscalls to be only using non-core symbols. But of course you never know without decompiling the module
- yjftsjthsd-h 2y ago> and I can't imagine a av module able to intercept filesystem and syscalls to be only using non-core symbols. I can, considering that you can do that from user space using strace. Or ebpf which is probably the actual right way to do this kind of thing.
- vbezhenar 2y agoLast time I dealt with HP, I had to use their fakeraid proprietary kernel module which "tainted" the kernel. Of course they never open-sourced it. I guess it's not necessary.