ssh -- from local/userA --> remote/userB

[bruce]

Hi.

Sorry to even ask htis basic question.

I'm trying to do something like:
 userA: ssh userB(a)1.2.3.4

so I'm on the local box as userA

trivially .. ssh userA(a)1.2.3.4 works as it should with the pub/private
keys established as required.

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/config need to be changed to
accomodate some items for the userB?

currently, running
userA   -- ssh userB(a)1.2.3.4

gets
key_read: uudecode
AAAAB3NzaC1yc2EAAAABIwAAAQEArGwWyWyDoO2rlXVg6MjVlAXg8zbzwuNtRaNn9OILVY+YhzAQGmCG5XkQT6ZRICkMfgNo3dAHUtKZsq0nVCdcgCabP
 failed

but I am in the remote box as userB.

Haven't found anything on the net to solve this.. which is odd!

thanks

[Garry T. Williams]

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/config need to be changed to
>  accomodate some items for the userB? 
Add your public key(s) to userB's .ssh/authorized_keys file.

-- 
Garry T. Williams

[bruce]

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 <gtwilliams(a)gmail.com&gt; wrote:
> 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/config need to be changed to
>> accomodate some items for the userB?
>
> Add your public key(s) to userB's .ssh/authorized_keys file.
>
> --
> Garry T. Williams
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Cameron Simpson]

On 08Sep2018 17:43, bruce <badouglas(a)gmail.com&gt; 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 that.

If you have root privileges on machine B you can look at the ssh log 
(/var/log/auth.log or something else, depending on the system - "ls -ltra" in 
/var/log will at least show you the active log files to make finding it easy).

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. They can be very helpful in 
distinguishing "ssh going to wrong host" (no activity), "ssh as wrong user
on 
machine B", "ssh as user B but bad keys" and so forth.

For security reasons you see little of this detail on the machine A side as all 
such information helps attackers.

Cheers,
Cameron Simpson <cs(a)cskk.id.au&gt;

[Garry T. Williams]

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 systemd-journal groups.

Finding log messages of interest is easier using the journal.

This is a fine article:

   
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to...


-- 
Garry T. Williams