Internet Bandaid   [RSS Feed]

Archive for February, 2009

Yahoo and Live Better at Organic Search Results?

without comments

I put together a simple site called a couple of months ago. It provides a simple calories expended vs. heart rate calculator. I implemented all the usual SEO strategies for the site.

I find it surprising that this whole time, almost 100% of users find my site via the organic search of Yahoo or Live. 0% comes from Google. If you search by the keywords “heart rate calories”, shows up as the first item of Yahoo search and Live search. It doesn’t even show up on Google.

So is there any merit to the argument that Yahoo and Live are better at organic search than Google?

Written by John Lai

February 17th, 2009 at 1:45 pm

SVN Access via SSH keys for Linux and Windows

with 4 comments

Many shared hosting packages offers only 1 SSH account, which can be a problem if you have many developers each needing his/her own unique credentials to access the server. This is especially the case if you have multiple developers needing to access a single subversion repository.

In this post, I outline the steps to offer a client machine (your developer) unique SSH credentials for server access via SSH keys. I follow up by showing how they can connect to your svn repository.

Step A: Setup on Client’s Linux Machine

// Performed by client (the developer)

If you use a unix-like OS, continue reading this step. If you use a Windows OS, skip this step and go to Step B.

1. Open up the terminal/shell.

2. On the command line, type:

ssh-keygen -t dsa

3. When prompted to enter file name, type:


4. When prompted for a password, you can leave it blank and hit enter, or type in a password. Because we are authenticating via keys, it is not necessary to use a password.

5. Now you should have two files:

a) mykeys – the private key you keep to access the server
b) – the public key you give to your systems administrator

6. Copy mykeys to the ~/.ssh directory.

7. Rename mykeys to id_dsa.

8. Give to your systems administrator.

You are done. When your systems administrator installs the on his end in Step C, you will be able to access his server via ssh using the new password you chose.

Step B: Setup on Client’s Windows Machine

// Performed by client (the developer)

If you use a windows OS, continue reading this step. If you use a unix-like OS, avoid this step and perform only Step A.

1. Go to and download putty.exe and puttygen.exe.

2. Open puttygen.exe.

3. From the main menu, select Key>SSH-2 DSA key.

4. Press the Generate button.

5. Move your mouse cursor around to generate randomness as instructed by the program.

6. When key is generated, you may choose to fill in the keyphrase passes or leave them empty. Because we are authenticating via keys, it is not necessary to use a password.

7. Copy the contents in the “Public key for pasting into OPENSSH authorized_keys file:” into a text document. Save the text document as

8. Save private key as mykeys.ppk.

9. Send to your systems administrator. Wait for him to configure things in Step C before continuing.

10. When your systems administrator is finished with Step C, you are ready to set up Putty SSH and SVN access. Open up Putty and fill out the Host Name.

11. In the Saved Session, type in a Session Name that you can easily remember. It will be used by svn later on.

12. On the left hand side, go to Connection>SSH>Auth and find the mykeys file for the private key field.

13. Go to Connection>SSH and make sure SSH 2 is selected.

14. Go back to the first Putty screen and save these settings.

15. Test the new SSH Key by clicking Open. Putty will prompt you for the private key password you chose earlier.

16. Download and install Tortoise SVN for Subversion access.

17. When Tortoise is installed, the path to your svn repository is


The username is the ssh account username. The sessionname is the Session Name from step 11. This Session Name links back to the settings saved by Putty. When you log in, Tortoise will prompt you for your ssh key password.

You are done.

Step C: Setup on Unix-like Server

// Performed by systems administrator

1. Obtain the from your client.

2. Copy the contents of and append it to the file ~/.ssh/authorized_keys2 (if the file does not exist, create a blank document first and then append).

3. In the /pathtorepository/conf/passwd file, add a new username – password pair.

Your server is now ready to accept ssh access from your client. Repeat these steps for additional clients, and append the public keys to authorized_keys2.

Written by John Lai

February 13th, 2009 at 6:45 pm