actually all the keys were created when I installed the packages. I really
appreciated that because at the time when I was installing them I wasn't
able to find any kind of documentation anywhere for this app.

-- 
Mark

"If you don't share your concepts and ideals, they end up being worthless,"
"Sharing is what makes them powerful."

                                Linus Torvalds

On Thu, 11 Jan 2001, Tim Holmes wrote:

> I agree with Holly.  This took me a good 3 days with trial and error
> before I got this set up to work.  But use her instructions, I think
> she's point you upon the right path.
>
> When you create your key in your .ssh/ directory, it askes you to set
> a passwd for it.  Well it DOES not have to be the passwd for that
> account.  You're creating a passwd for that key.  So your passwd for
> that user account could be KICK and the passwd for your SSH key could
> be ASS and there will be no problems.
>
> Here's what I have in my .ssh/ directory.
>
> [timh@yoda ~/.ssh]$ ls -la
> total 24
> drwx------    2 timh     timh         4096 Nov 10 12:16 ./
> drwx------   51 timh     timh         4096 Jan 10 22:43 ../
> -rw-------    1 timh     timh          524 Nov 10 05:57 identity
> -rw-rw-r--    1 timh     timh          328 Nov 10 05:57 identity.pub
> -rw-r--r--    1 timh     timh         2752 Jan  7 23:03 known_hosts
> -rw-r--r--    1 timh     timh         1212 Nov 10 13:22 known_hosts2
>
> I ssh from/into about 15 different machines.  (A lot of them are at work,
> and require ssh or you're  SOL.)   So that's why I have a second known_hosts
> file.  Not sure how many that can hold but that's why there's a second one
> there.  Running the ssh-keygen will create the identity and identity.pub for
> you.
>
> If needed you can delete your identity and identity.pub and then create new
> ones.  Unless you've set some sort of setting via command line to not allow
> random ssh connections, all you should have to do is then type your command.
>
> ssh -l <userID> machine.name.com
>
> Enter in the correct ssh passwd, which may be refered to RSA, and you should
> be in.
>
> palladium:~> huh RSA
>
>    Found nothing in the ANS database
>    You might want to use the -s/--searchall option
>
>    Looking up "RSA" in Free OnLine Dictionary of Computing RSA
>
>    <cryptography, company> (The initials of the authors)
>    1. RSA Data Security, Inc.
>    2. Their cryptography systems, especially RSA encryption.
>    The RSA algorithm was first described in the paper:
>    [R. Rivest, A. Shamir, L. Adleman, "A Method for Obtaining Digital
>    Signatures and Public-key Cryptosystems". CACM 21,2; 1978]
>    (1995-03-21)
>    Try this search on OneLook / Google
>
> So I hopefully that be a bit more helpful, but Holly was on the right track.
> (I just like showing off by providing much more information then ever needed
> lol)  Thanx Holly, good luck Mark.
> tdh
> --
> T. Holmes
> Unixtechs.org
> [EMAIL PROTECTED]
> www.unixtechs.org/
>
> "Real Men use Vi."
>
>
> * Mark Weaver <[EMAIL PROTECTED]> [010110 19:30]:
> > Tim,
> >
> > I've got all these packages installed and I'm not able to connect to my
> > machine using ssh. When I get to the login it asks me for the passwd and
> > then refuses the connection. Are there other files that need to be
> > configured or something that I'm missing?
> >
> > --
> > Mark
> >
> > "If you don't share your concepts and ideals, they end up being worthless,"
> > "Sharing is what makes them powerful."
> >
> >                             Linus Torvalds
> >     >>>>>>>>>>>>>>>>>>>>>>REPLY BELOW<<<<<<<<<<<<<<<<<<<<<<<
>


Reply via email to