October 2016 - openSUSE Users - openSUSE Mailing Lists

Re: SV: [opensuse] DirtyCOW
by Dave Plater 22 Oct '16

22 Oct '16

On 22/10/2016 11:17, Bob Williams wrote: > On 22/10/16 10:14, Dave Plater wrote: >> >> On 22/10/2016 10:22, Per Jessen wrote: >>> That patch seems to cause a jump from kernel 4.1.31 to 4.4.25, is that >>> correct? >>> >>> >>> Per Jessen >>> >> I just updated my 42.1 system and it installed kernel-source-4.1.34. >> AFAIK the 4.4 kernel is 42.2. >> >> Dave >> > I just updated my 42.2 system, and it updated my kernel-default 4.4.24 > to 4.4.25, which would be similar to what Per observed. > > Bob It looks like he went from the old 42.1 kernel to the new 42.2 kernel somehow. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Adding a CRL
by Bjoern Voigt 21 Oct '16

21 Oct '16

I followed this openSUSE specific blog entry to install my CA certificate and CRL system-wide: https://blog.hqcodeshop.fi/archives/157-Installing-own-CA-root-certificate-… But unfortunately my CRL is still not found by openssl. Any ideas? # ls -l /etc/pki/trust/anchors total 8 -rw-r--r-- 1 root root 690 Oct 18 13:34 MY-CA.crl -rw-r--r-- 1 root root 1424 Oct 18 13:34 MY-CA.crt # egrep '(BEGIN|END)' /etc/pki/trust/anchors/MY-CA.crt /etc/pki/trust/anchors/MY-CA.crl /etc/pki/trust/anchors/MY-CA.crt:-----BEGIN CERTIFICATE----- /etc/pki/trust/anchors/MY-CA.crt:-----END CERTIFICATE----- /etc/pki/trust/anchors/MY-CA.crl:-----BEGIN X509 CRL----- /etc/pki/trust/anchors/MY-CA.crl:-----END X509 CRL----- # openssl crl -noout -hash -in /etc/pki/trust/anchors/MY-CA.crl 49742892 # ln -sv /etc/pki/trust/anchors/MY-CA.crl /var/lib/ca-certificates/openssl/49742892.r0 '/var/lib/ca-certificates/openssl/49742892.r0' -> '/etc/pki/trust/anchors/MY-CA.crl' # update-ca-certificates # openssl verify -crl_check_all /etc/pki/trust/anchors/MY-CA.crt /etc/pki/trust/anchors/MY-CA.crt: CN = My CA error 3 at 0 depth lookup:unable to get certificate CRL Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 7

[opensuse] Typical time to wake up Console on a headless PC?
by Greg Freemyer 21 Oct '16

21 Oct '16

All, I've had a KVM setup with a Leap 42.2 (beta) machine running for a few months. In the past I had issues with not being able to wake the console up if it had gone to sleep. (I could still ssh in. etc.) RC1 seems much more reliable, but it takes about 15 seconds after I reconnect the USB keyboard/mouse before the console comes back to life. It feels like a long time, but I don't know what normal is? My Windows PC on the same KVM is basically instantaneous. I've got all the power saving features disabled in KDE. I really don't want openSUSE turning if off my monitor at all. When I flip the KVM to the box, I want to have video immediately. To be honest, I don't login at the Console all that much (mostly I connect over the network). So I don't know if the KDE settings have any impact if I'm not logged into the Console? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Access rules of our administrator
by A. den Oudsten 21 Oct '16

21 Oct '16

What are the access rules of our administrator? Andre den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] rsyslog timestamp question
by Carlos E. R. 21 Oct '16

