April 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-en] Problem with /etc/resolv.conf
by Carlos E. R. 06 Apr '23

06 Apr '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My resolv.conf file on new laptop contains: Laicolasse:~ # cat /etc/resolv.conf ### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf ### autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. search Laicolasse.valinor nameserver 80.58.61.254 nameserver 80.58.61.250 Laicolasse:~ # It is not reading those variables: Laicolasse:~ # grep "NETCONFIG_DNS_STATIC_SEARCHLIST\|NETCONFIG_DNS_STATIC_SERVERS\|NETCONFIG_DNS_FORWARDER\|NETCONFIG_DNS_POLICY" /etc/sysconfig/network/config NETCONFIG_DNS_POLICY="auto" NETCONFIG_DNS_FORWARDER="resolver" NETCONFIG_DNS_FORWARDER_FALLBACK="yes" NETCONFIG_DNS_STATIC_SEARCHLIST="valinor valinor" # When the NETCONFIG_DNS_FORWARDER variable is set to "resolver", NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1" Laicolasse:~ # On my older laptop, it works: Legolas:~ # cat /etc/resolv.conf ### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf ### autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. search valinor Legolas.valinor nameserver 127.0.0.1 Legolas:~ # Calling that program does nothing. What am I missing? Maybe I have to write it up in the Network Manager config. I put in the wifi connection I am using [ipv4] dns=127.0.0.1; then wifi off, wifi on. Does not work. Then, I edit the information using the Netowrk Manager GUI. Now I get: ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. search Laicolasse.valinor nameserver 80.58.61.254 nameserver 80.58.61.250 nameserver 127.0.0.1 Laicolasse:~ # Which is not valid, it is still using the two servers from Telefónica. The GUI says "add", I want to replace. (the problem is that this way it is it not using dnsmasq!) The only way out I see is editing my own resolv file :-/ Done, it works. Will it survive a reboot? I guess not. :-( - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCtggRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVuU8AoJFdHVJv1rwvz1gR6PV1 /F2fcOhXAKCLZ9rIW3g/CWGzSxvdSIgDRv9vxQ== =p8Vq -----END PGP SIGNATURE-----

4 34

Re: [oS-en] Problem with /etc/resolv.conf, with intention of using dnsmasq
by kschneider bout-tyme.net 06 Apr '23

06 Apr '23

I suggest you read info on the following website to understand what (and how) the ‘search’ directive is used. It’s clearly not the way you are trying to use it. <https://www.baeldung.com/linux/etc-resolv-conf-file> [Linux-Featured-Image-12-k.png] The /etc/resolv.conf File | Baeldung on Linux<https://www.baeldung.com/linux/etc-resolv-conf-file> baeldung.com<https://www.baeldung.com/linux/etc-resolv-conf-file> Ken Schneider

5 26

make[1]: *** No rule to make target '.kernel_signing_key.pem', needed by 'certs/signing_key.x509'. Stop.
by Per Jessen 06 Apr '23

06 Apr '23

Building a kernel is not as easy as it used to be :-) On my raspi2, I'm trying to build a kernel (5.14.21) - using source from the leap 15.4 repo. It looks like $SUBJ is caused by a missing certificate for signing modules - I would like to just disable all of that, but which option is it? Andrei, any pointers? -- Per Jessen, Zürich (9.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

2 3

Re: coreutils 9.2 - breaking change in cp and mv
by Robert Webb 06 Apr '23

06 Apr '23

