ufw should not override procps' default of net.ipv4.tcp_syncookies=1

Bug #1737585 reported by Nils Toedtmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ufw (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

2008 ufw decided to *disable* TCP SYN cookies by default in /etc/ufw/sysctl.conf, see https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565

After a more detailed discussion that had started in 2006, procps *enabled* TCP SYN cookies by default in /etc/sysctl.d/10-network-security.conf in 2009, see https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091

No two packages should try to set conflicting defaults on the same sysctl without very good reason. This is a funny case where the base package procps uses a more secure default (SYN cookies enabled), and the firewall package ufw uses a less secure default (SYN cookies disabled) - one would expect the other way round. At least I would expect ufw not to *weaken* security settings.

Regarding the question whether or not SYN cookies should be enabled (as opposed to the question which package should own this setting): I guess that the are lots of systems without ufw, and all of those run happily with procps' default net.ipv4.tcp_syncookies=1, or at least I could not find any bug reports that complained. The kernel only activates the mechanism once it thinks a syn flood is happening, so whatever the disadvantages of SYN cookies are, they only kick in under these circumstances.

For all the above reasons I suggest ufw should not touch net.ipv4.tcp_syncookies and leave it however it is already set in /etc/sysctl.{conf,d/}

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This was actually fixed earlier this year: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/revision/972 and patched in Debian and Ubuntu via 0.35-3. I'm going to mark this as Fixed Released.

Thanks for reporting this bug! :)

Changed in ufw (Ubuntu):
status: New → Fix Released
Revision history for this message
Nils Toedtmann (m-launchpad-net-mail-nils-toedtmann-net) wrote :

Sorry for only checking the latest LTS, didn't realize it had been fixed in >= 17.04. Thx.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.