Why is the maximum length of OpenWrt’s root password 8 characters? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Hosting providers limiting the password length or allowed charactersCan only see 2GB of 4GB on 2.6.26-1-xen-amd64 debian 5, Dell PowerEdge 860How I can identify which process is making UDP traffic on Linux?pam_cracklib on Linux: how to disable creditsHow to enforce password complexity in Redhat?Strange OpenVPN behavior - disconnects after one minuteAllow linux root user mysql root access without passwordTurn off password expiration after user changes password (Linux)Changing the root passworddisable maximum password length on Windows Server

Why did the IBM 650 use bi-quinary?

Should I use a zero-interest credit card for a large one-time purchase?

How discoverable are IPv6 addresses and AAAA names by potential attackers?

At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan?

What does the word "veer" mean here?

illegal generic type for instanceof when using local classes

Using et al. for a last / senior author rather than for a first author

Identifying polygons that intersect with another layer using QGIS?

Seeking colloquialism for “just because”

Do I really need recursive chmod to restrict access to a folder?

What's the purpose of writing one's academic biography in the third person?

Echoing a tail command produces unexpected output?

Sci-Fi book where patients in a coma ward all live in a subconscious world linked together

How to answer "Have you ever been terminated?"

Bete Noir -- no dairy

How to deal with a team lead who never gives me credit?

3 doors, three guards, one stone

Why do we bend a book to keep it straight?

How can I (re)show post-installation notes?

What LEGO pieces have "real-world" functionality?

What would be the ideal power source for a cybernetic eye?

Extract all GPU name, model and GPU ram

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

What is the role of the transistor and diode in a soft start circuit?



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



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Hosting providers limiting the password length or allowed charactersCan only see 2GB of 4GB on 2.6.26-1-xen-amd64 debian 5, Dell PowerEdge 860How I can identify which process is making UDP traffic on Linux?pam_cracklib on Linux: how to disable creditsHow to enforce password complexity in Redhat?Strange OpenVPN behavior - disconnects after one minuteAllow linux root user mysql root access without passwordTurn off password expiration after user changes password (Linux)Changing the root passworddisable maximum password length on Windows Server



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








27















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






























    27















    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


























      27












      27








      27


      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 Apr 10 at 2:33









      Peter Mortensen

      2,15142124




      2,15142124










      asked Apr 9 at 12:19









      Alan42Alan42

      451412




      451412




















          2 Answers
          2






          active

          oldest

          votes


















          35














          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.



          (Side note: the digits-only salts in the md5crypt and sha512crypt examples above are just side effects of how hashcat creates example hashes; real, healthy salts are usually drawn from a much larger keyspace).



          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
































            20














            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




















            • 16





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

              – HBruijn
              Apr 9 at 13:19






            • 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
              Apr 9 at 14:49






            • 9





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

              – PhilippNagel
              Apr 9 at 17:22






            • 8





              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
              Apr 9 at 17:51






            • 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
              Apr 9 at 20:38











            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









            35














            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.



            (Side note: the digits-only salts in the md5crypt and sha512crypt examples above are just side effects of how hashcat creates example hashes; real, healthy salts are usually drawn from a much larger keyspace).



            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





























              35














              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.



              (Side note: the digits-only salts in the md5crypt and sha512crypt examples above are just side effects of how hashcat creates example hashes; real, healthy salts are usually drawn from a much larger keyspace).



              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



























                35












                35








                35







                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.



                (Side note: the digits-only salts in the md5crypt and sha512crypt examples above are just side effects of how hashcat creates example hashes; real, healthy salts are usually drawn from a much larger keyspace).



                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.



                (Side note: the digits-only salts in the md5crypt and sha512crypt examples above are just side effects of how hashcat creates example hashes; real, healthy salts are usually drawn from a much larger keyspace).



                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 Apr 11 at 18:31

























                answered Apr 9 at 17:39









                Royce WilliamsRoyce Williams

                1,302815




                1,302815























                    20














                    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




















                    • 16





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

                      – HBruijn
                      Apr 9 at 13:19






                    • 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
                      Apr 9 at 14:49






                    • 9





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

                      – PhilippNagel
                      Apr 9 at 17:22






                    • 8





                      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
                      Apr 9 at 17:51






                    • 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
                      Apr 9 at 20:38















                    20














                    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




















                    • 16





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

                      – HBruijn
                      Apr 9 at 13:19






                    • 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
                      Apr 9 at 14:49






                    • 9





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

                      – PhilippNagel
                      Apr 9 at 17:22






                    • 8





                      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
                      Apr 9 at 17:51






                    • 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
                      Apr 9 at 20:38













                    20












                    20








                    20







                    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 Apr 10 at 4:11









                    muru

                    498521




                    498521










                    answered Apr 9 at 13:14









                    Alan42Alan42

                    451412




                    451412







                    • 16





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

                      – HBruijn
                      Apr 9 at 13:19






                    • 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
                      Apr 9 at 14:49






                    • 9





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

                      – PhilippNagel
                      Apr 9 at 17:22






                    • 8





                      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
                      Apr 9 at 17:51






                    • 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
                      Apr 9 at 20:38












                    • 16





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

                      – HBruijn
                      Apr 9 at 13:19






                    • 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
                      Apr 9 at 14:49






                    • 9





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

                      – PhilippNagel
                      Apr 9 at 17:22






                    • 8





                      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
                      Apr 9 at 17:51






                    • 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
                      Apr 9 at 20:38







                    16




                    16





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

                    – HBruijn
                    Apr 9 at 13:19





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

                    – HBruijn
                    Apr 9 at 13:19




                    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
                    Apr 9 at 14:49





                    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
                    Apr 9 at 14:49




                    9




                    9





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

                    – PhilippNagel
                    Apr 9 at 17:22





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

                    – PhilippNagel
                    Apr 9 at 17:22




                    8




                    8





                    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
                    Apr 9 at 17:51





                    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
                    Apr 9 at 17:51




                    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
                    Apr 9 at 20:38





                    @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
                    Apr 9 at 20:38

















                    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

                    រឿង រ៉ូមេអូ និង ហ្ស៊ុយលីយេ សង្ខេបរឿង តួអង្គ បញ្ជីណែនាំ

                    QGIS export composer to PDF scale the map [closed] Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Print Composer QGIS 2.6, how to export image?QGIS 2.8.1 print composer won't export all OpenCycleMap base layer tilesSave Print/Map QGIS composer view as PNG/PDF using Python (without changing anything in visible layout)?Export QGIS Print Composer PDF with searchable text labelsQGIS Print Composer does not change from landscape to portrait orientation?How can I avoid map size and scale changes in print composer?Fuzzy PDF export in QGIS running on macSierra OSExport the legend into its 100% size using Print ComposerScale-dependent rendering in QGIS PDF output

                    PDF-ში გადმოწერა სანავიგაციო მენიუproject page