I assume you are familiar with installing packages and whatnot on the N900/Maemo OS.

1. First off I grabbed the plugin from the download page.
2. I installed it from the terminal using dpkg --install.
3. Next I entered my Gallery2 Administration interface and added a new user, I called it mobile. I configured it with a random password, which I jotted down to enter into the N900.
4. After that I enabled the Remote plugin in the administration interface.
5. I created a new album, with the title Mobile (note case is important here)
6. I adjusted the permissions on the album to permit the mobile user full access, I could probably lock this down a bit to only allow addition of new items but I’m not too worried.
7. Next I grabbed my N900 and went to configure the Gallery2 sharing service, this is where the fun began for me. I ended up using tcpdump over ssh to diagnose the problems!
8. I filled out the form with the following variables:

   User name

   mobile

   Passsword

   Pa$Sw0rd

   URL

   gallery.cs278.org (leave off the scheme, https is not supported.)

   Album

   Mobile (Case is important here, use the same as the album title you set.)

   If you get a network error, basically the plugin couldn’t authenticate to Gallery2 or you didn’t have the Remote interface enabled. Hopefully this helps somebody and saves you heading for tcpdump and some head scratching.

   ]]> http://www.cs278.org/blog/2010/02/01/sharing-photos-from-n900-to-gallery2/feed/ 4 http://www.cs278.org/blog/2008/11/16/punching-holes-in-firewalls/ http://www.cs278.org/blog/2008/11/16/punching-holes-in-firewalls/#comments Sun, 16 Nov 2008 16:37:09 +0000 Chris http://www.cs278.org/blog/?p=402 Continue reading →]]> It is a lot easier than you think.

   OpenSSH, which can only be described as the best utility of all time, is quite a versatile tool one feature people use frequently is port forwarding. This allows you to open a port on your computer that forwards the data over the SSH connection to the destination you specify, very useful when needing access to the an intranet web server when you don’t have a proper VPN set up for example. However, SSH can also do this in reverse! It opens a listening port up on the remote machine which then relays data to the destination you specify. For example you can SSH into a remote host and get SSH to open a port on that host which relays data back to the SSH port on the machine you are connection from, thereby allowing SSH access to a machine where it would normally be impossible.

   A practical example:

   chris@ktulu:~$ ssh sandman.cs278.org -R 2222:localhost:22

   This connects to the server sandman.cs278.org and opens port 2222 which forwards traffic to localhost:22 (localhost is the machine I am connecting from). Once logged into the server I can do this:

   chris@sandman:~$ ssh localhost -p 2222

   Which opens a connection back to the remote machine.

   ]]> http://www.cs278.org/blog/2008/11/16/punching-holes-in-firewalls/feed/ 0 http://www.cs278.org/blog/2008/01/12/blocking-ssh-brute-force-attempts-using-iptables/ http://www.cs278.org/blog/2008/01/12/blocking-ssh-brute-force-attempts-using-iptables/#comments Sat, 12 Jan 2008 15:53:33 +0000 Chris http://www.cs278.org/blog/2008/01/12/blocking-ssh-brute-force-attempts-using-iptables/ Continue reading →]]> After my recent break in I have looked into ways of protecting SSH and my server resources. I employ fail2ban on my main server, it has the resources to run such a programme – my Linksys NSLU2′s however do not. The solution is to use iptables to limit the number of connections any host can make in a given time frame. I wrote up a quick how to on this over at my wiki. Enjoy.
   ]]> http://www.cs278.org/blog/2008/01/12/blocking-ssh-brute-force-attempts-using-iptables/feed/ 1