[Since this reply msg by me (rw) is opinion/rant, I didn't think it belongs in the Factory list, so am posting it to Users.] On Wed, 05 Apr 2023 23:16:46 +0200, mh(a)mike.franken.de wrote (to factory(a)lists.opensuse.org) > On Montag, 3. April 2023 12:00:22 CEST Dominique Leuenberger wrote: >> ==== coreutils ==== >> Version update (9.1 -> 9.2) >> Subpackages: coreutils-lang > [...] >> * 'cp -n' and 'mv -n' now exit with nonzero status if they skip >> their action because the destination exists, and likewise for 'cp >> - i', 'ln -i', and 'mv -i' when the user declines. (POSIX >> specifies this for 'cp -i' and 'mv -i'.) > [...] > > be warned: > This might break lots of Makefiles and other scripts. > cp -n and mv -n return 1, if *any* file to copy or move exists in the > destination. I'm not sure, why this was introduced, because using -n > originally should avoid a non zero return status. I say, let them break. The functionality defined for the '-n' (--no-clobber) option before was broken. It was: "Do not overwrite an existing file; silently do nothing instead." That does not allow a script or makefile to detect whether the copy or move succeeded completely. If it doesn't succeed, it should return error status. The change is too bad for the scripts and makefiles written for the old functionality, but most of them using '-n' were probably carelessly written, and were bugs waiting to happen. Seeing an error will give people an opportunity to fix it. I was happy when first becoming aware of a new --no-clobber option for these utilities, until noticing that no proper result status was returned. That made it unusable for my scripts and makefiles, and so, mine won't break from the change. "It usually does what you want" is not good enough. BTW, the '-t' and '-T' options were a welcome addition to make the behavior of cp, mv, and ln, more deterministic. In scripts, one of those two should always be used. -- Robert Webb

2 2

The latest shim from Leap 15.4 disallows shim from Tumbleweed and possibly other distributions
by Andrei Borzenkov 06 Apr '23

06 Apr '23

https://forums.opensuse.org/t/after-a-shim-update-yesterday-no-longer-able-… https://bugzilla.opensuse.org/show_bug.cgi?id=1209985 To explain. There is relatively new standard SBAT which makes it possible to "mass blacklist" EFI binaries supporting it. In rough overview, each binary carries a "generation" number which is increased when vulnerability is fixed. System has SbatLevel EFI variable which lists minimal accepted generations. Any binary which has smaller generation is rejected (by shim). What is important is that shim also verifies itself when starting. That is the general theory. Now comes implementation - there is no tool to manage SbatLevel variable directly - it is written by shim itself! At best you can select between two different values ("previous" and "latest") or reset this variable to some initial value. What "previous" and "latest" contain is entirely up to shim developers/maintainers. Initial value is empty. What happened now was the following 1. Leap 15.4 shim fixed some CVE and increased its own generation 2. Current Leap shim automatically enforces "latest" content of SbatLevel during installation which now requires at least shim generation 2 3. shim in Tumbleweed on one hand supports SBAT, on the other hand it has too old generation and so refuses to run. It also means that once you booted current Leap 15.4 shim at least once, you can no more to boot any installation image that includes shim new enough to understand SBAT but old enough to have generation 1 (like current Ubuntu shim :) ) with Secure Boot enabled. It will simply turn system off after showing error message. It is possible to mitigate it by using mokutil --set-sbat-policy previous *before* updating to the new shim. In this case new shim will set embedded previous policy that does only lists grub2. Initial policy after reset (empty, only header): sbat,1,2021030218 Policy after rebooting into new shim with "previous" set: sbat,1,2022052400 grub,2 Policy after rebooting with new shim after default installation (implicit "latest"): sbat,1,2022111500 shim,2 grub,3 As you see, even "previous" adds minimal grub requirement which may block grub from other distributions (all to protect you of course :) ). What is *NOT* possible is to tell shim to leave SbatLevel the hell alone on *my* system. Frankly the implementation looks like security theater to me, but I am not security expert ...

2 1

Zypper up kann amavisd-new und perl-razor-agents nicht updaten
by Joerg Rohrer 05 Apr '23

05 Apr '23

Hallo Liste Wie im subject geschrieben bekomme ich den amavisd-new perl-razor-agents nicht upgedatet. z.Zt ist amavis aus dem OS Repo installiert, warum auch immer. Habe bis anhin gedacht es kommt aus dem Mail repo. Postfix und cyrus stammen aus dem mail repo. habe das mal umgestellt weil cyrus nach dem update von 15.3 zu 15.4 einfach de-installiert wurde. Leider bekomme ich beim versuch zypper dup --from "Email services (15.4)" folgendes. Scheint dass das Paket perl(Net::LibIDN2) ist nirgends zu finden ist. Möchte mir den mailer nicht wieder zerschiessen darum frage ich mal hier:) Loading repository data... Reading installed packages... Computing distribution upgrade... 4 Problems: Problem: nothing provides 'perl(Net::LibIDN2)' needed by the to be installed amavisd-new-2.13.0-lp154.172.1.noarch Problem: problem with the installed libclucene-contribs-lib1-2.3.3.4-1.31.x86_64 Problem: problem with the installed libclucene-core1-2.3.3.4-1.31.x86_64 Problem: problem with the installed libclucene-shared1-2.3.3.4-1.31.x86_64 Problem: nothing provides 'perl(Net::LibIDN2)' needed by the to be installed amavisd-new-2.13.0-lp154.172.1.noarch Solution 1: deinstallation of amavisd-new-2.12.2-lp154.171.4.noarch Solution 2: keep obsolete amavisd-new-2.12.2-lp154.171.4.noarch Solution 3: break amavisd-new-2.13.0-lp154.172.1.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): zypper lr -u # | Alias | Name | Enabled | GPG Check | Refresh | URI --+-----------------------------------+----------------------------------------------------------+---------+-----------+---------+------------------------------------------------------------------ 1 | repo-${releasever}-non-oss | openSUSE-15.4 Non-OSS | Yes | (r ) Yes | No | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/ 2 | repo-${releasever}-oss | openSUSE-15.4 OSS | Yes | (r ) Yes | No | http://download.opensuse.org/distribution/leap/15.4/repo/oss/ 3 | repo-${releasever}-update-non-oss | openSUSE-15.4 Updates Non-OSS | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/non-oss/ 4 | repo-${releasever}-update-oss | openSUSE-15.4 Updates OSS | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/oss/ 5 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debug-> | No | ---- | ---- | http://download.opensuse.org/update/leap/15.4/backports_debug/ 6 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/backports/ 7 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE-> | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.4/sle/ 8 | repo-sle-update | Update repository with updates from SUSE Linux Enterpr-> | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/sle/ 9 | server_mail | Email services (15.4) | Yes | (r ) Yes | No | https://download.opensuse.org/repositories/server:/mail/15.4/ zypper se -s amavis Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------------------------+------------+---------------------+--------+------------------------------------------------------------- | amavisd-milter | package | 1.7.2-150400.9.3.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 | amavisd-milter | package | 1.7.2-lp154.5.12 | x86_64 | Email services (15.4) | amavisd-milter | srcpackage | 1.7.2-150400.9.3.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15 | amavisd-milter | srcpackage | 1.7.2-lp154.5.12 | noarch | Email services (15.4) | amavisd-milter-debuginfo | package | 1.7.2-lp154.5.12 | x86_64 | Email services (15.4) | amavisd-milter-debugsource | package | 1.7.2-lp154.5.12 | x86_64 | Email services (15.4) i+ | amavisd-new | package | 2.12.2-lp154.171.4 | noarch | (System Packages) v | amavisd-new | package | 2.13.0-lp154.172.1 | noarch | Email services (15.4) v | amavisd-new | package | 2.12.1-150400.1.4 | noarch | openSUSE-15.4 OSS v | amavisd-new | package | 2.11.1-150000.6.6.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 | amavisd-new | srcpackage | 2.13.0-lp154.172.1 | noarch | Email services (15.4) | amavisd-new | srcpackage | 2.11.1-150000.6.6.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15 i | amavisd-new-docs | package | 2.12.2-lp154.171.4 | noarch | (System Packages) v | amavisd-new-docs | package | 2.13.0-lp154.172.1 | noarch | Email services (15.4) v | amavisd-new-docs | package | 2.12.1-150400.1.4 | noarch | openSUSE-15.4 OSS v | amavisd-new-docs | package | 2.11.1-150000.6.6.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 grüsse jörg

