rTorrent and selfsigned SSL certs

Here is a little tutorial for using rTorrent on sites using self signed SSL certs that I wrote today.

I have taken bits a pieces from various sites around the place.

Broadly speaking the process to get rTorrent working using a self signed cert are these:-

1. Get the cert and convert to a format rTorrent can use
2. Put the cert somewhere you will be able to find
3. Change rTorrents config to ensure it knows where to find the SSL certs

So, here we go.

1. ==Get the cert==
Log into your linux box as the user that will be running rTorrent and change to you home

Pass the following command……

sudo openssl s_client -connect thesitenamehere.com:443 | tee out_cert

You will see the SSL certificate on your screen, now hit CTRL-C, magically in the directory
you are now in will be a file called out_cert. Now you need to convert the cert to x509
format. To do this pass the following command

sudo openssl x509 -inform PEM -in out_cert -text -out out.pem

You can view the files we created with a text editor if you so wish.

2. ==Put the cert in a know directory==
Now you need to find out where your QNAP/NAS/PC has all the SSL certificates, they could be
in /etc/ssl/certs, take a look. If not you need to find out where they are. Once you
have found where they are copy the out.pem file to the directory where the SSL certs are
lets pretend they are in /etc/ssl/certs. Pass the following command…

sudo cp out.pem /etc/ssl/certs

Then once it is in that directory change to the /etc/ssl/certs directory. Once you are in
there pass the following command….

sudo c_rehash

3. ==The ~rtorrent.rc==
Now you need to find the example ~rtorrent.rc file that comes with rTorrent (note
that it is a hidden file as it starts with ‘~’).
Once found copy it to the home directory of the user that will be running rTorrent. the name of the
file should be ~rtorrent.rc

Now go into the ~rtorrent.rc file and take a look at the options it gives you, this is the
power of rTorrent. Use your favourite text editor, I use vi, there are plenty others.

Anyway, now you need to put the following line at the bottom of the ~rtorrent.rc file

# directory for ssl certificates on self signed trackers

That should be it. You should be able to connect to your site now and torrent away.

You will need to change the rtorrent.rc file to ensure it works well with your QNAP/NAS/PC. In particular you should alter it to include a watch directory for new .torrent files so its starts automatically downloading, and also perhaps a default save directory etc.

Check out rtorrents site and also read some of the tutorials out there……

Howto: Use rtorrent like a pro

Enjoy rTorrent, its the shitzen.

showRSS and bashpodder still no play nice

This is really starting to depress me. showRSS is the shitzen but my RSS feed reader solution (bashpodder) is just not working with it. It will down load the first feed ann enclosure that appears but will not down load subsequent enclosures there after, this is still the case with just using the public feeds. So, its back to mininova feeds for me with the following added to each of tyhe feeds to ensure only the most recent is downloaded “?num=1” What a pisser. Any bash scripting gurus please feel free to chime in and let me know how to fix this in the script.

rTorrent RSS with bashpodder Pt.2

We getting the DNS-323 to run the bashpodder script for the RSS feed to be used in rTorrent turned out to be trickier than I thought.

It basically boiled down to environmental variables in cron being different than for my user on the NAS.

I have solved this issue now, my post on the DNS-323 hack forum will help you here.

rTorrent and bashpodder on DNS-323

I have finally been able to get rTorrent and bashpodder playing together on the DNS-323 NAS. In short bashpodder acts as the RSS feed reader and downloads the torrent file to a directory that rTorrent watches and then rTorrent kicks off the torrent download. Its light and NOT a resource hog (which is important for the DNS-323 as its got little resources to start with).

Please see my write up at the DNS-323 hack forum.

Brother MFC-440CN and the eeePC (701)

My wife has been bothering me for some time about her eeePC not working with our printer. Today I finally got around to fixing it. Thanks to this blog I was successful.  Having learnt from Adam’s experience I first created the directory…

mkdir /etc/printcap.local

then copied /etc/printcap to /etc/printcap.local by…

sudo cp /etc/printcap /etc/printcap.local

After that I also created the directory…

sudo mkdir /var/spool/lpd.

Passing the command…

dpkg -i --force-all --force-architecture mfc440cnlpr-1.0.1-1.i386.deb

installed the lpd without a hitch. I then installed the CUPS driver using…

dpkg -i --force-all --force-architecture mfc440cncupswrapper-1.0.1-1.i386.deb

and this to was successful.

I then went into the eeePC’s printer setup and added a new printer.

  • Type = Network printer
  • Attribute = “other”
  • Path = socket://192.168.x.xx:9100 (you will need to put the IP address in this bit for your network setup)
  • Selected brother for the manufacturer and then selected the MFC-440CN driver from the list which will be there now thanks to the steps we have previously taken.
  • After this I selected ‘yes’ to print a test page.

It worked. Wohoooo!

My wife loves me again, she is now busy making up for lost time and furiously contributing to the deforestation of Indonesia.

Hello all.

I enjoy technology and Linux, I run my own server so I created this so that I can keep anyone that’s interested up to speed on what I’m up to.

I’ll be making it pretty as I go so stay tuned.