January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1018187] New: [yast2] provide summary, at the same time a confirmation form with settings after bootloader configuration is ready to be used
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018187 Bug ID: 1018187 Summary: [yast2] provide summary, at the same time a confirmation form with settings after bootloader configuration is ready to be used Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: richard.bos(a)xs4all.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- As the bootloader config is an important piece of the system, it may be helpful to the user to provide the user a summary of the chosen settings and selections taken by the bootloader tool, after the user finishes configuring the bootloader settings. A good example of an automatic selection, is the selection to use the active disk (that is: if current openSUSE install is at sdb5, the boot code location (if selected) will be sdb and not sda when the disk order is sda sdb). The form can also be used to check if the chosen settings make sense. It's probably more useful when the user is adding or changing disk or when a new openSUSE version is added to the disk (in it's own partition). Use case: - Launch yast - bootloader - Make settings at: - boot code location tab - kernel tab - options tab - Press 'next' - Perform checks if OK: - provide summary screen - press continue: creates the grub config and update the boot code if NOK - Show error and go back -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018259 Bug ID: 1018259 Summary: VUL-0: CVE-2017-5180: firejail: local root exploit Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other URL: https://smash.suse.de/issue/178257/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software Assignee: tiwai(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de CC: krahmer(a)suse.com, tiwai(a)suse.com Found By: Security Response Team Blocker: --- courtesy bug from the SUSE security team for a package not in the distribution: from http://seclists.org/oss-sec/2017/q1/20 > * Firejail has too broad attack surface that allows users > * to specify a lot of options, where one of them eventually > * broke by accessing user-files while running with euid 0. > > const char *const ldso = "/etc/ld.so.preload"; > ... > snprintf(path, sizeof(path) - 1, "%s/.firenail/.Xauthority", home); > ... > symlink(ldso, path) https://github.com/netblue30/firejail/issues/1020 https://github.com/netblue30/firejail/commit/60d4b478f65c60bcc825bb56f85fd6… https://github.com/netblue30/firejail/commit/e74fdab5d2125ce8f058c1630ce7cc… Also note that Virtualization/firejail is at 0.9.44, while 0.9.44.2 has the following: https://firejail.wordpress.com/download-2/release-notes/ > Version 0.9.44.2, Sunday, December 4, 2016 > > security: overwrite /etc/resolv.conf found by Martin Carpenter > secuirty: TOCTOU exploit for –get and –put found by Daniel Hodson > security: invalid environment exploit found by Martin Carpenter > security: several security enhancements References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5180 http://seclists.org/oss-sec/2017/q1/21 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 994883] systemd breaks parport: No sound at reboot
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=994883 http://bugzilla.suse.com/show_bug.cgi?id=994883#c57 --- Comment #57 from Franck Bui <fbui(a)suse.com> --- The question here is: do you want to allow *any* logged users access the devices managed by avrdude or do you want to create a dedicate group (like Debian) and selectively put users in this group ? It seems that the second option is saner. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018198] devel:languages:php: Fails when getrandom syscall unavailable
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018198 http://bugzilla.suse.com/show_bug.cgi?id=1018198#c2 --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- (Of course preferably drop the non upstream patch.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018198] devel:languages:php: Fails when getrandom syscall unavailable
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018198 http://bugzilla.suse.com/show_bug.cgi?id=1018198#c1 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgajdos(a)suse.com Assignee|pgajdos(a)suse.com |crrodriguez(a)opensuse.org --- Comment #1 from Petr Gajdos <pgajdos(a)suse.com> --- These versions differ for example in php7-getrandom-test.patch presence. Christian, could you please look at it? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017778] New: bootloader is written to disk sdb, while this is not configured. System does not show the bootloader when sdb is selected.
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017778 Bug ID: 1017778 Summary: bootloader is written to disk sdb, while this is not configured. System does not show the bootloader when sdb is selected. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: richard.bos(a)xs4all.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 708204 --> http://bugzilla.opensuse.org/attachment.cgi?id=708204&action=edit y2log for only the bootloader session YaST/bootloader configured, with the options shown in the screenshot Bootloader_code_tab.jpg. There is nowhere set or mentioned (displayed) at which disk the bootloader will be stored. From the documentation [1] and help [2] I understood that the bootloader would be stored at 1st disk (sda), but according the logs the bootloaders is stored at sdb. Why? On the other hand it's something I wanted (bootloader at disk sdb) so I can test the bootloader. After booting the system and selecting the 2nd disk (sdb) there is no bootprompt at all :( Two questions: 1) Why is the bootloader saved at sdb (2nd disk) and not to the 1st? 2) The system does not boot from the saved bootloader at sdb, why? [1]: https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.re… [2]: https://bugzilla.opensuse.org/attachment.cgi?id=708132 (#1017677) y2logs attached for only this bootloader session. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1017765] [yast2/bootloader]: Make it possible to exclude foreign OS' from the bootloader menu
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017765 http://bugzilla.suse.com/show_bug.cgi?id=1017765#c6 --- Comment #6 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Richard Bos from comment #5) > Remark: it nicer although longer Operation System instead OS. There is > sufficient space to write it full. > > As such the current 'Probe for foreign OS' can be become: > Probe for foreign Operating System > or > Probe for other installed Operating Systems. Just do not forget about ncurses and minimal terminal which is 80x24 chars. I am thinking for text like "Find and add to menu other OSes" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1011053] Rebooting takes a long time because dmeventd refuses to exit (LVM thin volume)
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1011053 GuoQing Jiang <gqjiang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gqjiang(a)suse.com |zren(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 846807] 131.1 RC1 - I managed to destroy a btrfs - anyone wants to investigate it?
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=846807 http://bugzilla.opensuse.org/show_bug.cgi?id=846807#c11 Libor Pechacek <lpechacek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #11 from Libor Pechacek <lpechacek(a)suse.com> --- Thanks for the confirmation, Carlos! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003886] systemd-sysctl Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1003886 http://bugzilla.suse.com/show_bug.cgi?id=1003886#c4 Michal Kubeček <mkubecek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmueller(a)suse.com, | |ro(a)suse.com, vuntz(a)suse.com --- Comment #4 from Michal Kubeček <mkubecek(a)suse.com> --- /proc/sys/net/bridge only exists when bridge module is loaded. So I guess the problem here is that either bridge module is not loaded at all (it isn't unless someone needs it) or it is loaded after sysctl files are processed. If someone really wants to override the default, install directive in modprobe.conf is probably the way to go. That being said, I find the reasoning in bsc#845496 rather weak (and the comment in sysctl file misleading) and I don't see any mention there that the change was intended to affect anything else than cloud setups. Therefore I find very disturbing that such change was imposed on all openSUSE and SLE systems without discussing this with networking developers first (or at least telling them). And also without testing, apparently. -- You are receiving this mail because: You are on the CC list for the bug.

1 0