December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193282] grub2 sbat security contact
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193282 https://bugzilla.suse.com/show_bug.cgi?id=1193282#c7 --- Comment #7 from Ludwig Nussel <lnussel(a)suse.com> --- Btw, how about SLE vs Leap. Is it expected to reuse the identical SLE binary on Leap in this case? Ie the SBAT values would say SLE then. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175908] New: encrypted rootfs does not boot anymore
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1175908 Bug ID: 1175908 Summary: encrypted rootfs does not boot anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: koenig(a)linux.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since quite a while initrd for newer kernel do not boot/mount my encrypted rootfs anymore. I'm still running kernel 5.3.12-2-default. first time I tried to boot new kernel and failed was with kernel-default-5.5.7-1.1, then later with kernel-default-5.7.1-1.2 and now with kernel-default-5.8.0-1.1 these are the messages from journalctl for the failed boot of 5.8.0: Aug 28 21:13:23 hl systemd[1]: Found device Samsung_SSD_850_EVO_2TB 5. Aug 28 21:13:23 hl systemd[1]: Found device Samsung_SSD_850_EVO_2TB 3. Aug 28 21:13:23 hl systemd[1]: Reloading. Aug 28 21:13:23 hl systemd[1]: Starting Cryptography Setup for cr_sda5... Aug 28 21:13:23 hl systemd[1]: Started Forward Password Requests to Plymouth. Aug 28 21:13:32 hl systemd-cryptsetup[433]: Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/sda5. Aug 28 21:13:32 hl systemd-cryptsetup[433]: device-mapper: reload ioctl on failed: No such file or directory Aug 28 21:13:32 hl systemd-cryptsetup[433]: Failed to activate with specified passphrase: Invalid argument Aug 28 21:13:32 hl systemd[1]: systemd-cryptsetup(a)cr_sda5.service: Main process exited, code=exited, status=1/FAILURE Aug 28 21:13:32 hl systemd[1]: systemd-cryptsetup(a)cr_sda5.service: Failed with result 'exit-code'. Aug 28 21:13:32 hl systemd[1]: Failed to start Cryptography Setup for cr_sda5. Aug 28 21:13:32 hl systemd[1]: Dependency failed for Local Encrypted Volumes. Aug 28 21:13:32 hl systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. and here the msgs for successfully booting into 5.3.12-2 again: Aug 28 23:29:19 hl systemd[1]: Found device Samsung_SSD_850_EVO_2TB 5. Aug 28 23:29:19 hl systemd[1]: Found device Samsung_SSD_850_EVO_2TB 3. Aug 28 23:29:19 hl systemd[1]: Starting Cryptography Setup for cr_sda5... Aug 28 23:29:19 hl systemd[1]: Reloading. Aug 28 23:29:19 hl systemd[1]: Started Forward Password Requests to Plymouth. Aug 28 23:29:25 hl systemd-cryptsetup[476]: Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/sda5. Aug 28 23:29:26 hl systemd[1]: Finished Cryptography Setup for cr_sda5. Aug 28 23:29:26 hl systemd[1]: Reached target Local Encrypted Volumes. both initrd are freshly created with up-to-date dracut: -rw------- 1 root root 18584060 Aug 28 23:10 /boot/initrd-5.8.0-1-default -rw------- 1 root root 17643032 Aug 28 23:11 /boot/initrd-5.3.12-2-default what is "missing" in this msg in between "on" and "failed:" (between the two extra spaces)? Aug 28 21:13:32 hl systemd-cryptsetup[433]: device-mapper: reload ioctl on failed: No such file or directory ^^^ -- You are receiving this mail because: You are on the CC list for the bug.

1 37

[Bug 1193261] Leap15.3: Inkscape won´t start
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

1 0

[Bug 1193282] grub2 sbat security contact
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193282 https://bugzilla.suse.com/show_bug.cgi?id=1193282#c6 --- Comment #6 from Ludwig Nussel <lnussel(a)suse.com> --- Yes, it's in https://github.com/systemd/systemd/blob/main/src/boot/efi/secure-boot.c In systemd it's called SBAT_DISTRO SBAT_DISTRO_GENERATION SBAT_DISTRO_SUMMARY SBAT_DISTRO_URL As can be seen in https://github.com/systemd/systemd/blob/main/src/boot/efi/meson.build systemd tries to fill in values from /etc/os-release which doesn't work as we have dummy-release in the build root. ID -> SBAT_DISTRO NAME -> SBAT_DISTRO_SUMMARY BUG_REPORT_URL -> SBAT_DISTRO_URL on TW that would be NAME="openSUSE Tumbleweed" ID="opensuse-tumbleweed" BUG_REPORT_URL="https://bugs.opensuse.org" does it make sense to take that scheme? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192672] devel:languages:php/php8: Bug /etc/php8/fpm/php.ini is not created
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192672 https://bugzilla.suse.com/show_bug.cgi?id=1192672#c3 --- Comment #3 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Arjen de Korte from comment #2) > No, this is an additional bug, not a duplicate. Yes, you are right. Sorry. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193272] devel:libraries:c_c++/libffi causes fallout in Staging:A
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

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

1 0

[Bug 1140772] New: openconnect: please update vpnc-script
by bugzilla_noreply＠novell.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1140772 Bug ID: 1140772 Summary: openconnect: please update vpnc-script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gernot(a)hillier.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current openconnect package from openSUSE:factory still includes a vpnc-script dating back at least 2 years (file date according to OBS: 2017-09-22, see https://build.opensuse.org/package/show/network/openconnect). Please update this file to a current version from the vpnc-script repository of David Woodhouse (openconnect author), see http://git.infradead.org/users/dwmw2/vpnc-scripts.git/blob/refs/heads/maste…. This brings a lot of improvements for non-trivial network setups, IPv6 etc., see http://git.infradead.org/users/dwmw2/vpnc-scripts.git/shortlog - including necessary extensions we need for using OpenConnect at Siemens. :) Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1180387] Dracut package misses dependency for purge-kernels-service
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1180387 https://bugzilla.suse.com/show_bug.cgi?id=1180387#c1 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |antonio.feijoo(a)suse.com Resolution|--- |WONTFIX --- Comment #1 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Sorry for the lack of response here. We are cleaning up old bug entries, the current version of Leap is 15.3, so this cannot be reproduced anymore. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1140772] openconnect: please update vpnc-script
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1140772 https://bugzilla.suse.com/show_bug.cgi?id=1140772#c3 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Dirk Mueller <dmueller(a)suse.com> --- forwarded to factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193282] grub2 sbat security contact
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193282 https://bugzilla.suse.com/show_bug.cgi?id=1193282#c5 --- Comment #5 from Michael Chang <mchang(a)suse.com> --- (In reply to Ludwig Nussel from comment #2) > btw, the data in SBAT I suppose needs to comply to certain standards. Would > it be possible to package that data in a form consumable by other packages? https://github.com/rhboot/shim/blob/main/SBAT.md#generation-based-revocatio… > I just noticed that systemd will need the data in the future. Is it systemd-boot ? It seems to request for Microsoft signing recently. > I guess we > should avoid duplicating it. > Could be as simple as rpm macros or some shell sourceable config. Yes defining rpm marcos for common sbat vaules would be helpful, eg vendor_name and vendor_url. -- You are receiving this mail because: You are on the CC list for the bug.

1 0