What are the various levels in ssh -vvv: debug1, debug2, debug3

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












Is each a different side of the connection or a deeper layer of logging. I am interested because of, for example, this excerpt from a vvv output



debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection reset by nnnn port 22


Looking through the output I can't determine which side is saying what.










share|improve this question



























    up vote
    -1
    down vote

    favorite












    Is each a different side of the connection or a deeper layer of logging. I am interested because of, for example, this excerpt from a vvv output



    debug3: send packet: type 30
    debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
    Connection reset by nnnn port 22


    Looking through the output I can't determine which side is saying what.










    share|improve this question

























      up vote
      -1
      down vote

      favorite









      up vote
      -1
      down vote

      favorite











      Is each a different side of the connection or a deeper layer of logging. I am interested because of, for example, this excerpt from a vvv output



      debug3: send packet: type 30
      debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
      Connection reset by nnnn port 22


      Looking through the output I can't determine which side is saying what.










      share|improve this question















      Is each a different side of the connection or a deeper layer of logging. I am interested because of, for example, this excerpt from a vvv output



      debug3: send packet: type 30
      debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
      Connection reset by nnnn port 22


      Looking through the output I can't determine which side is saying what.







      openssh






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 at 4:12









      Rui F Ribeiro

      38.3k1475127




      38.3k1475127










      asked Nov 22 at 19:40









      Stephen Boston

      1848




      1848




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote













          In ssh I have noticed that:



          ssh -v
          will tell you what is happening mostly on your end
          ssh -vv
          will tell you low level on both ends
          ssh -vvv
          will tell you almost everything from both ends.


          Hence the conversation :



          debug1:Some useful information from 1
          debug2:Some useful information from 2
          debug1:Some useful information from 1
          debug3:Some useful information about what is passing between both and more..





          share|improve this answer



























            up vote
            0
            down vote













            The short answer:



            Yes!



            The long answer:



            From man ssh:




            -v


              Verbose mode.  Causes ssh to print debugging messages about its
              progress.  This is helpful in debugging connection, authentication, and configuration problems.  Multiple -v options increase
              the verbosity.
                The maximum is 3.


            To see what it really does, have a look at the edits on this question as we asked the OP to go from -v to -vvv (Debug levels 2 and 3 for -vv and -vvv respectively)






            share|improve this answer






















            • Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
              – Stephen Boston
              Nov 22 at 20:09










            • At your service. Answer edited. :-) @StephenBoston
              – Fabby
              Nov 22 at 22:55










            • @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
              – Fabby
              Nov 23 at 13:42










            • @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
              – G-Man
              Nov 23 at 22:38










            • (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
              – G-Man
              Nov 23 at 22:38











            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            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',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f483528%2fwhat-are-the-various-levels-in-ssh-vvv-debug1-debug2-debug3%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            In ssh I have noticed that:



            ssh -v
            will tell you what is happening mostly on your end
            ssh -vv
            will tell you low level on both ends
            ssh -vvv
            will tell you almost everything from both ends.


            Hence the conversation :



            debug1:Some useful information from 1
            debug2:Some useful information from 2
            debug1:Some useful information from 1
            debug3:Some useful information about what is passing between both and more..





            share|improve this answer
























              up vote
              1
              down vote













              In ssh I have noticed that:



              ssh -v
              will tell you what is happening mostly on your end
              ssh -vv
              will tell you low level on both ends
              ssh -vvv
              will tell you almost everything from both ends.


              Hence the conversation :



              debug1:Some useful information from 1
              debug2:Some useful information from 2
              debug1:Some useful information from 1
              debug3:Some useful information about what is passing between both and more..





              share|improve this answer






















                up vote
                1
                down vote










                up vote
                1
                down vote









                In ssh I have noticed that:



                ssh -v
                will tell you what is happening mostly on your end
                ssh -vv
                will tell you low level on both ends
                ssh -vvv
                will tell you almost everything from both ends.


                Hence the conversation :



                debug1:Some useful information from 1
                debug2:Some useful information from 2
                debug1:Some useful information from 1
                debug3:Some useful information about what is passing between both and more..





                share|improve this answer












                In ssh I have noticed that:



                ssh -v
                will tell you what is happening mostly on your end
                ssh -vv
                will tell you low level on both ends
                ssh -vvv
                will tell you almost everything from both ends.


                Hence the conversation :



                debug1:Some useful information from 1
                debug2:Some useful information from 2
                debug1:Some useful information from 1
                debug3:Some useful information about what is passing between both and more..






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 20:35









                Michael Prokopec

                62115




                62115






















                    up vote
                    0
                    down vote













                    The short answer:



                    Yes!



                    The long answer:



                    From man ssh:




                    -v


                      Verbose mode.  Causes ssh to print debugging messages about its
                      progress.  This is helpful in debugging connection, authentication, and configuration problems.  Multiple -v options increase
                      the verbosity.
                        The maximum is 3.


                    To see what it really does, have a look at the edits on this question as we asked the OP to go from -v to -vvv (Debug levels 2 and 3 for -vv and -vvv respectively)






                    share|improve this answer






















                    • Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                      – Stephen Boston
                      Nov 22 at 20:09










                    • At your service. Answer edited. :-) @StephenBoston
                      – Fabby
                      Nov 22 at 22:55










                    • @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                      – Fabby
                      Nov 23 at 13:42










                    • @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                      – G-Man
                      Nov 23 at 22:38










                    • (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                      – G-Man
                      Nov 23 at 22:38















                    up vote
                    0
                    down vote













                    The short answer:



                    Yes!



                    The long answer:



                    From man ssh:




                    -v


                      Verbose mode.  Causes ssh to print debugging messages about its
                      progress.  This is helpful in debugging connection, authentication, and configuration problems.  Multiple -v options increase
                      the verbosity.
                        The maximum is 3.


                    To see what it really does, have a look at the edits on this question as we asked the OP to go from -v to -vvv (Debug levels 2 and 3 for -vv and -vvv respectively)






                    share|improve this answer






















                    • Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                      – Stephen Boston
                      Nov 22 at 20:09










                    • At your service. Answer edited. :-) @StephenBoston
                      – Fabby
                      Nov 22 at 22:55










                    • @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                      – Fabby
                      Nov 23 at 13:42










                    • @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                      – G-Man
                      Nov 23 at 22:38










                    • (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                      – G-Man
                      Nov 23 at 22:38













                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    The short answer:



                    Yes!



                    The long answer:



                    From man ssh:




                    -v


                      Verbose mode.  Causes ssh to print debugging messages about its
                      progress.  This is helpful in debugging connection, authentication, and configuration problems.  Multiple -v options increase
                      the verbosity.
                        The maximum is 3.


                    To see what it really does, have a look at the edits on this question as we asked the OP to go from -v to -vvv (Debug levels 2 and 3 for -vv and -vvv respectively)






                    share|improve this answer














                    The short answer:



                    Yes!



                    The long answer:



                    From man ssh:




                    -v


                      Verbose mode.  Causes ssh to print debugging messages about its
                      progress.  This is helpful in debugging connection, authentication, and configuration problems.  Multiple -v options increase
                      the verbosity.
                        The maximum is 3.


                    To see what it really does, have a look at the edits on this question as we asked the OP to go from -v to -vvv (Debug levels 2 and 3 for -vv and -vvv respectively)







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Nov 22 at 23:45









                    G-Man

                    12.3k92961




                    12.3k92961










                    answered Nov 22 at 19:57









                    Fabby

                    3,14911127




                    3,14911127











                    • Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                      – Stephen Boston
                      Nov 22 at 20:09










                    • At your service. Answer edited. :-) @StephenBoston
                      – Fabby
                      Nov 22 at 22:55










                    • @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                      – Fabby
                      Nov 23 at 13:42










                    • @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                      – G-Man
                      Nov 23 at 22:38










                    • (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                      – G-Man
                      Nov 23 at 22:38

















                    • Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                      – Stephen Boston
                      Nov 22 at 20:09










                    • At your service. Answer edited. :-) @StephenBoston
                      – Fabby
                      Nov 22 at 22:55










                    • @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                      – Fabby
                      Nov 23 at 13:42










                    • @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                      – G-Man
                      Nov 23 at 22:38










                    • (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                      – G-Man
                      Nov 23 at 22:38
















                    Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                    – Stephen Boston
                    Nov 22 at 20:09




                    Thank you. I understand that from my own reading of the man page. I am wondering how the verbosity is increased. Is there a principle or policy? Does a double v look more deeply into one side of the connection process or one aspect of the connection process than a single v or are the verbosity levels based on the whim of whichever developer is working on that piece of code. I'll add a piece to my question.
                    – Stephen Boston
                    Nov 22 at 20:09












                    At your service. Answer edited. :-) @StephenBoston
                    – Fabby
                    Nov 22 at 22:55




                    At your service. Answer edited. :-) @StephenBoston
                    – Fabby
                    Nov 22 at 22:55












                    @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                    – Fabby
                    Nov 23 at 13:42




                    @G-Man: Is that the standard here on U&L? Quotes from man pages to be formatted as quotes and link to be included? Thanks for the edit!
                    – Fabby
                    Nov 23 at 13:42












                    @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                    – G-Man
                    Nov 23 at 22:38




                    @Fabby: Well, I wouldn't say that it's standard, per se. I do it whenever I see a man page excerpt formatted as a code block, particularly when somebody copies a hyphenated word without putting the pieces back together (e.g., “authentica‐” / “tion”). After all, (1) It is a quote, (2) it's not code, and (3) when you format the excerpt as code, (3a) you make it hard to use italic and bold formatting (i.e., if you just indent four spaces), (3b) you make it impossible to format individual words (e.g., command line options) as code, … (Cont’d)
                    – G-Man
                    Nov 23 at 22:38












                    (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                    – G-Man
                    Nov 23 at 22:38





                    (Cont’d) …  and (3c) you set the line breaks (i.e., the right margin) of the source you copied from in concrete for everybody, which means wasted space on the right for some people and horizontal scrolling for others.  (Of course block quotes word-wrap just like ordinary text.) (4) Also, of course, our anti-plagiarism policy requires that all quotes be linked to a source.  Some people play fast and loose with that rule for man pages; I believe that linking is the right thing to do.
                    – G-Man
                    Nov 23 at 22:38


















                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2funix.stackexchange.com%2fquestions%2f483528%2fwhat-are-the-various-levels-in-ssh-vvv-debug1-debug2-debug3%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

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?