Cannot parse privateKey: Unsupported key format












1














In my Mac book pro with OS Majave, I used SSH-KEYGEN generate a new SSH key for node.js module SSH2. However, I got error message: Cannot parse privateKey: Unsupported key format



I validated the key with ssh command, it just works fine. But not with the node.js module SSH2.



In the private key file, the header is
-----BEGIN OPENSSH PRIVATE KEY----- while the end is -----END OPENSSH PRIVATE KEY-----.



I checked module ssh2-streams keyParser.js. The regexp pattern RE_HEADER_OPENSSH_PRIV does not include my header. Can anyone help?










share|improve this question
























  • I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
    – George Zhang
    Nov 20 '18 at 20:00










  • what parameters did you use for ssh-keygen ?
    – mihai
    Nov 21 '18 at 8:16










  • I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
    – George Zhang
    Nov 22 '18 at 18:47










  • the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
    – mihai
    Nov 22 '18 at 19:26
















1














In my Mac book pro with OS Majave, I used SSH-KEYGEN generate a new SSH key for node.js module SSH2. However, I got error message: Cannot parse privateKey: Unsupported key format



I validated the key with ssh command, it just works fine. But not with the node.js module SSH2.



In the private key file, the header is
-----BEGIN OPENSSH PRIVATE KEY----- while the end is -----END OPENSSH PRIVATE KEY-----.



I checked module ssh2-streams keyParser.js. The regexp pattern RE_HEADER_OPENSSH_PRIV does not include my header. Can anyone help?










share|improve this question
























  • I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
    – George Zhang
    Nov 20 '18 at 20:00










  • what parameters did you use for ssh-keygen ?
    – mihai
    Nov 21 '18 at 8:16










  • I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
    – George Zhang
    Nov 22 '18 at 18:47










  • the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
    – mihai
    Nov 22 '18 at 19:26














1












1








1


0





In my Mac book pro with OS Majave, I used SSH-KEYGEN generate a new SSH key for node.js module SSH2. However, I got error message: Cannot parse privateKey: Unsupported key format



I validated the key with ssh command, it just works fine. But not with the node.js module SSH2.



In the private key file, the header is
-----BEGIN OPENSSH PRIVATE KEY----- while the end is -----END OPENSSH PRIVATE KEY-----.



I checked module ssh2-streams keyParser.js. The regexp pattern RE_HEADER_OPENSSH_PRIV does not include my header. Can anyone help?










share|improve this question















In my Mac book pro with OS Majave, I used SSH-KEYGEN generate a new SSH key for node.js module SSH2. However, I got error message: Cannot parse privateKey: Unsupported key format



I validated the key with ssh command, it just works fine. But not with the node.js module SSH2.



In the private key file, the header is
-----BEGIN OPENSSH PRIVATE KEY----- while the end is -----END OPENSSH PRIVATE KEY-----.



I checked module ssh2-streams keyParser.js. The regexp pattern RE_HEADER_OPENSSH_PRIV does not include my header. Can anyone help?







node.js ssh openssh ssh-keygen ssh2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 '18 at 8:11









mihai

23.4k73968




23.4k73968










asked Nov 20 '18 at 19:57









George Zhang

365




365












  • I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
    – George Zhang
    Nov 20 '18 at 20:00










  • what parameters did you use for ssh-keygen ?
    – mihai
    Nov 21 '18 at 8:16










  • I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
    – George Zhang
    Nov 22 '18 at 18:47










  • the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
    – mihai
    Nov 22 '18 at 19:26


















  • I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
    – George Zhang
    Nov 20 '18 at 20:00










  • what parameters did you use for ssh-keygen ?
    – mihai
    Nov 21 '18 at 8:16










  • I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
    – George Zhang
    Nov 22 '18 at 18:47










  • the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
    – mihai
    Nov 22 '18 at 19:26
















I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
– George Zhang
Nov 20 '18 at 20:00




I found this issue in github.com/mscdex/ssh2-streams/issues/100 . Anyone have any idea to fall back the ssh-keygen to old version?
– George Zhang
Nov 20 '18 at 20:00












what parameters did you use for ssh-keygen ?
– mihai
Nov 21 '18 at 8:16




what parameters did you use for ssh-keygen ?
– mihai
Nov 21 '18 at 8:16












I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
– George Zhang
Nov 22 '18 at 18:47




I tried "-o " and almost all combinations already. But it still use OPENSSH in the header. For now, I just copied the old private key for the SSH2.
– George Zhang
Nov 22 '18 at 18:47












the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
– mihai
Nov 22 '18 at 19:26




the thing is, you shouldn't be using -o. See this article tutorialinux.com/convert-ssh2-openssh
– mihai
Nov 22 '18 at 19:26












1 Answer
1






active

oldest

votes


















0














Had the same problem, found the solution here.



basically use the PEM option when you create your key:



ssh-keygen -m PEM -t rsa 





share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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%2fstackoverflow.com%2fquestions%2f53400628%2fcannot-parse-privatekey-unsupported-key-format%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









    0














    Had the same problem, found the solution here.



    basically use the PEM option when you create your key:



    ssh-keygen -m PEM -t rsa 





    share|improve this answer


























      0














      Had the same problem, found the solution here.



      basically use the PEM option when you create your key:



      ssh-keygen -m PEM -t rsa 





      share|improve this answer
























        0












        0








        0






        Had the same problem, found the solution here.



        basically use the PEM option when you create your key:



        ssh-keygen -m PEM -t rsa 





        share|improve this answer












        Had the same problem, found the solution here.



        basically use the PEM option when you create your key:



        ssh-keygen -m PEM -t rsa 






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 9 hours ago









        Dozon Higgs

        593




        593






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f53400628%2fcannot-parse-privatekey-unsupported-key-format%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

            Costa Masnaga

            Fotorealismo

            Sidney Franklin