Re: Secondary SSH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I 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?

The solution was provided through the openssh mailing list. I've added
an alias to my system and will use it when connecting from JuiceSSH:

   alias xssh="unset SSH_AUTH_SOCK; ssh"
-- 
Dave Close, Compata, Irvine CA          "Whenever you have a secret,
dave@xxxxxxxxxxx, +1 714 434 7359        you have a vulnerability."
dhclose@xxxxxxxxxxxxxxxxxx                  -- Whitfield Diffie


-- 
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux