May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184428] New: VUL-0: CVE-2021-21404: syncthing: relay server `strelaysrv` can be caused to crash and exit by sending a relay message with a negative length field
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184428 Bug ID: 1184428 Summary: VUL-0: CVE-2021-21404: syncthing: relay server `strelaysrv` can be caused to crash and exit by sending a relay message with a negative length field Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/281245/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-21404 Syncthing is a continuous file synchronization program. In Syncthing before version 1.15.0, the relay server `strelaysrv` can be caused to crash and exit by sending a relay message with a negative length field. Similarly, Syncthing itself can crash for the same reason if given a malformed message from a malicious relay server when attempting to join the relay. Relay joins are essentially random (from a subset of low latency relays) and Syncthing will by default restart when crashing, at which point it's likely to pick another non-malicious relay. This flaw is fixed in version 1.15.0. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-21404 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21404 https://github.com/syncthing/syncthing/commit/fb4fdaf4c0a79c22cad000c42ac13… https://github.com/syncthing/syncthing/releases/tag/v1.15.0 https://github.com/syncthing/syncthing/security/advisories/GHSA-x462-89pf-6… https://pkg.go.dev/github.com/syncthing/syncthing -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1185572] New: yast2-ruby-bindings fails test suite when using tmux 3.2
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185572 Bug ID: 1185572 Summary: yast2-ruby-bindings fails test suite when using tmux 3.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- tmux 3.2 has been submitted for integration into Tumbleweed In staging, we have seen yast2-ruby-bindings failing the test suite though: [ 76s] 28: error creating /run/tmux/399 (No such file or directory) [ 77s] 28: error creating /run/tmux/399 (No such file or directory) [ 77s] 28: error creating /run/tmux/399 (No such file or directory) [ 77s] 28: error creating /run/tmux/399 (No such file or directory) The test suite intentionally declares TMUX_TMPDIR=/tmp in order to not rely on systems creating the /run/tmux structure But with tmux 3.2 as submitted, this is no longer functional -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123411] New: falkon browser seeks libs in /usr/bin
by bugzilla_noreply＠novell.com 03 May '21

03 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1123411 Bug ID: 1123411 Summary: falkon browser seeks libs in /usr/bin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: j.reitsma(a)hccnet.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The fakon browser complains about /usr/bin/libGLESv2.so not being available. When I, just to see what would happen, copie the GLES lib from /usr/lib64 to /usr/bin, falkon complains about /usr/bin/libEGL.so not being found. These libs should be searched in /usr/lib64, not in /usr/bin/ -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1185520] coreutils testsuite fails on 1-core VM
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185520 https://bugzilla.suse.com/show_bug.cgi?id=1185520#c1 Raymund Will <rw(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann(a)suse.com, | |mail(a)bernhard-voelker.de Flags| |needinfo?(bwiedemann(a)suse.c | |om) --- Comment #1 from Raymund Will <rw(a)suse.com> --- Would you mind to re-test with SR#889683, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185115] YaST Autoinstallation Configuration - Cloning: internal error in User and Group Management
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185115 https://bugzilla.suse.com/show_bug.cgi?id=1185115#c6 --- Comment #6 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- Should be fixed by yast2-users-4.3.11 SR: https://build.suse.de/request/show/240509 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185570] New kernel breaks bcache mounted rootfs
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185570 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |diego.ercolani(a)gmail.com Flags| |needinfo?(diego.ercolani@gm | |ail.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185570] New kernel breaks bcache mounted rootfs
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185570 https://bugzilla.suse.com/show_bug.cgi?id=1185570#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colyli(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you elaborate what's exactly broken and how? In anyway, adding bcache maintainer to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185115] YaST Autoinstallation Configuration - Cloning: internal error in User and Group Management
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185115 https://bugzilla.suse.com/show_bug.cgi?id=1185115#c5 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen(a)suse.com --- Comment #5 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- This was partially solved by https://github.com/yast/yast-users/pull/242 but the fix has not been submitted yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184157] JeOS Xen image: Wrong console parameters for Xen PV
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1184157 https://bugzilla.suse.com/show_bug.cgi?id=1184157#c5 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Summary|JeOS Xen image: Boot never |JeOS Xen image: Wrong |finishes without NIC |console parameters for Xen | |PV --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Ulrich Windl from comment #3) > (In reply to Fabian Vogt from comment #1) > > Is that after or before the jeos-firstboot wizard? > > I don't remember, but my guess is before the jeos-firstboot wizard. > Did you have a look at the console messages? Yes. > > My suspicion is that you only have the serial console enabled, but > > jeos-firstboot starts on tty0, so it's "invisible". Does it work if you add > > a graphical output? > > Adding graphical output woiuld be against the philosophy of JEOS IMHO. It's just for testing. I could reproduce the issue in a Xen PV VM. The issue is that it needs console=hvc0 instead. console=ttyS0 doesn't exist, and it just failed to boot because of that. So it might be necessary to add console=hvc0 to the list and implement displaying jeos-firstboot on all consoles (bug 1179157). > > Wicked should start only after completion of jeos-firstboot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185524] Changing to NetworkManager via Yast Network throws an internal error
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185524 https://bugzilla.suse.com/show_bug.cgi?id=1185524#c4 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen(a)suse.com Flags| |needinfo?(kanderssen(a)suse.c | |om) --- Comment #4 from Steffen Winterfeldt <snwint(a)suse.com> --- Knut, is this a known issue? -- You are receiving this mail because: You are on the CC list for the bug.

1 0