Today one of our production machine (in Amazon EC2) was down and I couldn’t bring-up the instance due to unavailability of SSH in PORT 22, connection was refused and I had no clue what to do, after sometime I was able to bring-up the instance – (ok short and sweet).
Though I got it working after some work-around, I wanted to make sure what I did was correct, hence I asked experts in stackoverflow.com – got good advice/suggestion and I hope all set for a fix. BTW, the answer on the question also helped in learning a new stuff called auditd on the disk – a must have tool for system admin.
Okay, the reason why I wanted to pin-down this blog is to show what I did to fix /dev/urandomand how did I get the server up and running. Let me go straight to there.
Today I am going to talk about only installation of tools/apps required for LINUX Server. I have chosen DEBIAN, since it makes you intelligent ;-).
Okay, cool, now? First thing you have to buy a hosting space, there are quite a good people who provide this service – do a quick Google.
OKAY – Now let’s say you have got the hosting space and you have selected the DEBIAN (LENNY) OSand logged into the machine – remember DEBIAN is for intelligent & its not for human-beings means most of the tools/apps will require a separate installation. You have to dive deeper to figure out the tools you want and install them – this is interesting because it let’s you know things :-).
This blog post is recommended for those users who knows about LINUX SERVER & shouldn’t find the meaning of Debian in the dictionary.
“OMG, not again” this is what I say when-ever I ran a svn commit/update command in cos-root machine. This ensures to have a secure transaction between the repository server to the server where the file is being updated, but at some point of time you can’t type-in your password each time :-(, but make sure your transaction is secured.
Follow these steps and have a happy relaxed life ;-).
To log in from machine A to machine B via ssh without a password (assume same username):
On machine A:
Run `ssh-keygen -t dsa`. Hit enter at every prompt (do NOT enter a passphrase).
This produces two files: id_dsa.pub (public key) and id_dsa (private key)
Copy you public key.
On machine B:
Edit or create the file ~/.ssh/authorized_keys.
Paste in the public key you copied from machine A. Note that the key is a single really long line.