January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 900398] New: XenServer Installation failed
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900398 Bug ID: 900398 Summary: XenServer Installation failed Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: olivpass(a)web.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 Build Identifier: openSUSE-13.2-NET-Build0019-x86_64.iso Hi, XenServer installation failed because there is no installation kernel in this iso openSUSE-13.2-NET-Build0019-x86_64.iso! Error Message auf XenServer: Oct 9, 2014 10:05:09 AM Error: Starting VM 'opensuse132_r1_klein' - The bootloader for this VM returned an error -- did the VM installation succeed? INVALID_SOURCE The repository specified did not contain a required file, file:///tmp/cdrom-repo-isbQ8F/boot/x86_64/vmlinuz-xen. The DVD installation with iso openSUSE-13.2-DVD-Build0019-x86_64.iso works well. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1017919] New: using "include =" in smb.conf does not work on Leap 42.1
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017919 Bug ID: 1017919 Summary: using "include =" in smb.conf does not work on Leap 42.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: wagner-thomas(a)gmx.at QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- Hi, On Leap 42.1 the "include =" statement in smb.conf seems to be not working. For test-purposes I used this simple config file: # cat /etc/samba/users/thomas.conf [tmp] comment = test tmp path = /tmp In /etc/samba/smb.conf I added the following line: include = /etc/samba/users/thomas.conf Then I restarted samba with "systemctl restart smb", however smbd crashed immediately with "Failed to start Samba SMB Daemon." in the systemd log. Starting smbd in interactive mode to see possible error won't show the share [tmp] # smbd -i -d 2 smbd version 4.2.4-21.3-3689-SUSE-SLE_12-x86_64 started. Copyright Andrew Tridgell and the Samba Team 1992-2014 uid=0 gid=0 euid=0 egid=0 rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Can't find include file /etc/samba/dhcp.conf Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Can't find include file /etc/samba/dhcp.conf Processing section "[homes]" Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[printers]" Processing section "[print$]" added interface eth0 ip=192.168.7.107 bcast=192.168.7.255 netmask=255.255.255.0 testparm won't find an error but does show [tmp] # testparm Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Can't find include file /etc/samba/dhcp.conf Processing section "[homes]" Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[printers]" Processing section "[print$]" Processing section "[tmp]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] map to guest = Bad User printcap name = cups logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile usershare allow guests = Yes idmap config * : backend = tdb cups options = raw include = /etc/samba/dhcp.conf [homes] comment = Home Directories valid users = %S %D%w%S read only = No inherit acls = Yes browseable = No [profiles] comment = Network Profiles Service path = %H read only = No create mask = 0600 directory mask = 0700 store dos attributes = Yes [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes [printers] comment = All Printers path = /var/tmp create mask = 0600 printable = Yes print ok = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 include = /etc/samba/users/thomas.conf [tmp] comment = test tmp path = /tmp When I copy the content of /etc/samba/users/thomas.conf to smb.conf (read: do manually what "include =" is supposed to do). It works. Samba starts and I can access /tmp. Using include = /etc/samba/users/%U.conf instead of include = /etc/samba/users/thomas.conf will allow smb to start but /tmp won't be serverd. TL;DR With Samba 4.2.4 on Leap 42.1 "include =" cannot be used in smb.conf Best regards Thomas -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1018259] VUL-0: CVE-2017-5180: firejail: local root exploit
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018259 http://bugzilla.suse.com/show_bug.cgi?id=1018259#c3 --- Comment #3 from Andreas Stieger <astieger(a)suse.com> --- (In reply to Marcus Meissner from comment #2) > is the CVE correct? it is quite high for a 2017 one >From http://seclists.org/oss-sec/2017/q1/21 > Use CVE-2017-5180. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018259] VUL-0: CVE-2017-5180: firejail: local root exploit
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018259 http://bugzilla.suse.com/show_bug.cgi?id=1018259#c2 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- is the CVE correct? it is quite high for a 2017 one -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 909418] when ejecting DVD using hardware button, system thinks DVD is still mounted
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=909418 http://bugzilla.suse.com/show_bug.cgi?id=909418#c46 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #46 from Franck Bui <fbui(a)suse.com> --- Please open a new bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017925] LibreOffice demands libobdc.so.1 but unixOBDC only provids libobdc.so.2
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017925 http://bugzilla.suse.com/show_bug.cgi?id=1017925#c7 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Adam Majer <amajer(a)suse.com> --- For Leap 42.1, please install the unixODBC-devel package. This bug has already been addressed in Leap 42.2's version unixODBC and also fixed in latest upstream version of LibreOffice (it will look for libodbc.so.2). Since this is not an important bug (because of an very easy workaround), it is unlikely to be fixed in Leap 42.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 909418] when ejecting DVD using hardware button, system thinks DVD is still mounted
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=909418 http://bugzilla.suse.com/show_bug.cgi?id=909418#c45 Peter Wullinger <wullinger(a)rz.uni-kiel.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |wullinger(a)rz.uni-kiel.de Resolution|FIXED |--- --- Comment #45 from Peter Wullinger <wullinger(a)rz.uni-kiel.de> --- The implemented patch seems to cause an assertion fault, in particular I can observe: systemd[11505]: Assertion 'dev' failed at src/core/device.c:301, function device_is_bound_by_mounts(). Aborting. systemd[1]: Assertion 'dev' failed at src/core/device.c:301, function device_is_bound_by_mounts(). Aborting. systemd[1]: Caught <ABRT>, dumped core as pid 30128. systemd[1]: Freezing execution. It looks like it is valid for dev to be NULL in device_setup_unit(Manager *m, struct udev_device *dev, const char *path, bool main). At least there are various guards with if (dev) in the source. This is not checked before the (new) call to device_is_bound_by_mounts(), which itself does assert(dev). As a result, PID1 aborts and the system cannot be managed any more. I'm not familiar with the new logic, but the fix may be a simple guard condition inside device_is_bound_by_mounts(). Note that this would halt a production machine hard, being unable to even reboot normally (since the system dbus is down Upstream Issue: https://github.com/systemd/systemd/issues/5025 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018371] New: VUL-0: CVE-2016-10030: slurm: prolog failure vulnerability
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018371 Bug ID: 1018371 Summary: VUL-0: CVE-2016-10030: slurm: prolog failure vulnerability Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other URL: https://smash.suse.de/issue/178269/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: eich(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de CC: burnus(a)gmx.de, eich(a)suse.com, scorot(a)free.fr Found By: Security Response Team Blocker: --- network:cluster/slurm, not in the distribution The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 ("success") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-10030 https://www.schedmd.com/news.php?id=178 https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017738] New: sshd pubkey auth fails due to wrong path for authorized_keys in sshd_config
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017738 Bug ID: 1017738 Summary: sshd pubkey auth fails due to wrong path for authorized_keys in sshd_config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: audiomobster(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In /etc/sshd_config "AuthorizeKeysFile" must be set like this: AuthorizedKeysFile /%h/.ssh/authorized_keys -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1017783] Boot issues with Tumbleweed and Kernel 4.9 (booting stops at Loading initial ramdisk; kernel 4.9 does not boot)
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017783 Steve Wickert <steve.wickert(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |steve.wickert(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0