https://bugzilla.novell.com/show_bug.cgi?id=810599 https://bugzilla.novell.com/show_bug.cgi?id=810599#c1 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent CC| |koenig@linux.de Severity|Normal |Critical --- Comment #1 from Harald Koenig <koenig@linux.de> 2013-03-30 08:46:08 UTC --- just got hit by the same problem: a server with some internet connection started with firewall down after update! this should not happen:-(( it's a shame that this security issue did not even got assigned for 10 days now. raising priority and severity because of possible security impacts! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=810599 https://bugzilla.novell.com/show_bug.cgi?id=810599#c3 --- Comment #3 from Harald Koenig <koenig@linux.de> 2013-04-02 08:24:32 UTC --- (In reply to comment #2)

Could you check if the firewall is actually off from the command line, using

SuSEfirewall2 status

if you have a freshly updated machine?

of course, in the mean time I've fixed the missing firewall settings, but before "iptables -L" showed now firewall rules at all (like now after "systemctl stop SuSEfirewall2.service" and "systemctl status SuSEfirewall2.service" showed something line inactive/idle or similar.

In my case, YaST was reporting the firewall was off. However someone in the IRC #suse IRC channel pointed out that it is a bug affecting YaST detection of the firewall status, rather than the firewall actually being off.

I did not try yast(2) at all, only command line tools... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.