On Tue, 1 Nov 2016, Jim Garrison wrote: > If you generated a new keypair, you'll have to transfer the public key to > the target system (the one you want to connect TO) and put it in > ~/.ssh/authorized_keys. ssh-copy-id does this but it must be able to ssh > into the target system, either with the old private key or a password. If > you cannot ssh into the target system currently, then you cannot deploy > the new public key over the network. You must find some other way to get > the public key to the target.
Jin, I thought this was the case. After reading the ssh-copy-id man page and some web fora threads I thought that I'd be asked to provide my password on the target/remote host before ssh-copy-id did its thing. But, the ssh connection is being refused in both directions so I'm not asked for a password. My suspicion is that even after transferring the public key to the remote host the ssh connection will still be refused. Testing will need to wait until late this afternoon. Will update status as I go. Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
