{"action":"created","issue":{"url":"https://api.github.com/repos/squash/sudosh2/issues/16","repository_url":"https://api.github.com/repos/squash/sudosh2","labels_url":"https://api.github.com/repos/squash/sudosh2/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/squash/sudosh2/issues/16/comments","events_url":"https://api.github.com/repos/squash/sudosh2/issues/16/events","html_url":"https://github.com/squash/sudosh2/issues/16","id":173029349,"number":16,"title":"sudosh2 drops ssh environment variables","user":{"login":"rfifarek","id":17889857,"avatar_url":"https://avatars.githubusercontent.com/u/17889857?v=3","gravatar_id":"","url":"https://api.github.com/users/rfifarek","html_url":"https://github.com/rfifarek","followers_url":"https://api.github.com/users/rfifarek/followers","following_url":"https://api.github.com/users/rfifarek/following{/other_user}","gists_url":"https://api.github.com/users/rfifarek/gists{/gist_id}","starred_url":"https://api.github.com/users/rfifarek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rfifarek/subscriptions","organizations_url":"https://api.github.com/users/rfifarek/orgs","repos_url":"https://api.github.com/users/rfifarek/repos","events_url":"https://api.github.com/users/rfifarek/events{/privacy}","received_events_url":"https://api.github.com/users/rfifarek/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-24T18:50:07Z","updated_at":"2016-08-24T20:32:03Z","closed_at":null,"body":"When using SSH agent forwarding, sudosh2 doesn't preserve SSH environment variables that support agent forwarding, preventing chaining.\r\n\r\nFor example, in a situation like client1 -> root@server1 -> root@server2\r\n\r\n- client1 has private ssh key access to root@server1 and root@server2, and ssh-agent has the key loaded \r\n- root@server1 and root@server2 are both set to /usr/bin/sudosh as login shell, and /etc/sudosh.conf has /bin/bash as the default shell.\r\n\r\nIf I ssh -A root@server1, ssh -A root@server2 does not work as expected, because SSH_AUTH_SOCK is not preserved/set.  I can manually set SSH_AUTH_SOCK, as a work around.\r\n\r\nIf I switch the login shell for root@server1 to /bin/bash, SSH_AUTH_SOCK is preserved, and I can chain connections as expected.\r\n"},"comment":{"url":"https://api.github.com/repos/squash/sudosh2/issues/comments/242198469","html_url":"https://github.com/squash/sudosh2/issues/16#issuecomment-242198469","issue_url":"https://api.github.com/repos/squash/sudosh2/issues/16","id":242198469,"user":{"login":"rfifarek","id":17889857,"avatar_url":"https://avatars.githubusercontent.com/u/17889857?v=3","gravatar_id":"","url":"https://api.github.com/users/rfifarek","html_url":"https://github.com/rfifarek","followers_url":"https://api.github.com/users/rfifarek/followers","following_url":"https://api.github.com/users/rfifarek/following{/other_user}","gists_url":"https://api.github.com/users/rfifarek/gists{/gist_id}","starred_url":"https://api.github.com/users/rfifarek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rfifarek/subscriptions","organizations_url":"https://api.github.com/users/rfifarek/orgs","repos_url":"https://api.github.com/users/rfifarek/repos","events_url":"https://api.github.com/users/rfifarek/events{/privacy}","received_events_url":"https://api.github.com/users/rfifarek/received_events","type":"User","site_admin":false},"created_at":"2016-08-24T20:32:03Z","updated_at":"2016-08-24T20:32:03Z","body":"Cool, I didn't know of that config option - that fixed it, thanks!\n\nCan you add that to the man page?\n\nOn Wed, Aug 24, 2016 at 1:09 PM, squash <notifications@github.com> wrote:\n\n>\n> Is this with 'clearenvironment=no' in sudosh.conf?\n>\n>\n> On 08/24/2016 02:50 PM, rfifarek wrote:\n> > When using SSH agent forwarding, sudosh2 doesn't preserve SSH\n> > environment variables that support agent forwarding, preventing chaining.\n> >\n> > For example, in a situation like client1 -> root@server1 -> root@server2\n> >\n> > * client1 has private ssh key access to root@server1 and root@server2,\n> > and ssh-agent has the key loaded\n> > * root@server1 and root@server2 are both set to /usr/bin/sudosh as\n> > login shell, and /etc/sudosh.conf has /bin/bash as the default shell.\n> >\n> > If I ssh -A root@server1, ssh -A root@server2 does not work as expected,\n> > because SSH_AUTH_SOCK is not preserved/set. I can manually set\n> > SSH_AUTH_SOCK, as a work around.\n> >\n> > If I switch the login shell for root@server1 to /bin/bash, SSH_AUTH_SOCK\n> > is preserved, and I can chain connections as expected.\n> >\n> > —\n> > You are receiving this because you are subscribed to this thread.\n> > Reply to this email directly, view it on GitHub\n> > <https://github.com/squash/sudosh2/issues/16>, or mute the thread\n> > <https://github.com/notifications/unsubscribe-auth/\n> AAgMYWKlR6XTJy5Vurx7nzyCrPiRUlEbks5qjJJggaJpZM4JsVH9>.\n> >\n>\n> —\n> You are receiving this because you authored the thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/squash/sudosh2/issues/16#issuecomment-242191984>, or mute\n> the thread\n> <https://github.com/notifications/unsubscribe-auth/ARD6Qaprjb1BGWn_S34d24FDNi-1bIx_ks5qjKUIgaJpZM4JsVH9>\n> .\n>\n\n\n\n-- \nRichard H. Fifarek\nrfifarek@gmail.com\n"}}
{"actor":{"display_login":"rfifarek"}}