August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 865132] New: Postfix main.cnf had mailbox_command stripped
by bugzilla_noreply＠novell.com 23 Jul '16

23 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=865132 https://bugzilla.novell.com/show_bug.cgi?id=865132#c0 Summary: Postfix main.cnf had mailbox_command stripped Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrew(a)acooke.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=579559) --> (http://bugzilla.novell.com/attachment.cgi?id=579559) output from save_y2logs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 I was confusedly messing around with Yast network config (adding and then removing a bridge) when local mail delivery suddenly broke. Instead of mail messages being delivered to a local maildir via procmail, they were being delivered to the system mailbox. Looking at /etc/postfix, I saw that main.cnf had a modified date of today. When I diffed it with a daily backup, the mailbox_command parameter had been cleared. originally I had mailbox_command = /usr/bin/procmail but that had been changed to mailbox_command = Note - for some strange reason, this entry appeared TWICE in main.cnf. Both entries were consistent, in either case. So it would be more correct to say that originally I had it defined twice as procmail, and afterwards, it was cleared twice. Grepping for "postfix" in y2log, I see y2log:2014-02-21 11:26:04 <1> block(7737) [Ruby] network/runtime.rb:48 Updating sendmail and/or postfix configuration. which had the right date (and about the right time; by this point I had edited main.cnf and changed the timestamps, so I cannot check exactly). That message seems to be associated with changes made when I deleted the bridge in Yast (but decide yourself; I will include the logs). It seems that the "update" to postfix accidentally wiped important data. This is not good. Reproducible: Didn't try Steps to Reproduce: 1. Sorry, but I don't want to mess around with this system more than necessary. 2. 3. -- 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.

1 12

[Bug 852604] New: Modify network config through yast messing up postfix config main.cf and master.cf
by bugzilla_noreply＠novell.com 23 Jul '16

23 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=852604 https://bugzilla.novell.com/show_bug.cgi?id=852604#c0 Summary: Modify network config through yast messing up postfix config main.cf and master.cf Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: HP OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joerg.rohrer(a)upc-cablecom.ch QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0 After i upgraded the OS via zypper dup from 12.3 to 13.1 the postfix config is screwed up after you modify something on the "network settings" through yast. I just disabled ipv6. Reproducible: Always Steps to Reproduce: 1. do a pseudo main.cf. put something under smtpd_recipient_restrictions 2. Start yast. disable or enable as example ipv6. 3. check main.cf. Actual Results: main.cf and master.cf are screwed up Expected Results: don't touch config files at all. -- 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.

1 12

[Bug 917818] New: fail2ban can not use systemd-journal to ban ips
by bugzilla_noreply＠novell.com 23 Jul '16

23 Jul '16

http://bugzilla.opensuse.org/show_bug.cgi?id=917818 Bug ID: 917818 Summary: fail2ban can not use systemd-journal to ban ips Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: robin.roth(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build Identifier: The fail2ban version availbale with openSuSE 13.2 is not capable of parsing the systemd-journal. Therefore an existing 13.1 configuration that bans ip's based on failed logins will not work when upgrading to 13.2 (fail2ban fails to start saying /var/log/messages does not exist). This essentially disables the security provided by fail2ban against brute-force attacks. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 930191] New: kernel BUG at ../security/apparmor/inc
by bugzilla_noreply＠novell.com 22 Jul '16

22 Jul '16

http://bugzilla.opensuse.org/show_bug.cgi?id=930191 Bug ID: 930191 Summary: kernel BUG at ../security/apparmor/inc Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 633707 --> http://bugzilla.opensuse.org/attachment.cgi?id=633707&action=edit first file I am running a Lenovo X201 notebook with opensuse 13.2 and standard kernel. I recently got a kernel panic. I checked my journalctl and found that I have several warnings about a kernel.bug involving apparmor. I thought I forward them sorry for not being more specific. Journal is available anytime if you tell me what I have to send and how I have to gather the info as I have not a big knowlege in kernel things, I apologize. I join three of the most recent warnings, the panic should be within, I searched for "kernel panic" in the log but strangely did not find the string. So I do not know for sure were to search (as I was stupid and did not take the time and date exactly when it happened). Attachment txt files, exerpts of the journal. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 546843] New: gkeytool lack a support for ECC certificates
by bugzilla_noreply＠novell.com 22 Jul '16

22 Jul '16

http://bugzilla.novell.com/show_bug.cgi?id=546843 User mvyskocil(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=546843#c546468 Summary: gkeytool lack a support for ECC certificates Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: matz(a)novell.com ReportedBy: mvyskocil(a)novell.com QAContact: qa(a)suse.de Found By: Development gkeytool fails on read ECC certificate - this is also in openjdk, but the fix adds a support for Elliptic Curve Cryptography already exists in upstream, but I did not find similar for gcc java. I read a commit log, asked on #openjdk(a)irc.oftc.net, where many openjdk and gcj developers are, but noone answered me yet. see bnc#546468 for details about openjdk The java-1_5_0-gcj-compat fails on keystore creation: + for key in '/etc/ssl/certs/*.pem' + yes ++ basename /etc/ssl/certs/COMODO_ECC_Certification_Authority.pem + gkeytool-4.4 -import -keystore cacerts -file /etc/ssl/certs/COMODO_ECC_Certification_Authority.pem -storepass '' -alias COMODO_ECC_Certification_Authority.pem keytool error: java.security.cert.CertificateException error: Bad exit status from /var/tmp/rpm-tmp.cYvDZ9 (%prep) I'm going to workaround it in java-1_5_0-gcj-compat by skipping those certificates during keystore creation, to provide a fix immediately to make OpenOffice.org build immediately. But it'd be nice to have gcj with ECC support enabled. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 725800] New: devel:libraries:c_c /libbsd: Bug
by bugzilla_noreply＠novell.com 19 Jul '16

