February 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192937] VUL-0: CVE-2021-21899: libdxfrw: heap out-of-bounds write in dwgCompressor:copyCompBytes21
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1192937 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jslaby(a)suse.com |security-team(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192938] VUL-0: CVE-2021-21900: libdxfrw: use-after-free in dxfRW:processLType()
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1192938 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jslaby(a)suse.com |security-team(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192936] VUL-0: CVE-2021-21898: libdxfrw: out-of-bounds write in dwgCompressor:decompress18()
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1192936 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Assignee|jslaby(a)suse.com |security-team(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c27 --- Comment #27 from Victor Zhestkov <victor.zhestkov(a)suse.com> --- Hi Takashi. Installed the patched kernel yesterday. But I booted the system only once since installing it. Now it works, but I'll put additionall comments if it will be ok or not on the next boots. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195412] smb does not start if openSUSE-SLE-15.3-2022-283 is installed and smb.conf has printers set up
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195412 https://bugzilla.suse.com/show_bug.cgi?id=1195412#c4 --- Comment #4 from Andreas Osterburg <andreas.osterburg(a)digide.net> --- (In reply to Mathias Homann from comment #3) > (In reply to Mathias Homann from comment #2) > > (In reply to Andreas Osterburg from comment #1) > > > Same here. It seems that apparmor is the problem. > > > > > > My workaround: > > > > > > Add the following two lines to /etc/apparmor.d/local/usr.sbin.smbd > > > > > > /usr/lib64/samba/samba-bgqd ix, > > > /run/samba/samba-bgqd.pid rw, > > > > > > and reload the appamor profile > > > > > > /sbin/apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd > > actually: > > akari:~ # /sbin/apparmor_parser -r /etc/apparmor.d/local/usr.sbin.smbd > AppArmor-Analysefehler f?r /etc/apparmor.d/local/usr.sbin.smbd in > /etc/apparmor.d/local/usr.sbin.smbd in Zeile 2: syntax error, unexpected > TOK_MODE, expecting TOK_OPEN You cannot load just the local part, you have to include the whole profile: /sbin/apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd (without "local") You can test whether unconfined mode "ux" works instead of "ix", but the forked process has no security constraints then. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195391] identify and declare bash dependencies explicitly
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195391 http://bugzilla.opensuse.org/show_bug.cgi?id=1195391#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1195391) was mentioned in https://build.opensuse.org/request/show/950645 Factory / ncurses -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195412] smb does not start if openSUSE-SLE-15.3-2022-283 is installed and smb.conf has printers set up
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195412 https://bugzilla.suse.com/show_bug.cgi?id=1195412#c3 --- Comment #3 from Mathias Homann <Mathias.Homann(a)opensuse.org> --- (In reply to Mathias Homann from comment #2) > (In reply to Andreas Osterburg from comment #1) > > Same here. It seems that apparmor is the problem. > > > > My workaround: > > > > Add the following two lines to /etc/apparmor.d/local/usr.sbin.smbd > > > > /usr/lib64/samba/samba-bgqd ix, > > /run/samba/samba-bgqd.pid rw, > > > > and reload the appamor profile > > > > /sbin/apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd actually: akari:~ # /sbin/apparmor_parser -r /etc/apparmor.d/local/usr.sbin.smbd AppArmor-Analysefehler f?r /etc/apparmor.d/local/usr.sbin.smbd in /etc/apparmor.d/local/usr.sbin.smbd in Zeile 2: syntax error, unexpected TOK_MODE, expecting TOK_OPEN -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195412] smb does not start if openSUSE-SLE-15.3-2022-283 is installed and smb.conf has printers set up
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195412 https://bugzilla.suse.com/show_bug.cgi?id=1195412#c2 --- Comment #2 from Mathias Homann <Mathias.Homann(a)opensuse.org> --- (In reply to Andreas Osterburg from comment #1) > Same here. It seems that apparmor is the problem. > > My workaround: > > Add the following two lines to /etc/apparmor.d/local/usr.sbin.smbd > > /usr/lib64/samba/samba-bgqd ix, > /run/samba/samba-bgqd.pid rw, > > and reload the appamor profile > > /sbin/apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd > > That works for me. > > Another solution is (if applicable) disabling spoolss in global section of > smb.conf: > > disable spoolss = yes I did the apparmor workaround, now my samba server does not have any printers anymore. Rolling back to the previous one instead... again... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195360] Kernel 5.16.1-1 PAM issue after upgrading from 20220101 to 20220121
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195360 https://bugzilla.suse.com/show_bug.cgi?id=1195360#c13 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- Pushed the fix to master+stable. It will appear in TW soon (in ~ a week). You can use Kernel:stable in the meantime (the fix will appear there today) or at least confirm the fix works for you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195395] hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 https://bugzilla.suse.com/show_bug.cgi?id=1195395#c17 --- Comment #17 from Dirk Mueller <dmueller(a)suse.com> --- (In reply to Dirk Mueller from comment #16) > My current guess is that pmf=2 would make you able to connect again. it appears that in the protocol handshake, the AP (fritzbox) is declaring to not require protected management frames. which is sort of true, it doesn't require it in WPA2 mode. However by specification WPA3 is always with PMF enabled, and it appears wpa_supplicant would have to ignore the AP advice and connect in SAE mode with PMF enabled. pmf=2 forces PMF even if the AP says it doesn't require it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0