Getting Fed Up With Flickr [17 Apr 2007|09:25pm] Tonight I went to go get some horse pictures from Flickr, just to use as my desktop wallpaper and boy was it a hassle. I understand why they want you to sign in to get the other sizes of images (actually no I don't...) but since I am an 'old skool' member they make it such a pain in the ass. I ended up getting a new Flickr ID... It doesn't really matter though because I use ZenPress for all my photo needs. I've got to get more into photography, this poor Canon Rebel XT is just sitting here, wanting me to use it! I guess I should read up on those photography books I bought too...so much to do in so little time... post comment

Getting through Port 548! [17 Apr 2007|11:19pm] It looks like Apple released a firmware update (version 7.1) that will let you use port 548 on the new Apple base stations. This is really nice because I don't use AirDisk currently and I would like to be using AFP on 548. Unfortunately you can't remotely update the firmware so it's going to have to wait for another day... post comment

Getting Fed Up With Flickr [17 Apr 2007|11:19pm] Tonight I went to go get some horse pictures from Flickr, just to use as my desktop wallpaper and boy was it a hassle. I understand why they want you to sign in to get the other sizes of images (actually no I don't...) but since I am an 'old skool' member they make it such a pain in the ass. I ended up getting a new Flickr ID... It doesn't really matter though because I use ZenPress for all my photo needs. I've got to get more into photography, this poor Canon Rebel XT is just sitting here, wanting me to use it! I guess I should read up on those photography books I bought too...so much to do in so little time... post comment

Creating Shared Host Keys [17 Apr 2007|11:19pm] This is an article aimed at mostly system administrators and people that use SSH on a daily basis to connect to remote clients and servers. I myself have been wanting to set this up for quite some time and now I've found the time and need too! I currently have multiple servers each running several various services. I plan on setting it up so that when one server makes a backup of a few databases it can automatically connect to another server and upload the backups there for safe keeping. While it sounds semi-complicated, especially when trying to get the servers talk to each other without any user interaction, it's not all that bad! In order to get the servers to talk to each other without having me type in usernames and passwords I'll be creating special "keys" that allow them to talk without user intervention! In our example I have Server1 which makes the actual backups of my databases, on Server2 I have a nice RAID setup so I can keep my backups safe and secure! Server2 is where I want to put Server1's backup files. Also the user I am using for an example on Server1 is jimmy and on Server2 it is jimmy2. Hopefully it's not too confusing! On Server1 I will open up a Terminal and type in: ssh-keygen -t rsa It will ask you where you want to save the key (usually something like /Users/your-username/.ssh/) - just hit enter here. It will then ask you to input a passphrase, just hit here and again when it asks you to 'enter in the same passphrase'. It will then spit out something like: Your identification has been saved in /Users/jimmy/.ssh/id_rsa. Your public key has been saved in /Users/jimmy/.ssh/id_rsa.pub. The key fingerprint is: 88:99:60:ee:eb:e5:ac:1f:fb:fe:ae:83:5c:3c:c4:0b jimmy@mycomputer Perfect! Now we need to put this special key onto the machine you want to remotely connect too, in this case Server2. What I did was use rsync: rsync -avz /Users/jimmy/.ssh/id_rsa.pub jimmy@ip-address-of-Server2:/Users/jimmy2/.ssh/ This bit: rsync -avz /Users/jimmy/.ssh/id_rsa.pub Will sync the file -- id_rsa.pub from Server1 to the user account of 'jimmy2' on Server2. It will put that file into: /Users/jimmy2/.ssh/ So now you can SSH into Server2, you will still be prompted for a password. Go into the .ssh directory for the user you synced the id_rsa.pub file too, in this example the user is jimmy2: cd ~/.ssh/ Now type: mv id_rsa.pub authorized_keys You can even copy and paste that command. That command will just rename the id_rsa.pub file to 'authorized_keys'. Now if all went well you can SSH from Server1 to Server2 and not be prompted for a password! This is a really excellent technique for moving files such as backups or when making mirror(s) of a website and not needing to input the password to the server(s) each time! A note of warning though! If you remember when we were making our special key it prompted to input a passphrase, the passphrase makes your key more secure, but it will prompt you for that passphrase every time you want to connect defeating the purpose of this exercise. You should also keep track of which servers/clients can connect to each other without a password. It's also possible to get Server2 to go into Server1 without requiring a password. Follow the same steps to create the key, I renamed it to id_rsa2.pub and then used rsync to move it to Server1. Then I just renamed it authorized_keys using the above 'mv' command. Good luck! I used this website to help me: http://ammonlauritzen.com/blog/index.php/2006/04/16/shared_key_ssh_authentication post comment

navigation [ viewing | April 17th, 2007 ] [ go | previous day|next day ]