19 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=725800 https://bugzilla.novell.com/show_bug.cgi?id=725800#c0 Summary: devel:libraries:c_c /libbsd: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: mrueckert(a)suse.com ReportedBy: stefan.jakobs(a)rus.uni-stuttgart.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: crrodriguez(a)opensuse.org, pgajdos(a)suse.com Found By: --- Blocker: --- The x86_64 devel package of libbsd-devel is lacking the file /usr/include/bsd/libutil.h. The i586 package has that file. I got the following error while trying to build xxxterm: In file included from ../xxxterm.c:48:0: /usr/include/bsd/stdlib.h:46:25: fatal error: bsd/libutil.h: No such file or directory # rpm -ql -p ./libbsd-devel-0.3.0-1.1.i586.rpm | grep libutil.h /usr/include/bsd/libutil.h /usr/include/libutil.h # rpm -ql -p ./libbsd-devel-0.3.0-1.1.x86_64.rpm | grep libutil.h /usr/include/libutil.h -- 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.

1 4

[Bug 913058] New: GNU tar doesn't cooperate well with Amanda anymore
by bugzilla_noreply＠novell.com 16 Jul '16

16 Jul '16

http://bugzilla.opensuse.org/show_bug.cgi?id=913058 Bug ID: 913058 Summary: GNU tar doesn't cooperate well with Amanda anymore Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: andreas.bolsch(a)alumni.tu-berlin.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Restoring files from Amanda via 'amrecover' doesn't work as expected anymore. When adding a directory to the extraction list only the directory itself gets extracted from the backup but *NOT* the files and directories below it. This affects only the recovery, the files still go into the backups and it is possible to extract everything manually, but that's quite cumbersome and makes 'amrecover' almost useless ... Details and a patch already available in the thread starting at http://lists.gnu.org/archive/html/bug-tar/2014-09/msg00006.html Would be nice to have the patch integrated. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 931152] New: During Default Installation Suse Firewall does NOT Assign any ZONE to the Network Interface Card
by bugzilla_noreply＠novell.com 15 Jul '16

15 Jul '16

http://bugzilla.opensuse.org/show_bug.cgi?id=931152 Bug ID: 931152 Summary: During Default Installation Suse Firewall does NOT Assign any ZONE to the Network Interface Card Classification: openSUSE Product: openSUSE 12.3 Version: Final Hardware: x86-64 OS: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: secure(a)aphofis.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I’ve have 4 x 12.3 Default Installations. 3 KDE 1 Gnome On inspection each and every PC showed the NIC as not being assigned to be in ANY Zone of the Suse2Firewall. You can easily identify this by watching the boot log from ESC during Start-up and you find that Suseefirewall doesn’t even start as such. In the unlikely event you cant validate this I'll do a fresh install for you and send you logs but sending you Yast Logs for any installation that is moths old, may yield little practice help due size and other extraneous issues. O.T Thanks for bashing out the Bug fixes and wow thanks for putting the graphical Bug numbers back on screen. A development project without public access to numbers as it has been for a few years when it disappeared off our screens....well I wont say the obvious but Hey, unreal work being done to fix bugs if the daily updates are any example -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 804992] New: tomcat: sanitize the CLASSPATH before start a service
by bugzilla_noreply＠novell.com 15 Jul '16

15 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=804992 https://bugzilla.novell.com/show_bug.cgi?id=804992#c0 Summary: tomcat: sanitize the CLASSPATH before start a service Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Java AssignedTo: mvyskocil(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- background: https://build.opensuse.org/request/show/15558 http://youtrack.jetbrains.com/issue/JT-18545 the CLASSPATH should be sanitized: 1.) remove trailing colons 2.) remove :: @maintenance, please add it to planned list for 12.2, 12.1, sle-10, sle-11. -- 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.

1 23

[Bug 941396] New: VUL-0: CVE-2015-5179: FreeIPA: non-printable characters aren't checked in every case of user data
by bugzilla_noreply＠novell.com 15 Jul '16

15 Jul '16

http://bugzilla.suse.com/show_bug.cgi?id=941396 Bug ID: 941396 Summary: VUL-0: CVE-2015-5179: FreeIPA: non-printable characters aren't checked in every case of user data Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: hguo(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- https://fedorahosted.org/freeipa/ticket/5153 Reported by: alich We might need more string checks for non-printable characters (same issue with \177 - DEL). VERSION: 4.2.90.201507201402GIT37b1af9, API_VERSION: 2.146 Affected: openSUSE:Factory/freeipa available on Tumbleweed: No OBS bugowner found. Assign to last committer Howard Guo. References: https://bugzilla.redhat.com/show_bug.cgi?id=1252567 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5179 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5179 -- You are receiving this mail because: You are on the CC list for the bug.

1 3