To be frank even though my host is Windows , my work normally happens in solaris/Linux boxes. For this I use Exceed as my remote login tool.

It was during while setting up the boxes I went through the SSh stuffs. After then even though I type daily atleast 10 times ssh command, I forgot the steps what happens internally .Its reallly bad right.So just thought of going through the basics of it and got landed at right place.

The basic steps are as follows:

1: Public and Private keys exist on the SSH server.(let's say 10.10.0.1) They were generated by the server Admin at the time SSH was first set up.

2: A user (10.10.0.30) attempts to ssh into the server (10.10.0.1). The server sends its PUBLIC KEY to the user.

3: The user checks to see if the PUBLIC KEY exists already in its system. If not, the user is warned that this key is not in the system. Once the user accepts the key, it is added to the trusted list.

4: The user (10.10.0.30) uses the server's PUBLIC KEY to encrypt all communications to the server (10.10.0.1). At the initial stage, this would include user name, password.

5: The user (10.10.0.30) also sends it's PUBLIC KEY to the server. (This is NOT the same as the Server's PUBLIC KEY). This is generated newly per every new SSH session(??)

6: The server uses it's own PRIVATE KEY to decrypt all communications from the user. (Which the user encrypted using the server's PUBLIC KEY) The server then uses the user's PUBLIC KEY to encrypt all communications before sending them on to the user.

7: The user then uses it's PRIVATE KEY to decrypt all communications send by the server. (Which the server encrypted using the user's PUBLIC KEY)

8: No one other than the server can decrypt packets encrypted with the server's PUBLIC KEY (Because only the server knows its own PRIVATE KEY).

9: No one other than the client can decrypt packets encrypted with the client's PUBLIC KEY (Because only the client knows its own PRIVATE KEY)

10: Points 8 & 9 work because the PUBLIC and PRIVATE keys are both huge primary numbers that are mathematically related, but would require an unimaginable number of calculations/computing power to derive one from the other.

In reference to: [other] How does SSH Work? - Ubuntu Forums (view on Google Sidewiki)

After I successfully Installed the GIT in my local user . I need to setup the remote repository in server end. When I am googling this I got this page which proves my work is done most. Setting up GIT remote server is as easy as creating the user in Unix.

They say its only 4 steps.

1) Install GIT what I did previously
2) Create one user git in your box.

sudo adduser git

3) Then Create the repository .

# login to remote server
ssh git@REMOTE_SERVER
# once logged in
mkdir example.git
cd example.git
git --bare init

4) Commit to this new repository .

mkdir example
cd example
git init
touch README
git add README
git commit -m 'first commit'
git remote add origin git@REMOTE_SERVER:example.git
git push origin master

With the above doc help I worked out in my local box and added few more steps .
To know more on this please see my sidewiki link.

in reference to:

"mkdir example cd example git init touch README git add README git commit -m 'first commit' git remote add origin git@REMOTE_SERVER:example.git git push origin master"
- CommonThread Blog Setting Up a Git Server (view on Google Sidewiki)

The Internet says the answer is GIT, so for the past few days I have been trying to learn something about GIT( but still Iam a CVS user).

Git is a free distributed revision control, or software source code management project with an emphasis on being fast. Git was initially designed and developed by Linus Torvalds for Linux kernel development.

Why the name GIT ?
Linus Torvalds has quipped about the name "git", which is British English slang for a stupid or unpleasant person. "I'm an egotistical bastard, and I name all my projects after myself. First Linux, now git." This self-deprecating humor is tongue-in-cheek, as Torvalds was actually pressured into naming Linux after himself .

I guess its enough of wikipedia's history let me share my little knowledge on GIT to you people. Before installing the server as your own, try this GITHUB social coding site . First create a free repository here, then install the GIT client in your end (I installed this in solaris, not a big deal just gzip -d , untar and make install ) . Just for the try I commited few files and checked it. Its really coooolllll.

Now my next step is to install the GIT server in my local box . I am not sure whether it will be easy or not ? After then its migration from CVS to GIT if possible. Let see how this project goes for me................

in reference to: jkamaraj's Gazolinia at master - GitHub (view on Google Sidewiki)

My working environment is something Interesting and funny , logging into remote servers ,digigng inside web logs , source codes etc . Nobody in our team of 3 , clearly knows how many modules we have in our application ,why that server running ? why that db breaks ? .To add this we have code of 1000 files each consisting around 1000 lines, without even a line of documentation . Eventhough it looks tough , it is really interesting to look at the code written by some great coders and understanding .