-
Notifications
You must be signed in to change notification settings - Fork 687
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
Update grsecurity kernels to 4.4.162 #3913
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few more tests. Only tested in VMs, not on hardware yet. So far, so good. Let's get this in so it can bake during the current development cycle.
hah this is breaking my PR #3909 .. thanks CSO!! Some cherry picking is in order. |
@msheiny Now that #3921 is in, we can rebase this on that, then we should be good for merge. Rebase incoming... Example build failure, showing it's requests: https://circleci.com/gh/freedomofpress/securedrop/19199 |
@conorsch im rebasing... and fixing stuff |
actually i just want to cherry pick here.. |
disregard! i was confused! rebase away |
9cd2900
to
bb708cb
Compare
Now that all users have reported a smooth transition to the 4.4 series kernels, let's remove these old, unmaintained and end-of-life kernel series.
Provides microcode updates to addres various Intel cpu-based vulnerabilities.
Remove 4.4.135 kernels
The microcode package was just added, so let's test for it. Also updated the kernel version to be a constant, so we can reuse it inside package names, notable the firmware image (for additional hardware support).
bb708cb
to
dfabb1c
Compare
I've been seeing some errors in syslog, in qubes staging, I will see if i can reproduce in other environments:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ apt-test.freedom.press
in apt sources for both app and mon
✅ after reboot, both app and mon running 4.4.162
❔ testinfra tests pass - I did not test due to #3938
✅ paxtest blackhat
kills all the things
I did not see any odd messages in syslog like you report @emkll. Minor nit inline, else if you're happy with this, feel free to merge
@@ -3,6 +3,9 @@ | |||
import re | |||
|
|||
|
|||
KERNEL_VERSION = "4.4.162" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: in the spirit of DRY, can we use pytest.securedrop_test_vars.grsec_version
here?
b383733
to
9234c32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
restamping after my requested change was implemented
No concerns, changes look good. Will rebase #3909 on top of latest develop post-merge to re-run CI over there. |
Status
Ready for review
4.4.162 kernel packages have already been uploaded to apt-test.freedom.press. Fixes #3838
Description of Changes
Testing
apt-test.freedom.press
is in apt-sources.vagrant up /staging/
, and testinfra tests passcron-apt -i -s
, and rebootuname -r
returns4.4.162-grsec
paxtest blackhat
kills all the thingsHardware-specific testing
I have tested this in VMs, NUCs and Mac Minis, and seem to work properly. If you have any other hardware
Deployment
Packages are live on apt-test.freedom.press for testing.
For the 0.11.0 release, kernel debs (both the
securedrop-grsec
metapackage andlinux-image-4.4.162-grsec_4.4.162-grsec-1_amd64
need to be uploaded to the apt server).If the instances fail to boot, instructions in https://docs.securedrop.org/en/stable/upgrade/0.5.x_to_0.6.html are still valid.
Checklist
If you made changes to the system configuration: