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

KSPP future in defconf linux distribution. #44

Closed
bryn1u opened this issue May 10, 2020 · 4 comments
Closed

KSPP future in defconf linux distribution. #44

bryn1u opened this issue May 10, 2020 · 4 comments

Comments

@bryn1u
Copy link

bryn1u commented May 10, 2020

Hello,

Im just curious what is the status of implementing KSPP to default kernel of linux GNU distribution ? Why linux distributions dont impelment for example most of kspp solutions for example steackleak or gcc hardeneing ? I use most of kspp feature based on your script Alexander and kernel works like a charm. Someone can explain to me ?

@Bernhard40
Copy link

Some settings may affect performance, debugability, support for older userspace software, etc.

@a13xp0p0v
Copy link
Owner

Some settings may affect performance, debugability, support for older userspace software, etc.

I agree.
Moreover, kernel self-protection features often give different performance penalty for different kinds of workload. It's difficult to find one kernel configuration that makes everyone happy.

I think Linux distributions could provide several kernel flavours for different purposes (e.g. generic, hardened, low-latency), to improve the situation.

I'm sure @kees has more insights about this.

@kees
Copy link

kees commented May 18, 2020

Yup! There is an open bug with KSPP to provide a defconfig fragment selection interface to the upstream kernel. You can see more details here:
KSPP/linux#14

@bryn1u
Copy link
Author

bryn1u commented May 20, 2020

Okey. Thanks guys for your work and explanation.

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

4 participants