Timeline for Source request for a GPL-licensed Linux kernel module?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2019 at 4:21 | comment | added | craig65535 | The source of the rpm used to install this software is CrowdStrike. They are both the author and the distributor. Do I email them to ask for source code? I expect they would ignore me, because if they wanted to share source it would already be on their github. This is why I asked if anyone has gone through this kind of thing before. | |
| Jan 13, 2019 at 10:07 | comment | added | amon | @craig65535 for the GPL compliance aspect it is irrelevant who authored the module, only who gave you a copy. So it might be best to determine as part of which RPM the module was installed, and to use the contact info for that package to obtain or request the corresponding source. | |
| Jan 12, 2019 at 18:29 | comment | added | craig65535 | I think the "intree" part is untrue. It's built for my specific RedHat kernel but is not in that source tree. | |
| Jan 12, 2019 at 18:27 | comment | added | craig65535 | The module is from CrowdStrike - but I'm not sure where to go to ask for the source. There's a way for kernel modules to be proprietary, but typically they're not as that limits what symbols they can link to. | |
| Jan 12, 2019 at 11:41 | history | answered | amon | CC BY-SA 4.0 |