February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1163082] New: factory-auto can't read some macros
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163082 Bug ID: 1163082 Summary: factory-auto can't read some macros Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hillwoodroc(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- I defined some macros in spec like this: %define commit f91a880e9dbf4ad28fbe9cda2cb899106c25ef97 %define shortcommit %(c=%{commit}; echo ${c:0:7}) The OBS could read them successfully, but factory-auto could not read the %{shortcommit} macro and declined my request. factory-auto thought there was a error in my spec: Output of check script: Source validator failed. Try "osc service localrun source_validator" (E) lunar-calendar-MACRO.tar.gz mentioned in spec file does not exist. (W) Attention, lunar-calendar-f91a880.tar.gz is not mentioned in spec files as source or patch. I don't think so. The request is https://build.opensuse.org/request/show/770634. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1162950] New: AUDIT-1: pam: mode of /sbin/unix*_chkpwd
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162950 Bug ID: 1162950 Summary: AUDIT-1: pam: mode of /sbin/unix*_chkpwd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: josef.moellers(a)suse.com Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jsegitz(a)suse.com, malte.kraus(a)suse.com, security-team(a)suse.de Found By: --- Blocker: --- In the proactive security we noticed that /sbin/unix_chkpwd and /sbin/unix2_chkpwd are installed setuid-root per our long standing entries in our permissions package configuration. The following mode and ownership are set: -rwsr-xr-x 1 root shadow 15K 6. Nov 14:41 /sbin/unix2_chkpwd -rwsr-xr-x 1 root shadow 27K 6. Nov 14:41 /sbin/unix_chkpwd The programs are installed with privileges to allow them to check against password hashes in /etc/shadow. /etc/shadow is actually owned by the shadow group: -rw-r----- 1 root shadow 1.1K 26. Jul 2019 /etc/shadow So the question we have is why unix*_chkpwd aren't installed setgid-shadow instead of setuid-root? It looks like this would be sufficient. The current setting with unix_chkpwd being owned by the shadow group but also have the setuid-root bit doesn't make sense in any case. I you can confirm that installing them setgid-shadow is sufficient then we can adjust the permissions configuration accordingly. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1160062] Update cracklib-dict-full package
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1160062 Michel Normand <normand(a)linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |normand(a)linux.vnet.ibm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120637] New: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1120637 Bug ID: 1120637 Summary: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hello! 've a test VLAN0, created via YaST2 standard wizard interface. Result config: ===== k_mikhail@linux-mk500:~> cat /etc/sysconfig/network/ifcfg-vlan0 BOOTPROTO='static' BROADCAST='' ETHERDEVICE='eth0' ETHTOOL_OPTIONS='' IPADDR='192.168.70.222/24' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' VLAN_ID='0' ====== The question is about REMOTE_IPADDR='' field: it is present in final config, but cannot be defined in YaST2 GUI. Steps-to-reproduce: 1. Open YaST2 via X11 or terminal. 2. Add a VLAN interface via YaST2. 3. Check 'cat /etc/sysconfig/network/ifcfg-vlan0' output after 2. is finished. Possible solution: 1. Have specific filed in YaST2 GUI for that to have possibility to add such address. 2. Keep REMOTE_IPADDR='' as is in case of leaving this field empty in YaST2 settings. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1163028] mount.nfs needs /etc/protocols
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1163028 http://bugzilla.suse.com/show_bug.cgi?id=1163028#c1 --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- Please check your /etc/*.rpm* files and merge them with your changes to get your system working correct again. The symlinks are no solution. You should check for *.rpmnew and *.rpmsave files after every update and merge them. Hint: /etc/nsswitch.conf.rpmnew -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162666] /etc/services moved
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162666 http://bugzilla.suse.com/show_bug.cgi?id=1162666#c13 --- Comment #13 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Paul Bransford from comment #12) > Postfix still needs work for this change, as '/etc/postfix/system/cond_slp' > has /etc/services only. this is present in the postfix unit, as a > ExecStartPost command. postfix should use getent services instead of this sed hack. Please create an own report for this, else you will never see a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c12 --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Suse User from comment #11) > > Why does pesign fail completely for 32bit? > > I don't know. I am not an expert. Sure, the answer and a solution is in comment 9. > > BTW do you have so old CPU, that -pae doesn't work on it? > > Attaching lscpu. Flags: fpu … pae It really looks like you should use more secure kernel-pae (NX), not kernel-default. Doesn't it work for you? Could you try it? It won't fix this problem, though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162479] Failure to create RAID0 or LVM when installing on two disks
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162479 http://bugzilla.suse.com/show_bug.cgi?id=1162479#c5 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colyli(a)suse.com Flags| |needinfo?(colyli(a)suse.com) --- Comment #5 from Neil Brown <nfbrown(a)suse.com> --- The problem here related to the fact that the RAID0 has two components of different sizes. A bug was introduced in Linux 3.14 which change the way data was laid out on those drives. So if you create such RAID0 with 3.13 (or earlier) and access it on 3.14 (or later) the data might get corrupted. We added code in Linux 5.4 so that array like that will be rejected (with error 524) unless they are explicitly marked to say which layout to use. mdadm was also change to explicitly set a layout on newer kernels. It seems that the new mdadm isn't being used here. Coly: where are we up to with the new mdadm? Is it in Tumbleweed? If so, when did it land? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158873] [Build 536.2] openQA test fails in random places on GNOME - wayland session suddenly crashed(sporadic)
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1158873 http://bugzilla.suse.com/show_bug.cgi?id=1158873#c15 --- Comment #15 from xiaoguang wang <xiaoguang.wang(a)suse.com> --- Could we get a journal log when gimp test case is successful? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159669] Previous authentication failure in GDM prevents XFCE session starting
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159669 Grace Wang <grace.wang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grace.wang(a)suse.com, | |yfjiang(a)suse.com, | |zcjia(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0