On Thu, May 14, 2020 at 7:31 PM Sreyan Chakravarty wrote:
> I am in the process of reading this detailed article about the bug:
>
> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html
>
>
> Meanwhile, I wanted to know if any one here has the same problem and
> what they did for mi
On Sat, May 9, 2020 at 5:59 PM Sam Varshavchik wrote:
> I haven't done much testing, but this does not seem to be quite right. After
> creating and adding the ipset, iptables -n -L still shows me:
>
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> ACCEPT a
On Thu, May 7, 2020 at 12:12 AM Sam Varshavchik wrote:
> Is there a way with firewall-cmd to /really/ block an IP address, new or
> established connections, or is manually adding an iptables rule my only
> option?
You can bypass connection tracking for dropping existing connections
by adding a ru
