[Bug 989077] New: Changing network settings with yast leads to unacceptable changes in /etc/postfix/main.cf
http://bugzilla.opensuse.org/show_bug.cgi?id=989077 Bug ID: 989077 Summary: Changing network settings with yast leads to unacceptable changes in /etc/postfix/main.cf Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: michaelof@rocketmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- As a side effect of Bug 989072 I've had to reconfigure my vserver's network settings with yast quite often these days. When applying changes to yast:system->network settings, also changes to /etc/postfix/main.cf are written by yast. In my case, not sure if my example shows all possible changes, the change was from mynetworks_style = host (set by me) to mynetworks_style = subnethost (set by yast) This is completely unacceptable for a vserver/root server/etc. with only one dedicated single IPV4 address, as this OPENS the postfix MTA for ALL OTHER "foreign" HOSTS in the subnet. Because of this I've set Severity to "Major" Remark: This is a very similar issue (same underlying root cause) than Bug 865132. Bug 865132's status is RESOLVED FIXED in 13.1, not sure if the issue reappeared. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=989077
http://bugzilla.opensuse.org/show_bug.cgi?id=989077#c2
Michal Filka
http://bugzilla.opensuse.org/show_bug.cgi?id=989077
http://bugzilla.opensuse.org/show_bug.cgi?id=989077#c3
--- Comment #3 from Michael from Offenbach Germany
http://bugzilla.opensuse.org/show_bug.cgi?id=989077
http://bugzilla.opensuse.org/show_bug.cgi?id=989077#c4
--- Comment #4 from Michal Filka
I can CONFIRM that this bug is fixed now, with yast2-network 3.1.140.5-9.1, coming from http://download.opensuse.org/update/leap/42.1/oss.
But I'm a little confused, as 3.1.140.5-9.1 should be older than the mentioned "should be fixed since yast2-network 3.1.158", or am I wrong?
it is different "version line" (for different product). Simply some features and fixes are shared. E.g. 3.1.158 is opensuse one, 3.1.140.5 is SLES-12-SP1.
Independent question: Any idea why I'm getting an
"You are not authorized to access bug #970320." ???
most probably bcs you're not authorized ;-) It was reported by an enterprise customer for SLES, so it can be locked for certain access rights only. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com