On Fri, Aug 23, 2024 at 5:44 PM Dave Close <dave@xxxxxxxxxxx> wrote:
>
> I have several local machines that, while working, I frequently use ssh
> to do something on a different machine. While on that second machine,
> I may even use ssh to do something on a third machine. All of this
> works exactly as it should.
>
> If I use JuiceSSH on my Android phone to contact one of my local
> machines, that also works well. But if, while connected, I try
> to start an ssh session to a different local machine, it simply
> times out. The last message seen with "ssh -vvv" is, "debug3:
> ssh_get_authentication_socket_path:". Up to that point, the output
> of "ssh -vvv" is identical when running successfully between two
> local machines without using JuiceSSH.
>
> If instead of trying to start an ssh session immediately upon
> connecting with JuiceSSH, I first use sudo to become root on the
> local machine and then try to ssh to another local machine, that works
> perfectly (provided, of course, that the second machine permits root
> ssh login). The second ssh session also works if I simply run "sudo
> su {me} -c ssh" so becoming root isn't the key.
>
> Summary:
> JuiceSSH -> user@machine1 -> user@machine2 :: FAILS
> JuiceSSH -> user@machine1 -> sudo on machine1 -> user@machine2 :: WORKS
>
> I've examined the output of the set command for all of these situations
> and can't find any variables that are different that seem relevant. (Of
> course, $PPID and similar variables are different.) Can anyone suggest
> what could be the issue? Or what other tests might be helpful?
I hope the sudo did not create directories with the wrong ownership.
And SSH sometimes fails if directory permissions are not expected,
like allow Others read or write access to .ssh/ directory.
At this point, I would visit each machine and:
mkdir -p ~/.ssh
chown -R dclose:dclose ~/.ssh
chmod -R o-rwx ~/.ssh
Jeff
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
