February 2021 - openSUSE Users - openSUSE Mailing Lists

what loads kernel modul v4l2loopback
by Simon Becherer 04 Feb '21

04 Feb '21

Hi, background: at tumbleweed, kde (but its a non platform specific question) we use i-phones with "droidcam" for webcam and sound. since about a half year with firefox. working fine. now i have to use chromium because of some jitsi servers did not accept firefox. to use chromium with the v4l2loopback driver i have to use the driver with additional options (if no option chromium did not find the webcam): rmmod v4l2loopback modprobe v4l2loopback exclusive_caps=1 will do the trick. -------------- problem: something is loading the v4l2loopback kernel modul without this option. i checked my system: inside: /etc/modules-load.d i have had a file (made by me, half year ago) who has loaded the driver without options. - i removed the file /etc/modprobe.d nothing releated to v4l2loopback /usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone /usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone now i think the system should start without v4l2loopback. restart the system lsmod shows v4l2loopback is still loaded. i insered a file at /etc/modprobe.d 50-v4l2loopback.conf with contend: options v4l2loopback exclusive_caps=1 reboot, still same problem driver is loaded without options. so what is loading this driver? i searched /etc and /usr/lib but did not find the text string "v4l2loopback" could there some udev rules? is it inside initrd ? (did i have to recreate initrd, how to do?) how to find this out, and how to delete or give this kernel-modul-load-command the option "exclusive_caps=1" simoN -- www.becherer.de

5 8

bug
by gumb 03 Feb '21

03 Feb '21

