opensuse

ssh keys in kde4

pontohonk.de wrote some code to have kdewallet supply your ssh keys when ssh-agent requires them. Great code, my problem was that it’s been a while since I used kde and f.example qmake wasn’t something I’m used to. So here’s how I did it in OpenSuse 12.1 .

download askpass.C and askpass.pro from pontohonk.de
Issue:

# zypper install libqt4-devel
# zypper install libkde4-devel
# qmake
# make
$ cp askpass /path/to/home/.local/bin/

The rest is well explained by pontohonk.de

Opensuse 12.1 gave me ‘wrong’ AltGr+4 character

In opensuse 12.1 having English (GB) as language and with norwegian keyboard I got the € character when pressing AltGr + 4 in txt console … In kde 4 my keyboard gave me a $ which is the character I’m used to get when typing that combination of keys.
In OpenSuse look in /etc/sysconfig/keyboard, in my case I changed the line KEYTABLE=”no-latin1.map.gz” to KEYTABLE=”no.map.gz” and I got my AltGr + 4 back to ‘normal’ .

SSL and .pem problems while setting up ifolder test server.

I’m looking at ifolder, and during installation on my test server I spent some time trying to get my head around the ifolder documentation regarding using .pem certificates with apache2. They explicitly say you have to export your self signed certificate as .pem with ‘ca certificate only’, on my OpenSuse test server /var/log/apache2/error.log kept on giving me

Init: Private key not found

This post gave me a hint on how to resolve this. Exporting the certificate as specified in the ifolder administrator documentation as ‘ca certificate AND the private key’ solved it all.

My snd-intel-hda was eating 30% cpu constantly

The alsa module snd-intel-hda was constantly eating up about 30% of my cpu.
Google pointed me in direction of blaming pulseaudio:
linux.debian.bugs.dist
tycheent.wordpress.com

But pulseaudio.org gave me a hint about snd-intel-hda being buggy.

I’m using OpenSuse 11.1 and came over this:
en.opensuse.org
which help you upgrade your alsa base and driver packages to 1.0.21 and problem solved !

Ntp and networkmanager aren’t friends

On my Opensuse box I’ve setup ntp to synchronize time, but because I’m using networkmanager and since Knetworkmanager doesn’t log me on to the network until KDE is up and running, ntp end up not finding any servers during boot and just goes to sleep.
A really easy / lazy fix to the problem is to simply restart the ntp service after logging on to Kde, but then again I need to be root to restart ntp.
I decided giving myself sudo rights with no password to the ntp service and put a script in Kde’s autostart folder.

Setup sudo rights in /etc/sudoers by issuing:

# visudo /etc/sudoers

Add the line:

 [your_username]    ALL = (ALL) NOPASSWD: /etc/init.d/ntp restart

Now your user can run the command:

$ sudo /etc/init.d/ntp restart

which you could but in a script in ~.kde4/Autostart/restart_ntp.sh and the problem is solved πŸ™‚

Note: sudo is quite picky about the command specified. In the line above my user can run the command as specified, but if I try to run for instance

 
$ sudo service ntp restart

which basically is the same command, sudo won’t let me because that’s not the command I specified.

noip2 client init script for opensuse

In opensuse I couldn’t find any noip2 packages in the default repositories (like I’m used to from debian/ubuntu).
I didn’t really search around for any yum repos or rpm’s, but decided I wanted to have a go at the code available at no-ip.com .

Compiling the source was straight forward, but the init script wasn’t really tailored for opensuse, so I wrote my own.
The script is available here for those interested :p

Add your ssh-key when logging on to Kde 4.x in OpenSUSE

I wanted my ssh-keys automatically loaded when loging on to my box.
In OpenSUSE you can easily fix this.

Make sure you got these packages installed:

joar@linux-xsuv:~> rpm -qa | grep ssh
pam_ssh-1.96-26.112
openssh-5.1p1-40.15
openssh-askpass-5.1p1-40.15

Now edit /etc/pam.d/xdm and add the lines

>auth     sufficient     pam_ssh.so
session  required       pam_ssh.so

don’t delete anything there, just add those lines mentioned above.

This ensures ssh-agent is started while logging on and pam tries to unlock any of your ssh keys by using your login password as a passphrase.

Obviously this requires your ssh-key passphrase to equal your login password πŸ™‚

I’ve tested this on OpenSUSE 11.1.

Source for this info at opensuse.org