Why is the maximum length of OpenWrt’s root password 8 characters?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







22















When I try to set root's password:



root@OpenWrt:~# passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.


It seems the maximum length is 8. If I try to set a password longer than 8, only the first 8 characters are valid. How can I set a longer password for root?



My OpenWrt version:



Linux OpenWrt 4.14.108 #0 SMP Wed Mar 27 21:59:03 2019 x86_64 GNU/Linux









share|improve this question































    22















    When I try to set root's password:



    root@OpenWrt:~# passwd
    Changing password for root
    Enter the new password (minimum of 5, maximum of 8 characters)
    Please use a combination of upper and lower case letters and numbers.


    It seems the maximum length is 8. If I try to set a password longer than 8, only the first 8 characters are valid. How can I set a longer password for root?



    My OpenWrt version:



    Linux OpenWrt 4.14.108 #0 SMP Wed Mar 27 21:59:03 2019 x86_64 GNU/Linux









    share|improve this question



























      22












      22








      22


      3






      When I try to set root's password:



      root@OpenWrt:~# passwd
      Changing password for root
      Enter the new password (minimum of 5, maximum of 8 characters)
      Please use a combination of upper and lower case letters and numbers.


      It seems the maximum length is 8. If I try to set a password longer than 8, only the first 8 characters are valid. How can I set a longer password for root?



      My OpenWrt version:



      Linux OpenWrt 4.14.108 #0 SMP Wed Mar 27 21:59:03 2019 x86_64 GNU/Linux









      share|improve this question
















      When I try to set root's password:



      root@OpenWrt:~# passwd
      Changing password for root
      Enter the new password (minimum of 5, maximum of 8 characters)
      Please use a combination of upper and lower case letters and numbers.


      It seems the maximum length is 8. If I try to set a password longer than 8, only the first 8 characters are valid. How can I set a longer password for root?



      My OpenWrt version:



      Linux OpenWrt 4.14.108 #0 SMP Wed Mar 27 21:59:03 2019 x86_64 GNU/Linux






      linux password root openwrt passwd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday









      Peter Mortensen

      2,14242124




      2,14242124










      asked yesterday









      Alan42Alan42

      386212




      386212






















          2 Answers
          2






          active

          oldest

          votes


















          30














          This is because DES-based crypt (AKA 'descrypt') truncates passwords at 8 bytes, and only checks the first 8 for the purpose of password verification.



          That's the answer to your direct question, but here's some general advice implied by your context:




          • Fortunately, from my reading, MD5 in /etc/login.defs is actually md5crypt ($1$), which, while a little outdated and declared deprecated by its author, is still far superior to DES-based crypt (and definitely much better than a raw, unsalted hash like plain MD5! Most unsalted hashes can be cracked on commodity GPUs at rates of billions per second)


          • It looks like SHA256 (actually sha256crypt) and SHA512 (actually sha512crypt) are also there. I would pick one of those instead.


          • If you set your password to password or something under each scheme, you can visually verify whether or not my conclusion that they're the -crypt variants is correct (examples here are taken from the hashcat example hashes, all 'hashcat', some wrapped for readability):



          Not recommended - unsalted or legacy hash types, much too "fast" (cracking rates) for password storage:



          MD5         - 8743b52063cd84097a65d1633f5c74f5
          SHA256 - 127e6fbfe24a750e72930c220a8e138275656b8e5d8f48a98c3c92df2caba935
          SHA512 - 82a9dda829eb7f8ffe9fbe49e45d47d2dad9664fbb7adf72492e3c81ebd3e2
          9134d9bc12212bf83c6840f10e8246b9db54a4859b7ccd0123d86e5872c1e5082f
          descrypt - 48c/R8JAv757A


          OK - much better than unsalted, no truncation, but no longer sufficiently resistant to brute force on modern hardware:



          md5crypt    - $1$28772684$iEwNOgGugqO9.bIz5sk8k/


          Better - relatively modern hashes with large salts and work factors:



          sha256crypt - $5$rounds=5000$GX7BopJZJxPc/KEK$le16UF8I2Anb.rOrn22AUPWvzUETDGefUmAV8AZkGcD
          sha512crypt - $6$52450745$k5ka2p8bFuSmoVT1tzOyyuaREkkKBcCNqoDKzYiJL9RaE8yMnPgh2XzzF0NDrUhgrcLwg78xs1w5pJiypEdFX/


          Of these, only descrypt truncates at 8. The last two are your best bet.



          Note also that I'm only listing the hash types that are supported by /etc/login.defs on this platform. For general use, even sha256crypt and sha512crypt have been superseded - first by bcrypt, and then later by truly parallel-attack-resistant hashes like scrypt and the Argon2 family. (Note, however, that for interactive logins that should complete in under one second, bcrypt is actually more resistant to attack than the latter)






          share|improve this answer

































            17














            I modified this in /etc/login.defs:



            PASS_MAX_LEN            8


            problem fixed.





            Important additions:



            After I changed the above parameters, although I can set a password larger than 8 digits, it is still invalid because the real password is only the first eight digits. I don't know if this is my problem.



            My final solution is to set



            # ENCRYPT_METHOD DES


            to



            ENCRYPT_METHOD MD5


            in /etc/login.defs.



            Now, I can finally set a root password that is really larger than eight.






            share|improve this answer





















            • 15





              Good fix, but bad original choice for a system default though...

              – HBruijn
              yesterday






            • 8





              I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

              – marcelm
              yesterday






            • 9





              You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

              – PhilippNagel
              yesterday






            • 7





              really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

              – SnakeDoc
              yesterday






            • 4





              @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

              – marcelm
              yesterday












            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            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%2fserverfault.com%2fquestions%2f962214%2fwhy-is-the-maximum-length-of-openwrt-s-root-password-8-characters%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









            30














            This is because DES-based crypt (AKA 'descrypt') truncates passwords at 8 bytes, and only checks the first 8 for the purpose of password verification.



            That's the answer to your direct question, but here's some general advice implied by your context:




            • Fortunately, from my reading, MD5 in /etc/login.defs is actually md5crypt ($1$), which, while a little outdated and declared deprecated by its author, is still far superior to DES-based crypt (and definitely much better than a raw, unsalted hash like plain MD5! Most unsalted hashes can be cracked on commodity GPUs at rates of billions per second)


            • It looks like SHA256 (actually sha256crypt) and SHA512 (actually sha512crypt) are also there. I would pick one of those instead.


            • If you set your password to password or something under each scheme, you can visually verify whether or not my conclusion that they're the -crypt variants is correct (examples here are taken from the hashcat example hashes, all 'hashcat', some wrapped for readability):



            Not recommended - unsalted or legacy hash types, much too "fast" (cracking rates) for password storage:



            MD5         - 8743b52063cd84097a65d1633f5c74f5
            SHA256 - 127e6fbfe24a750e72930c220a8e138275656b8e5d8f48a98c3c92df2caba935
            SHA512 - 82a9dda829eb7f8ffe9fbe49e45d47d2dad9664fbb7adf72492e3c81ebd3e2
            9134d9bc12212bf83c6840f10e8246b9db54a4859b7ccd0123d86e5872c1e5082f
            descrypt - 48c/R8JAv757A


            OK - much better than unsalted, no truncation, but no longer sufficiently resistant to brute force on modern hardware:



            md5crypt    - $1$28772684$iEwNOgGugqO9.bIz5sk8k/


            Better - relatively modern hashes with large salts and work factors:



            sha256crypt - $5$rounds=5000$GX7BopJZJxPc/KEK$le16UF8I2Anb.rOrn22AUPWvzUETDGefUmAV8AZkGcD
            sha512crypt - $6$52450745$k5ka2p8bFuSmoVT1tzOyyuaREkkKBcCNqoDKzYiJL9RaE8yMnPgh2XzzF0NDrUhgrcLwg78xs1w5pJiypEdFX/


            Of these, only descrypt truncates at 8. The last two are your best bet.



            Note also that I'm only listing the hash types that are supported by /etc/login.defs on this platform. For general use, even sha256crypt and sha512crypt have been superseded - first by bcrypt, and then later by truly parallel-attack-resistant hashes like scrypt and the Argon2 family. (Note, however, that for interactive logins that should complete in under one second, bcrypt is actually more resistant to attack than the latter)






            share|improve this answer






























              30














              This is because DES-based crypt (AKA 'descrypt') truncates passwords at 8 bytes, and only checks the first 8 for the purpose of password verification.



              That's the answer to your direct question, but here's some general advice implied by your context:




              • Fortunately, from my reading, MD5 in /etc/login.defs is actually md5crypt ($1$), which, while a little outdated and declared deprecated by its author, is still far superior to DES-based crypt (and definitely much better than a raw, unsalted hash like plain MD5! Most unsalted hashes can be cracked on commodity GPUs at rates of billions per second)


              • It looks like SHA256 (actually sha256crypt) and SHA512 (actually sha512crypt) are also there. I would pick one of those instead.


              • If you set your password to password or something under each scheme, you can visually verify whether or not my conclusion that they're the -crypt variants is correct (examples here are taken from the hashcat example hashes, all 'hashcat', some wrapped for readability):



              Not recommended - unsalted or legacy hash types, much too "fast" (cracking rates) for password storage:



              MD5         - 8743b52063cd84097a65d1633f5c74f5
              SHA256 - 127e6fbfe24a750e72930c220a8e138275656b8e5d8f48a98c3c92df2caba935
              SHA512 - 82a9dda829eb7f8ffe9fbe49e45d47d2dad9664fbb7adf72492e3c81ebd3e2
              9134d9bc12212bf83c6840f10e8246b9db54a4859b7ccd0123d86e5872c1e5082f
              descrypt - 48c/R8JAv757A


              OK - much better than unsalted, no truncation, but no longer sufficiently resistant to brute force on modern hardware:



              md5crypt    - $1$28772684$iEwNOgGugqO9.bIz5sk8k/


              Better - relatively modern hashes with large salts and work factors:



              sha256crypt - $5$rounds=5000$GX7BopJZJxPc/KEK$le16UF8I2Anb.rOrn22AUPWvzUETDGefUmAV8AZkGcD
              sha512crypt - $6$52450745$k5ka2p8bFuSmoVT1tzOyyuaREkkKBcCNqoDKzYiJL9RaE8yMnPgh2XzzF0NDrUhgrcLwg78xs1w5pJiypEdFX/


              Of these, only descrypt truncates at 8. The last two are your best bet.



              Note also that I'm only listing the hash types that are supported by /etc/login.defs on this platform. For general use, even sha256crypt and sha512crypt have been superseded - first by bcrypt, and then later by truly parallel-attack-resistant hashes like scrypt and the Argon2 family. (Note, however, that for interactive logins that should complete in under one second, bcrypt is actually more resistant to attack than the latter)






              share|improve this answer




























                30












                30








                30







                This is because DES-based crypt (AKA 'descrypt') truncates passwords at 8 bytes, and only checks the first 8 for the purpose of password verification.



                That's the answer to your direct question, but here's some general advice implied by your context:




                • Fortunately, from my reading, MD5 in /etc/login.defs is actually md5crypt ($1$), which, while a little outdated and declared deprecated by its author, is still far superior to DES-based crypt (and definitely much better than a raw, unsalted hash like plain MD5! Most unsalted hashes can be cracked on commodity GPUs at rates of billions per second)


                • It looks like SHA256 (actually sha256crypt) and SHA512 (actually sha512crypt) are also there. I would pick one of those instead.


                • If you set your password to password or something under each scheme, you can visually verify whether or not my conclusion that they're the -crypt variants is correct (examples here are taken from the hashcat example hashes, all 'hashcat', some wrapped for readability):



                Not recommended - unsalted or legacy hash types, much too "fast" (cracking rates) for password storage:



                MD5         - 8743b52063cd84097a65d1633f5c74f5
                SHA256 - 127e6fbfe24a750e72930c220a8e138275656b8e5d8f48a98c3c92df2caba935
                SHA512 - 82a9dda829eb7f8ffe9fbe49e45d47d2dad9664fbb7adf72492e3c81ebd3e2
                9134d9bc12212bf83c6840f10e8246b9db54a4859b7ccd0123d86e5872c1e5082f
                descrypt - 48c/R8JAv757A


                OK - much better than unsalted, no truncation, but no longer sufficiently resistant to brute force on modern hardware:



                md5crypt    - $1$28772684$iEwNOgGugqO9.bIz5sk8k/


                Better - relatively modern hashes with large salts and work factors:



                sha256crypt - $5$rounds=5000$GX7BopJZJxPc/KEK$le16UF8I2Anb.rOrn22AUPWvzUETDGefUmAV8AZkGcD
                sha512crypt - $6$52450745$k5ka2p8bFuSmoVT1tzOyyuaREkkKBcCNqoDKzYiJL9RaE8yMnPgh2XzzF0NDrUhgrcLwg78xs1w5pJiypEdFX/


                Of these, only descrypt truncates at 8. The last two are your best bet.



                Note also that I'm only listing the hash types that are supported by /etc/login.defs on this platform. For general use, even sha256crypt and sha512crypt have been superseded - first by bcrypt, and then later by truly parallel-attack-resistant hashes like scrypt and the Argon2 family. (Note, however, that for interactive logins that should complete in under one second, bcrypt is actually more resistant to attack than the latter)






                share|improve this answer















                This is because DES-based crypt (AKA 'descrypt') truncates passwords at 8 bytes, and only checks the first 8 for the purpose of password verification.



                That's the answer to your direct question, but here's some general advice implied by your context:




                • Fortunately, from my reading, MD5 in /etc/login.defs is actually md5crypt ($1$), which, while a little outdated and declared deprecated by its author, is still far superior to DES-based crypt (and definitely much better than a raw, unsalted hash like plain MD5! Most unsalted hashes can be cracked on commodity GPUs at rates of billions per second)


                • It looks like SHA256 (actually sha256crypt) and SHA512 (actually sha512crypt) are also there. I would pick one of those instead.


                • If you set your password to password or something under each scheme, you can visually verify whether or not my conclusion that they're the -crypt variants is correct (examples here are taken from the hashcat example hashes, all 'hashcat', some wrapped for readability):



                Not recommended - unsalted or legacy hash types, much too "fast" (cracking rates) for password storage:



                MD5         - 8743b52063cd84097a65d1633f5c74f5
                SHA256 - 127e6fbfe24a750e72930c220a8e138275656b8e5d8f48a98c3c92df2caba935
                SHA512 - 82a9dda829eb7f8ffe9fbe49e45d47d2dad9664fbb7adf72492e3c81ebd3e2
                9134d9bc12212bf83c6840f10e8246b9db54a4859b7ccd0123d86e5872c1e5082f
                descrypt - 48c/R8JAv757A


                OK - much better than unsalted, no truncation, but no longer sufficiently resistant to brute force on modern hardware:



                md5crypt    - $1$28772684$iEwNOgGugqO9.bIz5sk8k/


                Better - relatively modern hashes with large salts and work factors:



                sha256crypt - $5$rounds=5000$GX7BopJZJxPc/KEK$le16UF8I2Anb.rOrn22AUPWvzUETDGefUmAV8AZkGcD
                sha512crypt - $6$52450745$k5ka2p8bFuSmoVT1tzOyyuaREkkKBcCNqoDKzYiJL9RaE8yMnPgh2XzzF0NDrUhgrcLwg78xs1w5pJiypEdFX/


                Of these, only descrypt truncates at 8. The last two are your best bet.



                Note also that I'm only listing the hash types that are supported by /etc/login.defs on this platform. For general use, even sha256crypt and sha512crypt have been superseded - first by bcrypt, and then later by truly parallel-attack-resistant hashes like scrypt and the Argon2 family. (Note, however, that for interactive logins that should complete in under one second, bcrypt is actually more resistant to attack than the latter)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 15 hours ago

























                answered yesterday









                Royce WilliamsRoyce Williams

                1,242815




                1,242815

























                    17














                    I modified this in /etc/login.defs:



                    PASS_MAX_LEN            8


                    problem fixed.





                    Important additions:



                    After I changed the above parameters, although I can set a password larger than 8 digits, it is still invalid because the real password is only the first eight digits. I don't know if this is my problem.



                    My final solution is to set



                    # ENCRYPT_METHOD DES


                    to



                    ENCRYPT_METHOD MD5


                    in /etc/login.defs.



                    Now, I can finally set a root password that is really larger than eight.






                    share|improve this answer





















                    • 15





                      Good fix, but bad original choice for a system default though...

                      – HBruijn
                      yesterday






                    • 8





                      I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                      – marcelm
                      yesterday






                    • 9





                      You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                      – PhilippNagel
                      yesterday






                    • 7





                      really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                      – SnakeDoc
                      yesterday






                    • 4





                      @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                      – marcelm
                      yesterday
















                    17














                    I modified this in /etc/login.defs:



                    PASS_MAX_LEN            8


                    problem fixed.





                    Important additions:



                    After I changed the above parameters, although I can set a password larger than 8 digits, it is still invalid because the real password is only the first eight digits. I don't know if this is my problem.



                    My final solution is to set



                    # ENCRYPT_METHOD DES


                    to



                    ENCRYPT_METHOD MD5


                    in /etc/login.defs.



                    Now, I can finally set a root password that is really larger than eight.






                    share|improve this answer





















                    • 15





                      Good fix, but bad original choice for a system default though...

                      – HBruijn
                      yesterday






                    • 8





                      I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                      – marcelm
                      yesterday






                    • 9





                      You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                      – PhilippNagel
                      yesterday






                    • 7





                      really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                      – SnakeDoc
                      yesterday






                    • 4





                      @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                      – marcelm
                      yesterday














                    17












                    17








                    17







                    I modified this in /etc/login.defs:



                    PASS_MAX_LEN            8


                    problem fixed.





                    Important additions:



                    After I changed the above parameters, although I can set a password larger than 8 digits, it is still invalid because the real password is only the first eight digits. I don't know if this is my problem.



                    My final solution is to set



                    # ENCRYPT_METHOD DES


                    to



                    ENCRYPT_METHOD MD5


                    in /etc/login.defs.



                    Now, I can finally set a root password that is really larger than eight.






                    share|improve this answer















                    I modified this in /etc/login.defs:



                    PASS_MAX_LEN            8


                    problem fixed.





                    Important additions:



                    After I changed the above parameters, although I can set a password larger than 8 digits, it is still invalid because the real password is only the first eight digits. I don't know if this is my problem.



                    My final solution is to set



                    # ENCRYPT_METHOD DES


                    to



                    ENCRYPT_METHOD MD5


                    in /etc/login.defs.



                    Now, I can finally set a root password that is really larger than eight.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited yesterday









                    muru

                    498521




                    498521










                    answered yesterday









                    Alan42Alan42

                    386212




                    386212








                    • 15





                      Good fix, but bad original choice for a system default though...

                      – HBruijn
                      yesterday






                    • 8





                      I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                      – marcelm
                      yesterday






                    • 9





                      You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                      – PhilippNagel
                      yesterday






                    • 7





                      really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                      – SnakeDoc
                      yesterday






                    • 4





                      @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                      – marcelm
                      yesterday














                    • 15





                      Good fix, but bad original choice for a system default though...

                      – HBruijn
                      yesterday






                    • 8





                      I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                      – marcelm
                      yesterday






                    • 9





                      You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                      – PhilippNagel
                      yesterday






                    • 7





                      really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                      – SnakeDoc
                      yesterday






                    • 4





                      @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                      – marcelm
                      yesterday








                    15




                    15





                    Good fix, but bad original choice for a system default though...

                    – HBruijn
                    yesterday





                    Good fix, but bad original choice for a system default though...

                    – HBruijn
                    yesterday




                    8




                    8





                    I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                    – marcelm
                    yesterday





                    I assume you changed your password to something longer than 8 characters now. Can you try if logging in with just the first 8 characters of your longer password works? Because it just might...

                    – marcelm
                    yesterday




                    9




                    9





                    You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                    – PhilippNagel
                    yesterday





                    You might consider changing that to SHA256 or SHA512 or they are supported - MD5 is considered broken these days.

                    – PhilippNagel
                    yesterday




                    7




                    7





                    really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                    – SnakeDoc
                    yesterday





                    really sha256 and sha512 by themselves aren't much better than md5. you need a salt, and use the crypt versions of these algorithms.

                    – SnakeDoc
                    yesterday




                    4




                    4





                    @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                    – marcelm
                    yesterday





                    @PhilippNagel With a high-entropy password, it's not too bad. While MD5 should certainly be considered broken, the currently known weaknesses don't affect it for password hashing. What is a problem for password hashing is the speed; non-iterated MD5 is so fast that brute-forcing is very feasible for many passwords.

                    – marcelm
                    yesterday


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • 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%2fserverfault.com%2fquestions%2f962214%2fwhy-is-the-maximum-length-of-openwrt-s-root-password-8-characters%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

                    What other Star Trek series did the main TNG cast show up in?

                    Berlina muro

                    Berlina aerponto