To all with symbian devices, especially the people with an E71:

I noticed that when you press and hold the 'Chr' key, and then simoultaniously press a letter, e.g. the e symbian will cycle through the possible accents that are applicable for that character!

To post the 'The Internets @ ...' posts I am using a perl script originally written by Stephen:

http://stephen.evilcoder.com/archives/2005/02/27/daily-delicious-links-perl-script

The script was later on modified by Edward de Leau to be compatible with wordpress 2.3.

And I must say, I am very happy with this script. One problem was that it also synchronizes private links. I don't like this, when I mark a link private, it should stay private, and not posted on my wordpress. So I modified the script to be able to NOT synchronize these links.

While I was at it I also added an option to include the tags in the body of the post or not. Well actually this already existed, but was commented out. I just added a boolean to be able to choose wether to include them or not.

In the future I plan to maybe at the option to be able to choose fixed tags to be used in wordpress for a daily post.

Download my modifications: wpds.pl

As I was reading my rss feeds I discovered one time password logins via ssh. I read it in a post on Philip's Blog. I found it interesting so decided to try this on a virtual machine as a test. Although it wasn't as simple as Philip's post, it was rather simple. But to help out you guys trying to configure and use it here are my findings: As this is a rather long post I'm going to use a break for this one time (sorry rssfeed readers! I forgot but I noticed my feed feeds entire blog posts, and not just the part before the break. Good!).

First, I installed opie-server, this is as simple as:

# apt-get install opie-server

Then, to make sure when you login through SSH, the pam_opie module is used, I had to edit /etc/pam.d/sshd as follows:

[...] # Standard Un*x authentication. #@include common-auth auth    sufficient      pam_opie.so auth    sufficient      pam_unix.so nullok_secure auth    require         pam_deny.so [...]

If you do it this way you will still be able to login with your normal password when te OTP(One Time Password) login fails. This may be handy when you have no possibility of calculating the appropriate response to the OTP challenge. If you do not like this behaviour and you want you or your users to be able to authenticate with OTP only you can comment out the pam_unix.so line:

[...] #auth    sufficient      pam_unix.so nullok_secure [...]

As after this it was still not working I looked into the /etc/ssh/sshd_config file and found that there was one option that needed to be enabled to make sure that the ssh server knows you will be using challenge response authentication. Edit /etc/ssh/sshd_config:

[...] ChallengeResponseAuthentication yes [...]

As a final step restart your ssh server:

/etc/init.d/ssh restart

As of here we can follow the simple step that Philip gave us in his blog post

:

$ opiepasswd -c Adding bert: Only use this method from the console; NEVER from remote. If you are using telnet, xterm, or a dial-in, type ^C now or exit with no password. Then run opiepasswd without the -c parameter. Using MD5 to compute responses. Enter new secret pass phrase: Again new secret pass phrase: ID bert OTP key is 499 mi7400 RIDE LUSH VIE YE BARD LOSE

When issuing opiepasswd -c you will be asked to enter a secret pass phrase, you will have to be able to remember this, but it should be very secret(not like your birthday or something like that). When we look at the following output:

ID bert OTP key is 499 mi7400 RIDE LUSH VIE YE BARD LOSE

• 'bert' is your unix username, and your OTP ID
• '499' is the sequence (this will count downwards every time a password has been used An already used password will be discarded and not usable anymore, hence OTP(One TIme Password) :-)
• 'mi7400' is the challenge string
• 'RIDE LUSH VIE YE BARD LOSE' is the password for this sequence (499) !! spaces included

Now, when ssh'ing to the system, and you have no private key file (because this will still work) you will be prompted the following:

$ ssh bert@minerva otp-md5 498 mi7400 ext, Response:

On a system where opie-client is installed you can calculate the appropriate response:

$ opiekey 498 mi7400 Using the MD5 algorithm to compute response. Reminder: Don't use opiekey from telnet or dial-in sessions. Sorry, but you don't seem to be on the console or a secure terminal. Warning: Continuing could disclose your secret pass phrase to an attacker! Enter secret pass phrase: WACK WAIT ALMA HERO WAR KIN

And use this password 'WACK WAIT ALMA HERO WAR KIN' to log in. Now offcourse the thing about this is that when you got your favorite machine with you (e.g. laptop) you do have your private keys. So there's no need for OTP. And when you need it (e.g. a public computer) you are not always (read: seldom) privileged to install an opie-client to calculate your response. Offcourse you can find online calculators but do you trust them with your passphrase? Luckely there's a nice solution for this problem: http://code.google.com/p/j2me-otp/ Thanks to "Marcin Gryszkalis" who posted this comment on Philip's blog post. This is a java application, so it should work on almost any modern cellphone. I tried this on my Nokia E61i and it works like a charm. (And offcourse, you do always have your cellphone with you!). A screenshot of the calculator in action: The only thing I could say about this application is that they chose to call the passphrase "Password" which might be a bit confusing. So, if you are a bit paranoid, or you just require a very secure authentication mechanism, this works like a charm, is not too difficult to setup and provides you with a handy mobile solution!

Thanks Aaron Toponce,
for pointing me to the windows_auto_renumber off option! Didn't know that one existed.

Regarding the problem that you usually remember which number a certain channel and/or conversation is(I do to) I do have a nice script which gives you an alternative 'act' bar. Instead of just the window number it also shows you the name of the channel/conversation.

The script can be found on f0rked.com and is called "Advanced Window List".

Some screenshots:

Using awl_hide_data=0, not hiding anything...

Using awl_hide_data=1, hiding inactive windows...

Using awl_hide_data=2, hiding all but msg's and query's...

I do realise that using this script can result into a very crowdy act bar, but that's what the awl_hide_data is for. You either like it or you don't and I do...

After reading this post I tried out the code snippet of Jan but honestly my eyes did not like it. The yellow didn't look good to me and I also had the feeling that the smiley was a bit overkill.

But as I truly liked the Idea (thanks Jan) I changed it a bit to comfort me.

A screenshot: