Page MenuHomeSolus

spectre-meltdown-checker
Closed, SpitePublic

Description

Name: spectre-meltdown-checker
Homepage: https://github.com/speed47/spectre-meltdown-checker
Why? It allows to evaluate whether a system is vulnerable against the several "speculative execution" CVEs that were made public in 2018.
Open source: yes
Tarball: https://github.com/speed47/spectre-meltdown-checker/archive/v0.39.tar.gz

Event Timeline

DataDrake claimed this task.
DataDrake added a subscriber: DataDrake.

No.

No.

Why not? I know it's up to you to include it or not but I thought this would be very helpful for myself to diagnose the system. So why is this rejected for inclusion?

Don't be so lazy. It's actually just 3 steps:

  • curl -L https://meltdown.ovh -o spectre-meltdown-checker.sh
  • chmod +x spectre-meltdown-checker.sh
  • sudo ./spectre-meltdown-checker.sh

vs. 2 steps:

  • sudo eopkg it spectre-meltdown-checker
  • sudo spectre-meltdown-checker

What's the big advantage of having this in the repos?

No.

Why not? I know it's up to you to include it or not but I thought this would be very helpful for myself to diagnose the system. So why is this rejected for inclusion?

Because it can't be used to check a remote system. There is no reason to use this on your local machine as you are already protected ( via Kernel patches, microcode updates, and compiler mitigations), provided that you did not explicitly disable protections via the kernel cmdline options. Claiming that it is needed in Solus is the same as saying you don't trust us to keep your system up to date and secure, whether that is your intent or not.