21 Oct '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, In my small home server I use rsyslog to write to log file the entries sent by other small machines in the house, such as router. I have just put into service a new WiFi access point. The entry in rsyslog.conf is: if ($source == '192.168.1.7') or ($source == 'ap') or ($source == 'ap.valinor') then \ -/var/log/router & stop and I get with that: <3.4> 2016-10-20T21:13:41+02:00 router kernel - - - [skip] w:eth0.3 l:eth4 dev:br0 <3.6> 2016-10-20T21:13:41+02:00 router kernel - - - br0: port 1(eth4) entering forwarding state <1.6> 2016-01-01T01:00:10+02:00 ap.valinor kernel - - - br0: port 2(eth1) entering forwarding state <1.6> 2016-01-01T01:00:10+02:00 ap.valinor kernel - - - br0: topology change detected, propagating <1.6> 2016-01-01T01:00:10+02:00 ap.valinor kernel - - - br0: port 1(vlan0) entering forwarding state <1.0> 2016-01-01T01:00:10+02:00 ap.valinor ntp - - - start NTP update The first two lines belong to the ISP router, left there for reference. The other four belong to the AP. Notice the timestamp? Obviously it is writing the time sent by the device, before it runs the NTP query, and thus the time is incorrect. How could I log a timestamp written by the rsyslog server machine? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlgJKw0ACgkQtTMYHG2NR9WBoACgh20NGGB+QnBrsKI4wTEAqGqj NhoAnAxZ656yZGTCMcnOdNyj47CGuPW0 =XvHv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] scripting usb pen recovery
by jdd 21 Oct '16

21 Oct '16

Hello, I have a bunch of usb pen written as various openSUSE dvd/live stick. I want to reset them to be ordinary ones. The SDB is here: https://en.opensuse.org/index.php?title=SDB:Live_USB_stick&diff=next&oldid=… but it's not handy for many copies. It's not that difficult to copy this in a script, but it makes it a very dangerous script in case of sdX X error :-( I noticed imagewriter knows if a plugged device is usb pen or not is there a way to do the same in a script? May be detect if the pen is an iso image before acting? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Hostname on kde login & lock screen?
by Per Jessen 20 Oct '16

20 Oct '16

How do I get the local hostname (with or without domain) displayed on the KDE login and the lock screens? sddm theme ? -- Per Jessen, Zürich (11.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] expected behavior when systemctl isolate is run
by Istvan Gabor 20 Oct '16

20 Oct '16

Hello: I tried to run systemctl isolate commands as it's suggested in a different thread (audio config) and I have a feeling that it doesn't work as expected. I use openSUSE 13.1 with KDE3 desktop and kdm3 login manager. First I tried to run the command in a KDE3 konsole window (I closed all applications before running the command): > su # systemctl isolate multi-user.target After this the graphical desktop window (on vt7) disappears and the screen becomes blank but the mouse pointer stays on the screen, it doesn't disappear. When switching to other terminal (vt 1-6) by CTRL+ALT+F[1-6] the login message is shown and the mouse pointer is shown too (on each 1-6 terminals). In addition, switching target doesn't log out the user who was logged in to the graphical desktop: # w 17:43:43 up 6 days, 5:40, 3 users, load average: 0.21, 0.61, 0.90 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT user :0 console 13Oct16 ?xdm? 1:40m 0.06s /bin/sh /opt/kde3/bin/startkde user console :0 13Oct16 6days 0.00s 0.06s /bin/sh /opt/kde3/bin/startkde root tty2 17:43 7.00s 0.04s 0.00s w After this I tried to switch back to graphical target: # systemctl isolate runlevel5.target but it doesn't give back the graphical login screen. If I run "killall starkde" the graphical login screen appears on vt7. What happens if I try to change target when graphical state is active but no one is logged in to KDE3? Running "systemctl isolate multi-user.target" turns graphical login screen off, without traces (no mouse pointer on screen). OK. If I try to switch back to graphical target: # systemctl isolate runlevel5.target the graphical window doesn't appear. If I switch to vt7 (CTRL+ALT+F7) only log messages are shown instead of KDE3 login screen and I can not switch away from this screen. I can't get away from this screen (by pressing any keyboard combination). I must press reset button to restart the system. Another thing: after running any systemctl isolate command it takes the cursor 32 seconds to reappear. I think it's too long. What I'd expect from running systemctl isolate commands: -to multi-user: switch to multiuser state and log out user logged in to graphical desktop -come into effect much faster, maximum a few seconds instead of 32 seconds -to runlevel5: switch to graphical target and show login screen -when switching to vt7, not to stick there It used to work like that earlier when init [35] commands changed runlevels. Any comment? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] IPv6 Router Configuration
by Lew Wolfgang 19 Oct '16

