On Saturday, September 8, 2018 6:52:59 PM EDT Cameron Simpson wrote:
> If you "tail -f /var/log/auth.log" (adjust to suit) on machine B as
> you do your sshes you will see useful log messages scroll by.
Or just do
$ journalctl -b -u sshd.service
if you are a member of either the wheel or sys
On 08Sep2018 17:43, bruce wrote:
Thanks for replies, found the answer was a weird corrupt
authorized_key file. Simply copied the pub keys and reinserted. For
some reason, it appears that one of the pub keys had been split witn a
"\n" in it..
Cut/paste from a terminal or email can sometimes do
Hi/Hey.
Thanks for replies, found the answer was a weird corrupt
authorized_key file. Simply copied the pub keys and reinserted. For
some reason, it appears that one of the pub keys had been split witn a
"\n" in it..
thanks
On Sat, Sep 8, 2018 at 5:27 PM, Garry T. Williams wrote:
> On Saturda
On Saturday, September 8, 2018 2:52:39 PM EDT bruce wrote:
> However, I'm "confused" (missing something) regarding how to ssh
> into the remote box as a different user.
>
> Do I have to have a separate /home/userB/.ssh on both the local and
> remote box?
>
> Does the local "userA" /home/userA/.ssh/
Hi.
Sorry to even ask htis basic question.
I'm trying to do something like:
userA: ssh userB@1.2.3.4
so I'm on the local box as userA
trivially .. ssh userA@1.2.3.4 works as it should with the pub/private
keys established as required.
However, I'm "confused" (missing something) regarding how