1 1

raspberry pi / leap 15.4 / blacklisting modules
by Per Jessen 05 Apr '23

05 Apr '23

Context - I have a Raspi (raspi1) running Leap 15.0, controlling some SK6812 LEDs. Has been working very well since 15.0, but I thought it was probably time to consider an upgrade. I have a 2nd Raspi (raspi2) now running 15.4. I am having trouble getting access to the GPIO I need, and I noticed that 15.4 has a lot more miscellaneous modules being loaded. I don't seem to be able to prevent loading modules with this: /etc/modprobe.d/99-local.conf blacklist this-or-that In my limited understanding, this ought to prevent this-or-that from being loaded, but it doesn't. Any thoughts? -- Per Jessen, Zürich (6.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

2 3

Re: [oS-en] Problem with /etc/resolv.conf, with intention of using dnsmasq
by Bob Rogers 05 Apr '23

05 Apr '23

From: "Carlos E. R." <robin.listas(a)telefonica.net> Date: Wed, 5 Apr 2023 04:09:10 +0200 On 2023-04-05 01:28, Bob Rogers wrote: > From: "Carlos E. R." <> > Date: Wed, 5 Apr 2023 00:43:52 +0200 > > . . . > > It says: > > # Defines the DNS merge policy as documented in netconfig(8) manual page. > # Set to "" to disable DNS configuration. > > Then, what DNS does it write to the resolv file? > > It doesn't; this is leaves resolv.conf untouched by the automatic stuff. > (You were saying how it would be "far simpler" to write it yourself.) No. The resolv file lives in ram, in a tmpfs. Something creates it on every boot. What? Never mind what. If you use this recipe to disable the "what", then you can delete the symlink to /var/run/netconfig/resolv.conf. Then make /etc/resolv.conf an ordinary file (sorry, I did forget to mention these steps), and the system will leave it alone, and it will persist between boots. -- Bob

1 0

leap 15.4 raspi jeos - default userid/pwd ?
by Per Jessen 04 Apr '23

04 Apr '23

It supposed to be root:linux, but that doesn't work. Any ideas ? -- Per Jessen, Zürich (11.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

2 4

[oS-en] Instant message client?
by Carlos E. R. 03 Apr '23

03 Apr '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Do we have some instant message client? Something that can send a text message to a mobile phone, from a script? Say whatsapp, signal, telegram... :-? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCFgzhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVsjEAn3Ssx4aen17N/zV55ccI AZ8IwlKOAJ4403ez85yFtAbNu2cGXAAeA6yjPQ== =TouZ -----END PGP SIGNATURE-----

16 54