October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1200182] New: systemd-resolved cannot bind port 53
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200182 Bug ID: 1200182 Summary: systemd-resolved cannot bind port 53 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: paul(a)pbarker.dev QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh installation of OpenSUSE MicroOS, I have attempted to switch to systemd-networkd and systemd-resolved to manage my network connections following the instructions in https://en.opensuse.org/Network_Management_With_Systemd. However, when trying to enable systemd-resolved I hit an error: alpha:~ # systemctl enable --now systemd-resolved Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service �� /usr/lib/systemd/system/systemd-resolved.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service �� /usr/lib/systemd/system/systemd-resolved.service. Job for systemd-resolved.service failed because the control process exited with error code. See "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details. alpha:~ # journalctl -xeu systemd-resolved.service �� Subject: Automatic restarting of a unit has been scheduled �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for �� the configured Restart= setting for the unit. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Stopped Network Name Resolution. �� Subject: A stop job for unit systemd-resolved.service has finished �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A stop job for unit systemd-resolved.service has finished. �� The job identifier is 1376 and the job result is done. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Starting Network Name Resolution... �� Subject: A start job for unit systemd-resolved.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit systemd-resolved.service has begun execution. �� The job identifier is 1376. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Positive Trust Anchors: Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.> Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Using system hostname 'alpha.cephei.uk'. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to listen on UDP socket 127.0.0.53:53: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to start manager: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit systemd-resolved.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Failed to start Network Name Resolution. It appears that the permission denied errors when systemd-resolved tried to bind port 53 are caused by SELinux. I confirmed that this is the case by disabling SELinux and retrying the command - this resulted in systemd-resolved successfully starting. Therefore I think there is an error in the SELinux policy here - systemd-resolved should be able to bind port 53 on localhost to offer DNS resolution services. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202351] New: dracut: remove mkinitrd wrapper
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202351 Bug ID: 1202351 Summary: dracut: remove mkinitrd wrapper Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1203019] New: yast2: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203019 Bug ID: 1203019 Summary: yast2: replace mkinitrd wrapper with native dracut 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: antonio.feijoo(a)suse.com QA Contact: jsrain(a)suse.com Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. References: - yast2 /usr/share/YaST2/modules/Initrd.rb:72: # parametr for mkinitrd because of splash screen /usr/share/YaST2/modules/Initrd.rb:75: # Additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:391: "/lib/mkinitrd/scripts/setup-splash.sh" /usr/share/YaST2/modules/Initrd.rb:400: "/sbin/mkinitrd %1 %2 >> %3 2>&1", /usr/share/YaST2/modules/Initrd.rb:405: File.join(Directory.logdir, "y2logmkinitrd").shellescape /usr/share/YaST2/modules/Initrd.rb:411: Ops.add(Directory.logdir, "/y2logmkinitrd") /usr/share/YaST2/modules/Initrd.rb:434: # Set the -s parameter of mkinitrd /usr/share/YaST2/modules/Initrd.rb:463: # Get additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:464: # @return [String] additional mkinitrd parameters /usr/share/YaST2/modules/Initrd.rb:469: # Set additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:470: # @param [String] params string additional mkinitrd parameters # rpm -qf /usr/share/YaST2/modules/Initrd.rb yast2-4.5.10-1.1.x86_64 - yast2-country /usr/share/YaST2/modules/Timezone.rb:85: # if mkinitrd should be called at the end /usr/share/YaST2/modules/Timezone.rb:86: @call_mkinitrd = false /usr/share/YaST2/modules/Timezone.rb:467: Builtins.y2milestone("calling mkinitrd...") /usr/share/YaST2/modules/Timezone.rb:470: "/sbin/mkinitrd >> /var/log/YaST2/y2logmkinitrd 2>> /var/log/YaST2/y2logmkinitrd" /usr/share/YaST2/modules/Timezone.rb:860: CallMkinitrd() if @call_mkinitrd && !Stage.initial /usr/share/YaST2/modules/Timezone.rb:1081: publish :variable => :call_mkinitrd, :type => "boolean" # rpm -qf /usr/share/YaST2/modules/Timezone.rb yast2-country-4.5.1-1.1.x86_64 - yast2-kdump /usr/share/YaST2/modules/Kdump.rb:419: update_command = (using_fadump? ? "/usr/sbin/mkdumprd -f" : "/sbin/mkinitrd") /usr/share/YaST2/modules/Kdump.rb:426: update_logfile = File.join(Directory.logdir, "y2logmkinitrd") # rpm -qf /usr/share/YaST2/modules/Kdump.rb yast2-kdump-4.5.3-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1175219] New: OpenVPN fails with certificates on smart cards on Leap 15.2 and TW
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1175219 Bug ID: 1175219 Summary: OpenVPN fails with certificates on smart cards on Leap 15.2 and TW Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from Leap 15.1 to Leap 15.2 working OpenVPN setups with PKCS11 certificates on Yubikeys are failing. The same applies to openSUSE Tumbleweed. Also other smart card devices may be affected. OpenVPN does not show many details, even with highest logging level. # openvpn --cd /etc/openvpn --config openvpn-yubikey-test.ovpn [...] Thu Aug 13 10:21:21 2020 VERIFY OK: depth=1, CN=Test CA Thu Aug 13 10:21:21 2020 VERIFY KU OK Thu Aug 13 10:21:21 2020 Validating certificate extended key usage Thu Aug 13 10:21:21 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Thu Aug 13 10:21:21 2020 VERIFY EKU OK Thu Aug 13 10:21:21 2020 VERIFY OK: depth=0, CN=host1.example.com Thu Aug 13 10:21:21 2020 OpenSSL: error:141F0006:SSL routines:tls_construct_cert_verify:EVP lib Thu Aug 13 10:21:21 2020 TLS_ERROR: BIO read tls_read_plaintext error Thu Aug 13 10:21:21 2020 TLS Error: TLS object -> incoming plaintext read error Thu Aug 13 10:21:21 2020 TLS Error: TLS handshake failed Thu Aug 13 10:21:21 2020 Fatal TLS error (check_tls_errors_co), restarting Thu Aug 13 10:21:21 2020 SIGUSR1[soft,tls-error] received, process restarting Thu Aug 13 10:21:21 2020 Restart pause, 5 second(s) The bug can be resolved by upgrading the pkcs11-helper packages from pkcs11-helper-1.25.1 to pkcs11-helper-devel-1.26.0. # openvpn --cd /etc/openvpn --config openvpn-yubikey-test.ovpn [...] Thu Aug 13 10:32:36 2020 VERIFY OK: depth=1, CN=Test CA Thu Aug 13 10:32:36 2020 VERIFY KU OK Thu Aug 13 10:32:36 2020 Validating certificate extended key usage Thu Aug 13 10:32:36 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Thu Aug 13 10:32:36 2020 VERIFY EKU OK Thu Aug 13 10:32:36 2020 VERIFY OK: depth=0, CN=host1.example.com Enter user1 token Password: (press TAB for no echo) There is a problem with inconsistent padding between OpenSSL 1.1.1 and pkcs11-helper-1.25.1. The details are described here: http://openssl.6102.n7.nabble.com/Issue-with-smartcard-authentication-for-o… The pkcs11-helper-devel-1.26.0 Changelog contains this line: - openssl: support RSA_NO_PADDING padding, thanks to Selva Nair -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1201144] New: Use KDE Discover to perform Distro Upgrades
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201144 Bug ID: 1201144 Summary: Use KDE Discover to perform Distro Upgrades Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: johnmaverick74(a)mail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Would be great to have Discover notifying the user when a new Distribution Upgrade becames available and being able to perform that upgrade (thru a GUI) similar to what happens in Kubuntu, Neon and soon Fedora KDE [0]. There was a project implementing this in Leap's GNOME software: [1] and [2] *[0] https://pagure.io/fedora-kde/SIG/issue/3 *[1] https://hackweek.opensuse.org/21/projects/implement-gnome-softwares-distrib… *[2] https://github.com/PackageKit/PackageKit/commit/930dd201b1da348f2a0ee7421c1… Other related Links: https://bugzilla.opensuse.org/show_bug.cgi?id=1197938 https://bugs.kde.org/show_bug.cgi?id=451849 https://hackweek.opensuse.org/projects/easy-opensuse-upgrade -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1196225] New: webcamoid wants to download binaries from the internet
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196225 Bug ID: 1196225 Summary: webcamoid wants to download binaries from the internet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: aloisio(a)gmx.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in settings->video->outputs the install button wants to download and run https://github.com/webcamoid/akvcam/releases/download/1.2.2/akvcam-linux-1.… That's not ok in openSUSE. Would it be possible to redirect the call to packagekit instead to make it install a distro package for the software in question? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1157881] New: mount.nfs improve error reporting: "Connection *WHERE*TO* timed out"
by bugzilla_noreply＠novell.com 28 Mar '23

