Consider adding the Bonding module to the SD grsec kernel

Description

Currently, the grsec kernel does not include the Bonding module necessary for combining multiple network interfaces into one. Although SecureDrop is a relatively low-bandwidth application, there are organizations that elect to make use of bonding, and in those scenarios they risk losing network access (and having the SecureDrop installation fail) once the system reboots into the current grsec kernel.

How will this impact SecureDrop users?

By adding this support, organizations who make use of bonded network interfaces would be able proceed with an installation as expected.

How would this affect SecureDrop's threat model?

No threat model changes or additional risks that I can think of.

User Stories

As an administrator, I want the grsec kernel to include the bonding module, so I can make use of bonded network interfaces to increase overall network throughput.

Start by locating the grsec kernel configuration and build entry point in this repository, then inspect how kernel modules are selected. Verify that the built kernel contains the bonding module and that a SecureDrop installation using bonded interfaces retains network access after reboot.