[Sugar-devel] I reinstalled my system back to a previous image, but don't know where to put my public key for gitorious

[James Cameron]

On Thu, Jun 02, 2011 at 09:49:36AM +0200, laurent bernabe wrote:
> * for my system instability, i fixed it by installing Xubuntu instead
> of Kubuntu (my laptop begins to be old).

It sounds like your instability was due to not enough system memory.

Add more memory; on physical hardware is one way, on a virtual guest
make sure enough of the physical memory of the host is made available to
the guest.

For development of Sugar activities, 512MB might be a reasonable
minimum.  Avoid opening too many applications at once.

> So another question come to me : if i change of computer, i presume
> that i will have to generate a new key pair (as the public key ends
> with my system account). Am i right ?

Yes, but only if you failed to keep a copy of the key pair.  That's what
step 2 in my careful actions was for.

Normally before I reinstall a computer, I take off any data that I might
need.  The .ssh directory is one such important thing.

If you lose the .ssh directory, then you MUST ssh-keygen and then "Add
SSH key" again.

> * i generated a new keys pair, but i was still unable to confirm my
> key on sugar gitorious. I joined the script file of my terminal.

> $ ssh gitorious at git.sugarlabs.org true
> The authenticity of host 'git.sugarlabs.org (18.85.44.120)' can't be established.
> RSA key fingerprint is 4f:5e:5c:7f:ca:94:49:9d:2e:77:85:86:7c:de:56:f1.
> Are you sure you want to continue connecting (yes/no)? no

I'm shocked and surprised.  Why did you say no?  You should say yes at
this point.  I can confirm that the RSA key fingerprint of
git.sugarlabs.org is indeed what you see displayed.  Please try again,
and this time say yes.

Because you said no, we cannot tell from your attachment if the key is
properly stored.

--

Another way to check that gitorious has your key properly stored:

Please go to http://git.sugarlabs.org/ and login, then click on "Manage
SSH keys", and note the Algorithm Fingerprint that is displayed.

Then, on your system, display the key fingerprint, like so:

	ssh-keygen -l -f id_rsa

Compare the two fingerprint values carefully.  They must match.  If they
do not match, it will be because you have not yet uploaded the new key,
therefore you must "Add SSH key" again.

-- 
James Cameron
http://quozl.linux.org.au/