28 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1157881 Bug ID: 1157881 Summary: mount.nfs improve error reporting: "Connection *WHERE*TO* timed out" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: 7eggert(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When one of the nfs mounts times out, it gets reported as "Connection timed out". This is semi-helpful and thus semi-qualifies as a bug as well as a feature request. Please forward this to upstream. (Also not being able to mount triggers a bug in systemd to unmount unrelated mounts. One of my nfs servers is currently unresponsive but the other servers do work, yet systemd unmounts several other mounts. mount.nfs not reporting the cause didn't help me to find the cause.) -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1204445] New: osc is broken since last update
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204445 Bug ID: 1204445 Summary: osc is broken since last update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I wanted to checkout a repository on my old Leap system. The last update of osc has broken osc. You can not checkout or anything else any more. kriesch@linux-yscv:~/home:AdaLovelace> osc bsc python-lupa > pruning cache > pruned 0 files comprised of 0 bytes Traceback (most recent call last): File "/usr/bin/osc", line 43, in <module> osccli = commandline.Osc() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 92, in __init__ self._load_plugins() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 9604, in _load_plugins mod = imp.load_source(modname, os.path.join(plugin_dir, extfile)) File "/usr/lib64/python3.6/imp.py", line 172, in load_source module = _load(spec) File "<frozen importlib._bootstrap>", line 684, in _load File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib/osc-plugins/osc-staging.py", line 17, in <module> from osclib.accept_command import AcceptCommand File "/usr/lib/osc-plugins/osclib/accept_command.py", line 14, in <module> from osclib.pkglistgen_comments import PkglistComments File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 48, in <module> class PkglistComments: File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 168, in PkglistComments def is_approved(self, comment, comments: dict) -> str | None: TypeError: unsupported operand type(s) for |: 'type' and 'NoneType' skriesch@linux-yscv:~/home:AdaLovelace:branches:devel:languages:misc> osc bco python-lupa Traceback (most recent call last): File "/usr/bin/osc", line 43, in <module> osccli = commandline.Osc() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 92, in __init__ self._load_plugins() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 9604, in _load_plugins mod = imp.load_source(modname, os.path.join(plugin_dir, extfile)) File "/usr/lib64/python3.6/imp.py", line 172, in load_source module = _load(spec) File "<frozen importlib._bootstrap>", line 684, in _load File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib/osc-plugins/osc-staging.py", line 17, in <module> from osclib.accept_command import AcceptCommand File "/usr/lib/osc-plugins/osclib/accept_command.py", line 14, in <module> from osclib.pkglistgen_comments import PkglistComments File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 48, in <module> class PkglistComments: File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 168, in PkglistComments def is_approved(self, comment, comments: dict) -> str | None: TypeError: unsupported operand type(s) for |: 'type' and 'NoneType' skriesch@linux-yscv:~> osc co openSUSE:Factory:zSystems/python-lupa Traceback (most recent call last): File "/usr/bin/osc", line 43, in <module> osccli = commandline.Osc() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 92, in __init__ self._load_plugins() File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 9604, in _load_plugins mod = imp.load_source(modname, os.path.join(plugin_dir, extfile)) File "/usr/lib64/python3.6/imp.py", line 172, in load_source module = _load(spec) File "<frozen importlib._bootstrap>", line 684, in _load File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib/osc-plugins/osc-staging.py", line 17, in <module> from osclib.accept_command import AcceptCommand File "/usr/lib/osc-plugins/osclib/accept_command.py", line 14, in <module> from osclib.pkglistgen_comments import PkglistComments File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 48, in <module> class PkglistComments: File "/usr/lib/osc-plugins/osclib/pkglistgen_comments.py", line 168, in PkglistComments def is_approved(self, comment, comments: dict) -> str | None: TypeError: unsupported operand type(s) for |: 'type' and 'NoneType' -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1127591] New: zypper option "ssl_capath" not working for mirror URLs from metalink file
by bugzilla_noreply＠novell.com 28 Mar '23

28 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1127591 Bug ID: 1127591 Summary: zypper option "ssl_capath" not working for mirror URLs from metalink file Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: cunix(a)bitmessage.ch QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- Using zypper (version: 1.14.12) for the update repository of openSUSE Leap 15.0 with the option baseurl=https://download.opensuse.org/update/leap/15.0/oss/?proxy=127.0.0.1… does not use the here configured trusted root certificates for mirror URLs, probably retrieved from a metalink file. The configured path is used for the initial connection to download.opensuse.org but following requests to mirrors seem to fallback to the system trusted certs from /etc/ssl/certs. If the mirrors' root CA is trusted in "ssl_capath=/path/to/directory/with/c_rehash/rootCAs" but not in /etc/ssl/certs, zypper,libzypp, multi-curl or something else aborts the TLS-Handshake with failure "Unknown CA (48)" and falls futher back to http (without transport layer encryption). Question for cc'ed security-team to answer: If using clear text is considered a security flaw where zypper is configured to use (https-)encryption, this might have security implications. Some Scenarios: Assume download.opensuse.org is signed by CA A and the mirror by CA B Assume further, ssl_capath=/path/to/directory/with/c_rehash/rootCAs is directory C and directory D is /etc/ssl/certs 1. If C includes A and B and in D at least B is not available, I would expect zypper to encrypt both connection, but the request to the mirror is not. 2. If A is not in C, no data (meta link file) is retrieved and therefore no mirror is connected - Good! No fallback of looking for A in D occurs. 3. If A is in C and B in D, both connections are encrypted. 4. If A is in C and B not in C and not in D, the mirror is contacted unencrypted - here I'm unsure if using plain text in this scenario is correct or if it should fail. So, in my opinion, 1. is the bug, 3. a workaround and 4. perhaps needs a zypper option to configure, if clear text fallback should be allowed. Another question is, if /etc/ssl/certs should actually be consulted when the option "ssl_capath" is used and pointing to a different directory. https://bugzilla.opensuse.org/show_bug.cgi?id=933839 might be related (similar setup). Problem and solution might be similar, too. By the way, is there a debugging option to dump the traffic from inside the encrypted connection? Especially being able to read the metalink file with the listed mirrors is of interest. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1204559] New: /proc/sys/kernel/random/poolsize is in bits, not bytes
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1204559 Bug ID: 1204559 Summary: /proc/sys/kernel/random/poolsize is in bits, not bytes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: snwint(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- yast copies the entropy pool during installation. But the pool size is actually provided in bits, not bytes, as this code assumes: https://github.com/yast/yast-installation/blob/master/src/lib/installation/… See docs: https://docs.kernel.org/admin-guide/sysctl/kernel.html#random -- You are receiving this mail because: You are on the CC list for the bug.

1 4