-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module signature verification issues on Ubuntu 16.04 LTS #152
Comments
It looks like some sort of combination of calling
|
Darling is being built in 16.04, but not the kernel module, because the 16.04 is just a Docker container running on Gentoo :-) But what you're showing is not a build failure; it just means the module couldn't be signed. It is up to the user how he deals with loading unsigned modules or signing them somehow, as there is no single good way (e.g. I'd feel bad if I started suggesting to disable validation completely). |
Ahh.. thanks for the heads up! It looks like you actually mention this on the website on the build instructions page. I'll look into just disabling it! |
I guess you can use this: |
When running
sudo make install
in thedarling/src/lkm
directory I get the following error:I looked into this, and according to this issue that another project was having, Ubuntu now uses Linux signed kernel modules. I'm assuming you guys already know about this though! :) As you're building darling on 16.04 on your teamcity ci.
Could you point me in the right direction as to how to get this working? I'm going to continue fiddling around with it, and see about making a pull request documentation wise if I figure something out :)
The text was updated successfully, but these errors were encountered: