> If you have it set up like A -> B where A is your workstation and B is > your server so that A has your private key and B has your public key > what happens if you now want to log into another remote server C (A -> B > -> C)?
Use agent forwarding. It will forward your key authentication-challenge request from C to B to A. The response will be forwarded back out again. > Should you copy your private key from A to B or should you generate a > new private key on B for the B -> C login? Neither. > I would guess that copying your private key to B would be a bad idea as > if B is compromised then they have your private key and maybe even track > your keystrokes as you enter your passphrase right? > > Does the agent-forwarding help in this case and how is it implemented? Read the docs on agent forwarding. THe OReilley book is also very good on the subject. Simple way is: o Run 'ssh-agent bash' o Use ssh-add to add your key(s). o SSH into server B from A. o SSH into server C from B. Assuming you have agent forwarding enabled on B (or you force it with the command line option), and assuming that C is configured to accept the same credentials as B, you shouldn't have any problems. thornton -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
