- openSUSE Bugs

[Bug 1231836] [MicroOS]: emergency mode after attempting to mount /.snapshots
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

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

1 0

[Bug 1231416] ZSWAP config cleanup
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

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

1 0

[Bug 1234573] New: VUL-0: CVE-2024-45337: glow: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234573 Bug ID: 1234573 Summary: VUL-0: CVE-2024-45337: glow: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/432234/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-45337:8.1:(AV:N/AC:H/PR:N/UI:N/ S:U/C:H/I:H/A:H) Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1234482 Target Milestone: --- Found By: --- Blocker: --- Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 https://github.com/golang/crypto/commit/b4f1988a35dee11ec3e05d6bf3e90b695fb… https://go.dev/cl/635315 https://go.dev/issue/70779 https://groups.google.com/g/golang-announce/c/-nPEi39gI4Q/m/cGVPJCqdAQAJ https://pkg.go.dev/vuln/GO-2024-3321 http://www.openwall.com/lists/oss-security/2024/12/11/2 https://bugzilla.redhat.com/show_bug.cgi?id=2331720 https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/45xxx/CVE-2024… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1229887] new pacakge: ZoneMinder
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229887 https://bugzilla.suse.com/show_bug.cgi?id=1229887#c5 --- Comment #5 from Nathan Cutler <ncutler(a)suse.com> --- Please submit also to openSUSE:Backports:SLE-15-SP7 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234561] New: VUL-0: CVE-2024-45337: gvisor-tap-vsock: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234561 https://bugzilla.suse.com/show_bug.cgi?id=1234561#c1 Bug ID: 1234561 Summary: VUL-0: CVE-2024-45337: gvisor-tap-vsock: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/432234/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-45337:8.1:(AV:N/AC:H/PR:N/UI:N/ S:U/C:H/I:H/A:H) Severity: Normal Priority: P5 - None Component: Security Assignee: danish.prakash(a)suse.com Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1234482 Target Milestone: --- Found By: --- Blocker: --- --- Comment #1 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 https://github.com/golang/crypto/commit/b4f1988a35dee11ec3e05d6bf3e90b695fb… https://go.dev/cl/635315 https://go.dev/issue/70779 https://groups.google.com/g/golang-announce/c/-nPEi39gI4Q/m/cGVPJCqdAQAJ https://pkg.go.dev/vuln/GO-2024-3321 http://www.openwall.com/lists/oss-security/2024/12/11/2 https://bugzilla.redhat.com/show_bug.cgi?id=2331720 https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/45xxx/CVE-2024… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234055] Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c30 --- Comment #30 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Otrebor Igorig from comment #29) > Unplugging every other device but the two monitors from the dock does not > help. The effect is still the same. > > I'm no hardware expert, but the notebook and the dock are recent enough > models that should cover the required bandwidth with ease. > > In fact, the dock is sold with the advertisement of being able to serve four > monitors (1xHDMI, 2xDP, 1xUSB-C). And the test with another notebook showed > that serving the two monitors with both in resolution 3840x2160 works. So I > would exclude the dock from the problem domain. > > The notebook specs linked above by Intel also suggest that this should work. > The notebook and the dock are linked by a Thunderbolt 4 spec cable, which > also should support this setup. So, where does this bandwidth limitation > come from? Yes, it should work with the setup you have. I believe the DP MST calculation in the i915 driver is the problem. It doesn't find enough bandwidth for the setup which makes me thing the bandwidth calculation is wrong. It could also be a problem in the Thunderbolt driver. Hopefully we can find the fix in newer kernels. If you have a HDMI cable of decent quality you can try connecting one of the displays with HDMI and the other with DP (try both ports). That should eliminate the need for DP MST to be used. It might be a workaround while we search for the real fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223444] New virt-v2v dependency on btrfsprogs causes error with zypper dup on systems without btrfs installed
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223444 https://bugzilla.suse.com/show_bug.cgi?id=1223444#c13 --- Comment #13 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:4335-1: An update that contains one feature and has one fix can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-ru-20244335-1 Category: recommended (moderate) Bug References: 1223444 Jira References: PED-6305 Maintenance Incident: [SUSE:Maintenance:36437](https://smelt.suse.de/incident/36437/) Sources used: openSUSE Leap 15.6 (src): guestfs-tools-1.52.2-150600.4.3.2, libguestfs-1.52.2-150600.4.3.3 Server Applications Module 15-SP6 (src): guestfs-tools-1.52.2-150600.4.3.2, libguestfs-1.52.2-150600.4.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231048] New: systemd-experimental: error message about homed
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231048 Bug ID: 1231048 Summary: systemd-experimental: error message about homed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I install systemd-experimental I get the following error message: Failed to preset unit: Unit systemd-homed.service does not exist systemd-homed is not part of systemd-experimental. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234620] [SELinux] virt-manager fails with AVC denial
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234620 Cathy Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234448] When sharing Yubikey from the host, I get "can't set config #1, error -32"
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234448 https://bugzilla.suse.com/show_bug.cgi?id=1234448#c6 Alberto Planas Dominguez <aplanas(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #6 from Alberto Planas Dominguez <aplanas(a)suse.com> --- Ahhh that was it. fuser report me the process in my host that kept the USB locked. It was pcscd, a service that uses another kind of USB devices to read smart cards. Once I stopped the service both redirector worked! Thanks Fabian! -- You are receiving this mail because: You are on the CC list for the bug.

1 0