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.

Sign up for GitHub

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

Jump to bottom

Add Google's kernelctf attack surface reduction #137

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add Google's kernelctf attack surface reduction #137

wants to merge 1 commit into from

Conversation

jvoisin
Copy link
Contributor

@jvoisin jvoisin commented May 16, 2024

No description provided.

@a13xp0p0v a13xp0p0v force-pushed the master branch 2 times, most recently from ea24300 to 78f5595 Compare June 2, 2024 12:49
@a13xp0p0v
Copy link
Owner

Hi @jvoisin,

Thanks for the idea!

Does disabling CONFIG_NF_TABLES break anything vital for general-purpose GNU/Linux distros?

@jvoisin
Copy link
Contributor Author

jvoisin commented Jun 9, 2024

If they're using nftables, yes :o)
Otherwise, if the old iptables interface is used, nothing should break, no.

@a13xp0p0v a13xp0p0v added the idea_for_the_future This idea is interesting, but needs more discussion label Jul 3, 2024
@a13xp0p0v
Copy link
Owner

Ok, let's save it as an idea for the future.

I have an idea: to add a column |with care| for dangerous options that may break something or introduce significant performance impact.

@a13xp0p0v a13xp0p0v mentioned this pull request Jul 3, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
idea_for_the_future This idea is interesting, but needs more discussion
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jvoisin @a13xp0p0v