You have a few options, (like creating an alias for the command you
don't want to type) but the "cleanest" would be to generate your own
set of keys with
ssh-keygen -t rsa
and put the the keys in the default location offered by the comand.
(You could also move his private key to your .ssh directory and give
it the default name, or tell ssh in a config file to use that key where
ever it is and whatever it is called, but
as you did not generate that key I would go with the "make it
yourself" option)
then use your uncle's key two more times, first use it to scp your new
public key over to his machine, then use it to ssh in to his machine
and add it to his .ssh/authorized_keys file.
Now you can use ssh or scp without giving the key because his side
will accept your default key.
As for ssh-add and such, that only applies if you have given a
passphrase when you created the keys. If you do, it's a good way to
go. If you don't it does not apply. I would of course recomend that
you do use a pasphrase but I do not know your security
issues/priorities and it sounds like convenience is high on your
priority list.
-Greg
--
Greg Priest-Dorman
[EMAIL PROTECTED]
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) MHVLS Auditorium
Feb 6 - DBUS
Mar 5 - Setting up a platform-independent home/small office network using
Linux
