Why is the maximum length of openwrt’s root password 8 characters? The 2019 Stack Overflow Developer Survey Results Are InHosting 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

Is there a name of the flying bionic bird?

Inflated grade on resume at previous job, might former employer tell new employer?

Why isn't airport relocation done gradually?

Monty Hall variation

What is this 4-propeller plane?

Is three citations per paragraph excessive for undergraduate research paper?

How to manage monthly salary

Lethal sonic weapons

What do hard-Brexiteers want with respect to the Irish border?

Why do UK politicians seemingly ignore opinion polls on Brexit?

Which Sci-Fi work first showed weapon of galactic-scale mass destruction?

On the insanity of kings as an argument against Monarchy

I see my dog run

Realistic Alternatives to Dust: What Else Could Feed a Plankton Bloom?

Geography at the pixel level

If a poisoned arrow's piercing damage is reduced to 0, do you still get poisoned?

Does light intensity oscillate really fast since it is a wave?

Why is Grand Jury testimony secret?

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Can't find the latex code for the ⍎ (down tack jot) symbol

Where to refill my bottle in India?

Does it makes sense to buy a new cycle to learn riding?

Could JWST stay at L2 "forever"?

Why is it "Tumoren" and not "Tumore"?



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



The 2019 Stack Overflow Developer Survey Results Are InHosting 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;








14















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 first 8 characters is 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






























    14















    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 first 8 characters is 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


























      14












      14








      14








      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 first 8 characters is 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 first 8 characters is 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 7 hours ago









      Machavity

      577517




      577517










      asked 12 hours ago









      Alan42Alan42

      301110




      301110




















          2 Answers
          2






          active

          oldest

          votes


















          13














          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




















          • 9





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

            – HBruijn
            11 hours ago






          • 6





            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
            9 hours ago






          • 6





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

            – PhilippNagel
            7 hours ago






          • 4





            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
            6 hours ago






          • 3





            @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
            3 hours ago


















          12














          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 no longer supported, 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 finish in under one second, bcrypt is actually more resistant to attack than the latter)






          share|improve this answer

























            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









            13














            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




















            • 9





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

              – HBruijn
              11 hours ago






            • 6





              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
              9 hours ago






            • 6





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

              – PhilippNagel
              7 hours ago






            • 4





              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
              6 hours ago






            • 3





              @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
              3 hours ago















            13














            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




















            • 9





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

              – HBruijn
              11 hours ago






            • 6





              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
              9 hours ago






            • 6





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

              – PhilippNagel
              7 hours ago






            • 4





              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
              6 hours ago






            • 3





              @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
              3 hours ago













            13












            13








            13







            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 7 hours ago

























            answered 11 hours ago









            Alan42Alan42

            301110




            301110







            • 9





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

              – HBruijn
              11 hours ago






            • 6





              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
              9 hours ago






            • 6





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

              – PhilippNagel
              7 hours ago






            • 4





              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
              6 hours ago






            • 3





              @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
              3 hours ago












            • 9





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

              – HBruijn
              11 hours ago






            • 6





              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
              9 hours ago






            • 6





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

              – PhilippNagel
              7 hours ago






            • 4





              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
              6 hours ago






            • 3





              @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
              3 hours ago







            9




            9





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

            – HBruijn
            11 hours ago





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

            – HBruijn
            11 hours ago




            6




            6





            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
            9 hours ago





            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
            9 hours ago




            6




            6





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

            – PhilippNagel
            7 hours ago





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

            – PhilippNagel
            7 hours ago




            4




            4





            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
            6 hours ago





            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
            6 hours ago




            3




            3





            @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
            3 hours ago





            @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
            3 hours ago













            12














            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 no longer supported, 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 finish in under one second, bcrypt is actually more resistant to attack than the latter)






            share|improve this answer





























              12














              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 no longer supported, 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 finish in under one second, bcrypt is actually more resistant to attack than the latter)






              share|improve this answer



























                12












                12








                12







                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 no longer supported, 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 finish 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 no longer supported, 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 finish 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 49 mins ago

























                answered 6 hours ago









                Royce WilliamsRoyce Williams

                1,037614




                1,037614



























                    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

                    How to create a command for the “strange m” symbol in latex? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)How do you make your own symbol when Detexify fails?Writing bold small caps with mathpazo packageplus-minus symbol with parenthesis around the minus signGreek character in Beamer document titleHow to create dashed right arrow over symbol?Currency symbol: Turkish LiraDouble prec as a single symbol?Plus Sign Too Big; How to Call adfbullet?Is there a TeX macro for three-legged pi?How do I get my integral-like symbol to align like the integral?How to selectively substitute a letter with another symbol representing the same letterHow do I generate a less than symbol and vertical bar that are the same height?

                    Българска екзархия Съдържание История | Български екзарси | Вижте също | Външни препратки | Литература | Бележки | НавигацияУстав за управлението на българската екзархия. Цариград, 1870Слово на Ловешкия митрополит Иларион при откриването на Българския народен събор в Цариград на 23. II. 1870 г.Българската правда и гръцката кривда. От С. М. (= Софийски Мелетий). Цариград, 1872Предстоятели на Българската екзархияПодмененият ВеликденИнформационна агенция „Фокус“Димитър Ризов. Българите в техните исторически, етнографически и политически граници (Атлас съдържащ 40 карти). Berlin, Königliche Hoflithographie, Hof-Buch- und -Steindruckerei Wilhelm Greve, 1917Report of the International Commission to Inquire into the Causes and Conduct of the Balkan Wars

                    Чепеларе Съдържание География | История | Население | Спортни и природни забележителности | Културни и исторически обекти | Религии | Обществени институции | Известни личности | Редовни събития | Галерия | Източници | Литература | Външни препратки | Навигация41°43′23.99″ с. ш. 24°41′09.99″ и. д. / 41.723333° с. ш. 24.686111° и. д.*ЧепелареЧепеларски Linux fest 2002Начало на Зимен сезон 2005/06Национални хайдушки празници „Капитан Петко Войвода“Град ЧепелареЧепеларе – народният ски курортbgrod.orgwww.terranatura.hit.bgСправка за населението на гр. Исперих, общ. Исперих, обл. РазградМузей на родопския карстМузей на спорта и скитеЧепеларебългарскибългарскианглийскитукИстория на градаСки писти в ЧепелареВремето в ЧепелареРадио и телевизия в ЧепелареЧепеларе мами с родопски чар и добри пистиЕвтин туризъм и снежни атракции в ЧепелареМестоположениеИнформация и снимки от музея на родопския карст3D панорами от ЧепелареЧепелареррр