Skip to content
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

Build a monolithic kernel #48

Open
legoktm opened this issue Apr 1, 2024 · 4 comments
Open

Build a monolithic kernel #48

legoktm opened this issue Apr 1, 2024 · 4 comments

Comments

@legoktm
Copy link
Member

legoktm commented Apr 1, 2024

At #45 (comment) @thedeadliestcatch wrote:

I would strongly suggest considering building monolithic kernels with a minimal config. If you transition away from HVM to pvgrub, and even if you don't, it will be a good idea. Removing LKM support has several benefits in terms of reducing attack surface in the kernel for ROP and code injection scenarios (after all, LKM support comes with the implicit need for a dynamic linker in kernel space).

I replied:

This is a good point and something I started wondering about mid-last week, whether there was any benefit to building individual modules. I'll look into doing a monolithic build.

From what I can tell we just need to change all the m settings to y and then turn off CONFIG_MODULES. We should make sure that the blacklisted modules (see freedomofpress/securedrop#1886) are disabled at build-time as well.

@legoktm
Copy link
Member Author

legoktm commented Apr 3, 2024

Oh heh, we already have an open issue about needing at least 1G memory: freedomofpress/securedrop-workstation#838. I never got around to digging into it further, are you saying it's just a requirement of the grsec patches?

@zenmonkeykstop
Copy link
Contributor

That shouldn't be a problem to set up, we can set the initial memory when we clone the templates used for sd-* app/dispvms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@legoktm @zenmonkeykstop and others