This is pretty much off-topic though it does potentially talk about an openSUSE-based PC at two ends of a connection. Just a quick, basic layman's response is all I'm looking for. Please, if this thread gets more than 10 posts long and delves into anecdotes about systems deployed in army conflicts in the 1970s, please delete it. Full paranoia tin-foil hat mode on: If, theoretically, a PC running openSUSE in one location, is communicating via encrypted video calls or SSH across the Internet, with another openSUSE PC in another location, and then the connection at one location (staffed by tech-averse personnel) mysteriously goes down, the provider then sends out an engineer who unexpectedly suggests that wiring behind the wall socket is 'draining the power', and proceeds to do some unknown work to the cabling that may hypothetically involve the covert placement of a bugging device on the line... breathe out, stay with me... Does that potentially compromise any secure connection, be it SSH, encrypted voice/video call etc. that is established between these computers, or does the encryption (provided it's strong enough) make it impossible to intercept with a physical device on the line? I'd have presumed the latter, because it's no different to trying to hack it from anywhere else, but I might be overlooking a technicality. To clarify, the PC connects to a router that is wired to a wall box serving as an 'entry point' of the connection into the property. Any such bugging device would therefore be placed between the router and the outbound cabling onto the street. gumb special agent

5 9

Learned something new - hostnamectl
by Stakanov 03 Feb '21

03 Feb '21

If you are like me and are eternally "behind" because just stumbling on new things every day using your PC. This came to may attention about a newsfeed of linuxdotcom, but no need to buy it, all resources easily found on the web. So you have a PC and never use the command line fumbling through menus to get sysinfo, or do want to change the hostname of your nice machine, try to open a terminal as user and write: hostnamectl status that already is a surprising amount of info you normally do not get to see with such an ease. Want to rename your machine, a nice list of commands, well explained, you find here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… networking_guide/sec_configuring_host_names_using_hostnamectl And if someone does know if this exists already in the openSUSE documentation, feel free to post a link hereafter. Hope that was not too obvious and is not considered "offtopic", but as I regularly see people running into the "I want to rename my machine with a pretty-name but it says network is governed by network manager" etc, this command / link may come handy if somebody wants to do it. Hence this post.

10 30

Trouble configuring split OpenVPN
by Chris Coutinho 03 Feb '21

03 Feb '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I am working with a client that has their own OpenVPN server configured, which I want to configure on my machine as a split tunnel VPN. I only want to route my traffic through their network to resources that they provide access to, otherwise use whatever the default network setup I happen to be on. I've been successful in routing known IP addresses through the tunnel, but I'm stuck with a nameserver problem - I can't resolve a host even when I add the ipv4 address to list of routes (see below). I'm wondering if there are any networking gurus here that can give me a hand. I'm using Tumbleweed, Gnome, and Network Manager I've been given an OpenVPN configuration file (client.ovpn) that I've loaded into the Gnome VPN settings GUI twice - once for the full tunnel and another for my "split" tunnel. I've configured the split tunnel connection as follows: # nmcli connection modify <split> dns=<local dns> # nmcli connection modify <split> ignore-auto-dns=true # nmcli connection modify <split> +ipv4.routes <cidr/32> When connecting to the split tunnel, I can access some of the resources based on IP, but others are not resolvable. Also, this is not really ideal as I'm setting up my DNS for this connection manually, rather than using what my LAN is providing. The difference between the hosts I can/can't resolve seems to be related to name servers. The hosts that I can connect to are also resolvable without the VPN (e.g. 'ping' is able to resolve the host -> ip but refuses my connection), whereas the hosts that are not resolvable without VPN remain unresolvable with the split VPN tunnel. The problem is that I don't know what information I need to configure the split tunnel correctly. This is what nslookup returns for one of the unresolvable hosts while connected to the full VPN. Isn't 8.8.8.8 just Google? $ nslookup <the host> Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: <the host> Address: 10.243.a.b Name: <the host> Address: 10.243.c.d Name: <the host> Address: 10.243.e.f Thanks in advance, Chris -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEss2dENO/PTuA9NTTOdNgxkl4+QMFAmAaZOQACgkQOdNgxkl4 +QP8zA/8DJhW+nDG/JYe6CJwvaFBCSJ/7RodlXJHYmUPT54+wcsqfTNy9YFmaR+S OJTzfTwh5a3B5JUzsV7mvN81x957qvAxs4pKoImw7Qud32JHfV+1sPB+7Zcgd5KQ VkC0RjwCxoFUsQQHV42UeFaEvhLb0Ki0eeroXVQHv4qvP/DHNzLuOEQ9SRQERj1H Z71X3bSIPOKlGj0ye0g7C3/8hk33QT3Ae4QchfY0J3xwTOjBQtWCgZV8k1mP0grz etMLDyTef0WBmyqne4aq8hlwWdBPBqC6FBn0d1klgra2MAfyvutA3HxjMDc251Nu KJgTPT5qZ/rGEM4hy2UTYsrHP/FjNK3jsBmETURM130syBg4b9JtOI9XV+XQz4kN bZ9jFeAzKuSpwcaqR3bYLNPAcXPMzVmFU06fb1uhIchRqoDt+upxjefBvw2RwDpi RaNZBdE1qbSWHxij71zTIUhYCYmWDnzyvmM1xswsIXgvnaO/zwxwzjlspTe1JuMy zaX5vBcJwfq1yzIFQvORVGzrXYQw8Cgu4+eCYfdRCr/zNiQnUyqoBvN/LDIzQtyv +H9EgI/EcI6ZDFc5HIyLSigesXTDMmfnhO29yjVj9YZ/Rv+4Ip6JX+SDogw4SxZO Kp08IxLvoTnohiCZkwaaGJ/lSLfPY10xqCSIRstEDNSehCZOkF4= =FMSE -----END PGP SIGNATURE-----

2 1

Leap 15.0 repo question
by Mark Hounschell 02 Feb '21

02 Feb '21

Are the isos at /pub/opensuse/distribution/leap/15.0/iso/ the original released isos or do they contain all the updates since birth? Thanks Mark

3 14

Server rebooted unexpectedly and without log trace
by Carlos E. R. 02 Feb '21

02 Feb '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was working at my desktop machine. My little server machine, media server, was playing the internet radio with Kodi. I went to the kitchen to put the dinner on the oven. On return, the media server had rebooted and was asking for login. There is no trace in the syslog: <1.5> 2021-01-23T21:15:03.643324+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-23T21:16:56.732717+01:00 Isengard systemd 1 - - Started Daily Cleanup of Snapper Snapshots. <3.6> 2021-01-23T21:16:56.873624+01:00 Isengard dbus-daemon 1109 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1048' (uid=0 pid=5447 comm="/usr/lib/snapper/systemd-helper --cleanup ") (using servicehelper) <3.6> 2021-01-23T21:16:57.131185+01:00 Isengard dbus-daemon 1109 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2021-01-23T21:21:56.728956+01:00 Isengard systemd 1 - - Starting Cleanup of Temporary Directories... <3.5> 2021-01-23T21:21:56.875752+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.879004+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.879901+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.883365+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.887213+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. <3.5> 2021-01-23T21:21:56.888626+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. <3.5> 2021-01-23T21:21:56.889240+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. <3.6> 2021-01-23T21:21:56.965040+01:00 Isengard systemd 1 - - Started Cleanup of Temporary Directories. <1.5> 2021-01-23T21:30:03.251921+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-23T21:33:54.528052+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46 <3.6> 2021-01-23T21:33:54.529239+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46 <3.6> 2021-01-23T21:33:54.603175+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65 <3.6> 2021-01-23T21:33:54.603840+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35 <1.5> 2021-01-23T21:45:03.043504+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) 2021-01-23 22:06:23+01:00 - Booting the system now ================================================================================ Linux Isengard 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) x86_64 x86_64 x86_64 GNU/Linux <3.6> 2021-01-23T22:06:24.780509+01:00 Isengard systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) <0.6> 2021-01-23T22:06:24.780976+01:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23 <0.5> 2021-01-23T22:06:24.781721+01:00 Isengard kernel - - - [ 0.000000] Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5. ... Aside note: Kernel boot information is missing from syslog. New bug? Compare with leap 15.1 syslog: 2020-09-24 13:57:39+02:00 - Halting the system now =========================================== uptime: 13:57:39 up 82 days 15:43, 0 users, load average: 1.20, 1.30, 1.47 2020-09-24 20:48:11+02:00 - Booting the system now ================================================================================ Linux Isengard 4.12.14-lp151.28.67-default #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f) x86_64 x86_64 x86_64 GNU/Linux <0.6> 2020-09-24T20:48:12.560421+02:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23 <0.5> 2020-09-24T20:48:12.560854+02:00 Isengard kernel - - - [ 0.000000] Linux version 4.12.14-lp151.28.67-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux) ) #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f) <0.6> 2020-09-24T20:48:12.560862+02:00 Isengard kernel - - - [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.28.67-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts resume=/dev/disk/by-label/Swap splash=verbose That would indicate a power failure, but the thing is on an UPS. I tested flipping the mains, for 5 seconds, and it survived. I was in the house, I would have noticed any power failure bigger than 0.1 second. A thermal event would be logged, and the machine is not loaded, anyway. Let's see if the journal has something: cer@Isengard:~> journalctl --list-boots - -9 6454520f76ef411aae4048bcad74bf29 Tue 2020-01-28 02:12:23 CET—Sun 2020-02-23 20:40:58 CET - -8 690c025a20e74949aa3b14a9920bc965 Sun 2020-02-23 20:41:43 CET—Sun 2020-04-12 19:41:11 CEST - -7 c931092ce6b742a0bcef0e0c789cc2d9 Sun 2020-04-12 19:41:55 CEST—Fri 2020-07-03 22:12:29 CEST - -6 d0d9dcc6f41d4d95bfb1bb7017fd89b9 Fri 2020-07-03 22:14:26 CEST—Thu 2020-09-24 13:59:17 CEST - -5 deddc3a843ba4ace9580e54614df5918 Thu 2020-09-24 20:46:37 CEST—Sat 2021-01-16 16:27:19 CET - -4 0078032ae9f446389daef4b9b1546184 Sat 2021-01-16 16:28:09 CET—Sat 2021-01-16 20:55:05 CET - -3 71982ddc703b49398aac561ae95a491f Sun 2021-01-17 10:12:08 CET—Sun 2021-01-17 21:01:44 CET - -2 ff6a60796ff94a26a514a8bff51fd3e0 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET - -1 84c1f9d5c6c34fdbb83fe961e42bef1f Sat 2021-01-23 22:01:18 CET—Sat 2021-01-23 22:24:05 CET 0 ecd9e2c9fa9945e4ae57ef7e55938b36 Sat 2021-01-23 22:24:40 CET—Sat 2021-01-23 22:46:51 CET cer@Isengard:~> I need session 2, -2 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET cer@Isengard:~> journalctl --boot=2 - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:07 CET. -- No - then session 3? - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. -- No... wtf? cer@Isengard:~> journalctl --boot=ff6a60796ff94a26a514a8bff51fd3e0 - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. -- That's the whole journal, not number 2. Where is the journal number 2? Another bug in the journal? Ok, let's find the boot point by grepping the whole journal, old style Jan 23 21:16:57 Isengard dbus-daemon[1109]: [system] Successfully activated service 'org.opensuse.Snapper' Jan 23 21:21:56 Isengard systemd[1]: Starting Cleanup of Temporary Directories... Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordin> Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordin> Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. Jan 23 21:21:56 Isengard systemd[1]: Started Cleanup of Temporary Directories. Jan 23 21:30:03 Isengard Sistema[5776]: Logging the current external IP= (omitted) Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35 Jan 23 21:45:03 Isengard Sistema[6157]: Logging the current external IP= (omitted) - -- Reboot -- Jan 23 22:01:18 Isengard kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23 Jan 23 22:01:18 Isengard kernel: Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) Jan 23 22:01:18 Isengard kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.60-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts splash=verbose splash=silent resume=/dev/disk/by-label/Swap mitigations=auto quiet Jan 23 22:01:18 Isengard kernel: x86/fpu: x87 FPU will use FXSAVE Jan 23 22:01:18 Isengard kernel: BIOS-provided physical RAM map: Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003efff] usable Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x000000000003f000-0x000000000003ffff] ACPI NVS Same info, that is, no info about what caused the machine to reboot. Has been fully reliable since I bought it on 2016: 2016-11-27 23:38:32+01:00 - Booting the system now ================================================================================ Linux Isengard 4.4.27-2-default #1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c) x86_64 x86_64 x86_64 GNU/Linux 2016-12-04 15:44:09+01:00 - Halting the system now =========================================== uptime: 15:44pm up 6 days 16:06, 0 users, load average: 0.66, 0.25, 0.14 But now it is running Leap 15.2 since 2021-01-17, that is, a week ago. It rebooted perhaps just at 22:00 - cronjob? I don't have, yet, any log entry on a Saturday at 22:00 with leap 15.2, the machine was upgraded from 15.1 to 15.2 just on past Saturday (with DVD). On previous 15.1, this is what happens normally: <1.5> 2021-01-09T21:30:03.324416+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <1.5> 2021-01-09T21:45:05.372100+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-09T21:48:37.584878+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 42 to 43 <3.6> 2021-01-09T21:48:37.586113+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 42 to 43 <3.6> 2021-01-09T21:48:37.640372+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66 <3.6> 2021-01-09T21:48:37.641443+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34 <3.6> 2021-01-09T22:00:03.382980+01:00 Isengard systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2021-01-09T22:00:03.514452+01:00 Isengard dbus-daemon 1186 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.16079' (uid=0 pid=23673 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper) <3.6> 2021-01-09T22:00:03.775706+01:00 Isengard dbus-daemon 1186 - - [system] Successfully activated service 'org.opensuse.Snapper' <1.5> 2021-01-09T22:00:08.698222+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <9.6> 2021-01-09T22:15:01.744156+01:00 Isengard run-crons.daily - - - Considering my daily cron jobs. <9.6> 2021-01-09T22:15:01.885387+01:00 Isengard run-crons.daily - - - Adjusting permissions of Video directories I'll have to keep watching and see... - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYAyj2hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV5CYAoIQFFQZGRpCSsGwRl9bj jWgcgHdvAJ0TCi2Cbp5P5RkyBNJLKTzsNojWVw== =D6AM -----END PGP SIGNATURE-----

6 11

AES-NI & encryption
by James Knott 01 Feb '21

01 Feb '21

I run pfsense for my firewall/router and it supports the AES-NI instructions for encryption. Does the same happen with openSUSE, with browsers, VPNs or other? https://en.wikipedia.org/wiki/AES_instruction_set#x86_architecture_processo…

2 1