19 Oct '16

Hi Folks, I finally started to fiddle with my router's IPv6 configuration. My ISP (Cox cable modem) advertises v6 compatibility, so things should work if all my stars line up, right? The router is a ZyXEL USG 20W, but I'm not using the Wifi radio portion. I click the /system/IPv6 "Enable IPv6" check box and it then enables v6 configuration options. Under /Network/Interface/Ethernet I now get options to configure the logical interfaces. (the USG 20W allows individual RJ45 Ethernet ports to be assigned to logical interfaces. I've got switches connected to the various ports to segment the lan appropriately.) IPv6 is disabled for all interfaces at this point. So I click on wan1 to edit it's config and am presented with these interesting options, among others: Yes/No: Enable SLACC V6 Address/Prefix Length (optional) Gateway (optional) Metric: 0-15 Address from DHCPv6 Delegation (add entries) DHCPv6: Server/Client/Relay Yes/No: Enable Router Advertisement Yes/No: Advertised Hosts get Network Config from DHCP6 Yes/No: Advertised Hosts get Other Config from DHCP6 MTU: 1480 default Router Preference: Low/Medium/High Advertised Prefix Table: Add IPv6 address/prefix length Advertised Prefix from DHCPv6 Prefix Delegation (add entries) Egress bandwidth: for load balancing Ingress bandwidth: for load balancing LAN1, LAN2, and DMZ have similar configuration screens. Certainly not plug-and-play! I'm sure that many of the config choices have reasonable defaults, but above that I haven't the foggiest notion how to configure this, and also how to test the configs for proper security. I'm sure I could figure it all out, but at this point in time, why bother? Maybe sometime if I've got a long weekend when no one else is using the network I'll fiddle with it again. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 70

[opensuse] IPv6 in openSUSE
by Per Jessen 19 Oct '16

19 Oct '16

jdd wrote: > Le 10/09/2016 à 11:50, Per Jessen a écrit : >> jdd wrote: > >>> I too often notice that allowing IPV6 brake the home connectivity... >> >> Where do you notice this? That is almost certainly due to a lack of >> skills and/or poor equipment. Either at home or at the providers. >> > nearly in any openSUSE install I have, I has to disable IPV6 to have a > working system. Last time it was due to a very long lag time at > connect. Initially I simply used default install. > > I don't think this is the place to discuss this in depth :-( In this thread ("ssh questions") perhaps not, but in general, IPv6 issues in openSUSE do belong here, I would say. I have never disabled IPv6 when installing or later. In my opinion, any problems are due to misunderstandings or a poorly configured network. I think Carlos had an example of the latter. (his providers problem, not his). I think James and Koenraad have both highlighted the issue in getting a Linux box to propagate an ipv6 prefix handed out by the provider. These are corner-cases though, they're not typical issues. > I simply don't promote IPV6 to anybody That is of course your choice, but I would say it is wrong to suggest IPv6 doesn't work or isn't available. I promote it every chance I get. I've been on IPv6 for almost ten years, since October 2006 when I opened my first tunnel account. Back then I also imagined a steep learning curve, and I didn't really get started until 2009 when I got a static prefix from my provider. The learning curve is just not that steep - especially not from an end-users point-of-view. If you want to play, there are a few concepts you need to understand, I think James mentioned some of them, but that's it. The learning curve is not that steep. Just do it. -- Per Jessen, Zürich (22.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 86