 Web servers keepalive settings and TCP keepalive enable the attack. My webserver was not particularly affected by that but the OS was. Or more precisely MariaDB that turned on the TCP keepalive that is normally disabled in Debian. If you are running MariaDB locally and without any network connections, enabling TCP keeplive for it makes no sense.
Web servers keepalive settings and TCP keepalive enable the attack. My webserver was not particularly affected by that but the OS was. Or more precisely MariaDB that turned on the TCP keepalive that is normally disabled in Debian. If you are running MariaDB locally and without any network connections, enabling TCP keeplive for it makes no sense.WARNING: SSHD uses but does not require TCP keepalive
If you disable tcp-keepalive, ssh will disconnect immediately. Unless you have physical access to your server or a recovery console, you will not be able to re-connect using ssh. SSHD does not need TCP keepalive to keep the connections alive although it is enabled by default.
You can disable TCP keepalive dependency by adding to your SSHD config
Code: Select all
sudo nano /etc/ssh_configCode: Select all
TCPKeepAlive noCode: Select all
sudo systemctl reload sshdHow to turn TCP keepalive off completely and permanently in Debian?
Before disabling TCP keepalive you must check carefully if there are any software that requires it.
To disable TCP keepalive you need to add settings to your sysconf configuration file to make the configuration persistent:
Code: Select all
sudo nano /etc/sysctl.confCode: Select all
net.ipv4.tcp_keepalive_time=0
net.ipv4.tcp_keepalive_intvl=0
net.ipv4.tcp_keepalive_probes=0Code: Select all
sudo sysctl -pHappy hacking,
s
