Pass SSH Escape into nested SSH session












1















Suppose I ssh from my laptop to a server alpha, then from there ssh to a server beta.



If the connection from alpha to beta dies, is it possible to pass SSH's escape (~.) across the ssh connection from my laptop to alpha, to the ssh client connected to beta?










share|improve this question



























    1















    Suppose I ssh from my laptop to a server alpha, then from there ssh to a server beta.



    If the connection from alpha to beta dies, is it possible to pass SSH's escape (~.) across the ssh connection from my laptop to alpha, to the ssh client connected to beta?










    share|improve this question

























      1












      1








      1








      Suppose I ssh from my laptop to a server alpha, then from there ssh to a server beta.



      If the connection from alpha to beta dies, is it possible to pass SSH's escape (~.) across the ssh connection from my laptop to alpha, to the ssh client connected to beta?










      share|improve this question














      Suppose I ssh from my laptop to a server alpha, then from there ssh to a server beta.



      If the connection from alpha to beta dies, is it possible to pass SSH's escape (~.) across the ssh connection from my laptop to alpha, to the ssh client connected to beta?







      ssh






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 4 '14 at 15:10









      Matthew G.Matthew G.

      12112




      12112






















          1 Answer
          1






          active

          oldest

          votes


















          3














          I think man ssh says it all:




          -e escape_char

          Sets the escape character for sessions with a pty (default: ‘~’).
          The escape character is only recognized at the beginning of a
          line. The escape character followed by a dot (‘.’) closes the
          connection; followed by control-Z suspends the connection; and
          followed by itself sends the escape character once
          . Setting the
          character to “none” disables any escapes and makes the session
          fully transparent.




          You need to send ~~. Alternatively you could change the escape character for every ssh hop you take with ssh -e escape_char.



          You can also specify it as a runtime option; e.g. -o EscapeChar=:



          Thus you may also add it to your client config file ${HOME}/.ssh/config.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f848492%2fpass-ssh-escape-into-nested-ssh-session%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            I think man ssh says it all:




            -e escape_char

            Sets the escape character for sessions with a pty (default: ‘~’).
            The escape character is only recognized at the beginning of a
            line. The escape character followed by a dot (‘.’) closes the
            connection; followed by control-Z suspends the connection; and
            followed by itself sends the escape character once
            . Setting the
            character to “none” disables any escapes and makes the session
            fully transparent.




            You need to send ~~. Alternatively you could change the escape character for every ssh hop you take with ssh -e escape_char.



            You can also specify it as a runtime option; e.g. -o EscapeChar=:



            Thus you may also add it to your client config file ${HOME}/.ssh/config.






            share|improve this answer






























              3














              I think man ssh says it all:




              -e escape_char

              Sets the escape character for sessions with a pty (default: ‘~’).
              The escape character is only recognized at the beginning of a
              line. The escape character followed by a dot (‘.’) closes the
              connection; followed by control-Z suspends the connection; and
              followed by itself sends the escape character once
              . Setting the
              character to “none” disables any escapes and makes the session
              fully transparent.




              You need to send ~~. Alternatively you could change the escape character for every ssh hop you take with ssh -e escape_char.



              You can also specify it as a runtime option; e.g. -o EscapeChar=:



              Thus you may also add it to your client config file ${HOME}/.ssh/config.






              share|improve this answer




























                3












                3








                3







                I think man ssh says it all:




                -e escape_char

                Sets the escape character for sessions with a pty (default: ‘~’).
                The escape character is only recognized at the beginning of a
                line. The escape character followed by a dot (‘.’) closes the
                connection; followed by control-Z suspends the connection; and
                followed by itself sends the escape character once
                . Setting the
                character to “none” disables any escapes and makes the session
                fully transparent.




                You need to send ~~. Alternatively you could change the escape character for every ssh hop you take with ssh -e escape_char.



                You can also specify it as a runtime option; e.g. -o EscapeChar=:



                Thus you may also add it to your client config file ${HOME}/.ssh/config.






                share|improve this answer















                I think man ssh says it all:




                -e escape_char

                Sets the escape character for sessions with a pty (default: ‘~’).
                The escape character is only recognized at the beginning of a
                line. The escape character followed by a dot (‘.’) closes the
                connection; followed by control-Z suspends the connection; and
                followed by itself sends the escape character once
                . Setting the
                character to “none” disables any escapes and makes the session
                fully transparent.




                You need to send ~~. Alternatively you could change the escape character for every ssh hop you take with ssh -e escape_char.



                You can also specify it as a runtime option; e.g. -o EscapeChar=:



                Thus you may also add it to your client config file ${HOME}/.ssh/config.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 22 at 14:32

























                answered Dec 4 '14 at 15:19









                Werner HenzeWerner Henze

                3,95931229




                3,95931229






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f848492%2fpass-ssh-escape-into-nested-ssh-session%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Список кардиналов, возведённых папой римским Каликстом III

                    Deduzione

                    Mysql.sock missing - “Can't connect to local MySQL server through socket”