Incorrect password for Linux user even after changing it





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







1















I am unable to log into a regular user account using a password, so I first change the password to something I know...
As root,



passwd  theUser


put in the password: thepassword



it states it updates successfully




passwd: all authenication tokens updated successfully




I then can



su - theUser


and Im now this user..I try



su - theUser


it asks me for the password,I put in the one I just assigned to it and it fails with



su: incorrect password


I even try to ssh into the box with that user and the password still fails.










share|improve this question















migrated from stackoverflow.com Mar 4 '12 at 19:59


This question came from our site for professional and enthusiast programmers.



















  • Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

    – Keith Thompson
    Mar 4 '12 at 19:59











  • what means "login fails"? Please be verbose here...

    – Jörg Beyer
    Mar 4 '12 at 20:03











  • There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

    – BillyCups
    Mar 4 '12 at 20:05













  • "su: incorrect password" is suspicious, since su is not part of the normal login.

    – Jörg Beyer
    Mar 4 '12 at 20:15











  • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:18


















1















I am unable to log into a regular user account using a password, so I first change the password to something I know...
As root,



passwd  theUser


put in the password: thepassword



it states it updates successfully




passwd: all authenication tokens updated successfully




I then can



su - theUser


and Im now this user..I try



su - theUser


it asks me for the password,I put in the one I just assigned to it and it fails with



su: incorrect password


I even try to ssh into the box with that user and the password still fails.










share|improve this question















migrated from stackoverflow.com Mar 4 '12 at 19:59


This question came from our site for professional and enthusiast programmers.



















  • Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

    – Keith Thompson
    Mar 4 '12 at 19:59











  • what means "login fails"? Please be verbose here...

    – Jörg Beyer
    Mar 4 '12 at 20:03











  • There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

    – BillyCups
    Mar 4 '12 at 20:05













  • "su: incorrect password" is suspicious, since su is not part of the normal login.

    – Jörg Beyer
    Mar 4 '12 at 20:15











  • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:18














1












1








1








I am unable to log into a regular user account using a password, so I first change the password to something I know...
As root,



passwd  theUser


put in the password: thepassword



it states it updates successfully




passwd: all authenication tokens updated successfully




I then can



su - theUser


and Im now this user..I try



su - theUser


it asks me for the password,I put in the one I just assigned to it and it fails with



su: incorrect password


I even try to ssh into the box with that user and the password still fails.










share|improve this question
















I am unable to log into a regular user account using a password, so I first change the password to something I know...
As root,



passwd  theUser


put in the password: thepassword



it states it updates successfully




passwd: all authenication tokens updated successfully




I then can



su - theUser


and Im now this user..I try



su - theUser


it asks me for the password,I put in the one I just assigned to it and it fails with



su: incorrect password


I even try to ssh into the box with that user and the password still fails.







linux passwords user






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 24 '18 at 14:50









Chris Stryczynski

1176




1176










asked Mar 4 '12 at 19:55









BillyCupsBillyCups

8114




8114




migrated from stackoverflow.com Mar 4 '12 at 19:59


This question came from our site for professional and enthusiast programmers.









migrated from stackoverflow.com Mar 4 '12 at 19:59


This question came from our site for professional and enthusiast programmers.















  • Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

    – Keith Thompson
    Mar 4 '12 at 19:59











  • what means "login fails"? Please be verbose here...

    – Jörg Beyer
    Mar 4 '12 at 20:03











  • There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

    – BillyCups
    Mar 4 '12 at 20:05













  • "su: incorrect password" is suspicious, since su is not part of the normal login.

    – Jörg Beyer
    Mar 4 '12 at 20:15











  • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:18



















  • Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

    – Keith Thompson
    Mar 4 '12 at 19:59











  • what means "login fails"? Please be verbose here...

    – Jörg Beyer
    Mar 4 '12 at 20:03











  • There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

    – BillyCups
    Mar 4 '12 at 20:05













  • "su: incorrect password" is suspicious, since su is not part of the normal login.

    – Jörg Beyer
    Mar 4 '12 at 20:15











  • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:18

















Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

– Keith Thompson
Mar 4 '12 at 19:59





Are you sure you're entering the same password each time? Copy-and-paste it, don't retype it.

– Keith Thompson
Mar 4 '12 at 19:59













what means "login fails"? Please be verbose here...

– Jörg Beyer
Mar 4 '12 at 20:03





what means "login fails"? Please be verbose here...

– Jörg Beyer
Mar 4 '12 at 20:03













There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

– BillyCups
Mar 4 '12 at 20:05







There is no /bin/false in the passwd file for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password

– BillyCups
Mar 4 '12 at 20:05















"su: incorrect password" is suspicious, since su is not part of the normal login.

– Jörg Beyer
Mar 4 '12 at 20:15





"su: incorrect password" is suspicious, since su is not part of the normal login.

– Jörg Beyer
Mar 4 '12 at 20:15













something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

– BillyCups
Mar 4 '12 at 20:18





something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

– BillyCups
Mar 4 '12 at 20:18










3 Answers
3






active

oldest

votes


















2














There are several places to check.




  • /etc/passwd - maybe the user has not access to a "valid shell"; if the line corresponding to this user ends with /bin/false, then this user does not have access to the command-line shell


  • /etc/hosts.allow and /etc/hosts.deny - access control


  • /etc/ssh/sshd_config - ssh configuration


  • /etc/security/access.conf - security setting


  • /etc/pam.d/sshd and /etc/pam.d/system-auth-ac - PAM settings



Using ssh -vv for verbose output may help.



And a user reported that reinstalling ssh resolved his issue.






share|improve this answer


























  • There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

    – BillyCups
    Mar 4 '12 at 20:05











  • Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

    – J. Bruni
    Mar 4 '12 at 20:07













  • I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

    – BillyCups
    Mar 4 '12 at 20:09













  • I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

    – J. Bruni
    Mar 4 '12 at 20:14













  • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:19



















0














On centos I had a user account that was 'locked' which I unlocked with the following:



faillock --user usernameGoesHere --reset





share|improve this answer































    -1














    Based on the answer from Chris, I used this command on a similar issue, with success:



    faillog --user usernameGoesHere --reset





    share|improve this answer
























    • This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

      – Vinícius M
      Feb 5 at 15:50











    • I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

      – Jacob Helbo Kristensen
      Feb 6 at 8:00














    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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%2fsuperuser.com%2fquestions%2f396857%2fincorrect-password-for-linux-user-even-after-changing-it%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    There are several places to check.




    • /etc/passwd - maybe the user has not access to a "valid shell"; if the line corresponding to this user ends with /bin/false, then this user does not have access to the command-line shell


    • /etc/hosts.allow and /etc/hosts.deny - access control


    • /etc/ssh/sshd_config - ssh configuration


    • /etc/security/access.conf - security setting


    • /etc/pam.d/sshd and /etc/pam.d/system-auth-ac - PAM settings



    Using ssh -vv for verbose output may help.



    And a user reported that reinstalling ssh resolved his issue.






    share|improve this answer


























    • There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

      – BillyCups
      Mar 4 '12 at 20:05











    • Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

      – J. Bruni
      Mar 4 '12 at 20:07













    • I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

      – BillyCups
      Mar 4 '12 at 20:09













    • I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

      – J. Bruni
      Mar 4 '12 at 20:14













    • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

      – BillyCups
      Mar 4 '12 at 20:19
















    2














    There are several places to check.




    • /etc/passwd - maybe the user has not access to a "valid shell"; if the line corresponding to this user ends with /bin/false, then this user does not have access to the command-line shell


    • /etc/hosts.allow and /etc/hosts.deny - access control


    • /etc/ssh/sshd_config - ssh configuration


    • /etc/security/access.conf - security setting


    • /etc/pam.d/sshd and /etc/pam.d/system-auth-ac - PAM settings



    Using ssh -vv for verbose output may help.



    And a user reported that reinstalling ssh resolved his issue.






    share|improve this answer


























    • There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

      – BillyCups
      Mar 4 '12 at 20:05











    • Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

      – J. Bruni
      Mar 4 '12 at 20:07













    • I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

      – BillyCups
      Mar 4 '12 at 20:09













    • I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

      – J. Bruni
      Mar 4 '12 at 20:14













    • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

      – BillyCups
      Mar 4 '12 at 20:19














    2












    2








    2







    There are several places to check.




    • /etc/passwd - maybe the user has not access to a "valid shell"; if the line corresponding to this user ends with /bin/false, then this user does not have access to the command-line shell


    • /etc/hosts.allow and /etc/hosts.deny - access control


    • /etc/ssh/sshd_config - ssh configuration


    • /etc/security/access.conf - security setting


    • /etc/pam.d/sshd and /etc/pam.d/system-auth-ac - PAM settings



    Using ssh -vv for verbose output may help.



    And a user reported that reinstalling ssh resolved his issue.






    share|improve this answer















    There are several places to check.




    • /etc/passwd - maybe the user has not access to a "valid shell"; if the line corresponding to this user ends with /bin/false, then this user does not have access to the command-line shell


    • /etc/hosts.allow and /etc/hosts.deny - access control


    • /etc/ssh/sshd_config - ssh configuration


    • /etc/security/access.conf - security setting


    • /etc/pam.d/sshd and /etc/pam.d/system-auth-ac - PAM settings



    Using ssh -vv for verbose output may help.



    And a user reported that reinstalling ssh resolved his issue.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 4 '12 at 21:52

























    answered Mar 4 '12 at 19:59









    J. BruniJ. Bruni

    1355




    1355













    • There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

      – BillyCups
      Mar 4 '12 at 20:05











    • Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

      – J. Bruni
      Mar 4 '12 at 20:07













    • I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

      – BillyCups
      Mar 4 '12 at 20:09













    • I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

      – J. Bruni
      Mar 4 '12 at 20:14













    • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

      – BillyCups
      Mar 4 '12 at 20:19



















    • There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

      – BillyCups
      Mar 4 '12 at 20:05











    • Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

      – J. Bruni
      Mar 4 '12 at 20:07













    • I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

      – BillyCups
      Mar 4 '12 at 20:09













    • I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

      – J. Bruni
      Mar 4 '12 at 20:14













    • something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

      – BillyCups
      Mar 4 '12 at 20:19

















    There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

    – BillyCups
    Mar 4 '12 at 20:05





    There is no /bin/false in the passwd for this user. I am cutting and pasting the password. the Logins fails with "su: incorrect password"

    – BillyCups
    Mar 4 '12 at 20:05













    Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

    – J. Bruni
    Mar 4 '12 at 20:07







    Try a simple password, just as a test. Something like 'abc123'. Does it work? Do not copy/paste in this simple test.

    – J. Bruni
    Mar 4 '12 at 20:07















    I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

    – BillyCups
    Mar 4 '12 at 20:09







    I just tried qwer1234 as the password and still no luck :( I mean it supposedly sets the new password but still can't log in with it

    – BillyCups
    Mar 4 '12 at 20:09















    I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

    – J. Bruni
    Mar 4 '12 at 20:14







    I'd check /etc/ssh/sshd_config... related configs: PasswordAuthentication, UsePAM, KerberosAuthentication, AllowUsers...

    – J. Bruni
    Mar 4 '12 at 20:14















    something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:19





    something that is interesting.. If I ssh from another box to this server and put in the correct password.. it instantly returns with "Connection closed by 22.22.22.22"... if I try to ssh in and on purpose put the wrong password, it says "Permission denied, please try again" so it knows the what the right password is ..it just won't let me in..

    – BillyCups
    Mar 4 '12 at 20:19













    0














    On centos I had a user account that was 'locked' which I unlocked with the following:



    faillock --user usernameGoesHere --reset





    share|improve this answer




























      0














      On centos I had a user account that was 'locked' which I unlocked with the following:



      faillock --user usernameGoesHere --reset





      share|improve this answer


























        0












        0








        0







        On centos I had a user account that was 'locked' which I unlocked with the following:



        faillock --user usernameGoesHere --reset





        share|improve this answer













        On centos I had a user account that was 'locked' which I unlocked with the following:



        faillock --user usernameGoesHere --reset






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 24 '18 at 14:24









        Chris StryczynskiChris Stryczynski

        1176




        1176























            -1














            Based on the answer from Chris, I used this command on a similar issue, with success:



            faillog --user usernameGoesHere --reset





            share|improve this answer
























            • This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

              – Vinícius M
              Feb 5 at 15:50











            • I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

              – Jacob Helbo Kristensen
              Feb 6 at 8:00


















            -1














            Based on the answer from Chris, I used this command on a similar issue, with success:



            faillog --user usernameGoesHere --reset





            share|improve this answer
























            • This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

              – Vinícius M
              Feb 5 at 15:50











            • I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

              – Jacob Helbo Kristensen
              Feb 6 at 8:00
















            -1












            -1








            -1







            Based on the answer from Chris, I used this command on a similar issue, with success:



            faillog --user usernameGoesHere --reset





            share|improve this answer













            Based on the answer from Chris, I used this command on a similar issue, with success:



            faillog --user usernameGoesHere --reset






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 5 at 9:54









            Jacob Helbo KristensenJacob Helbo Kristensen

            12




            12













            • This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

              – Vinícius M
              Feb 5 at 15:50











            • I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

              – Jacob Helbo Kristensen
              Feb 6 at 8:00





















            • This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

              – Vinícius M
              Feb 5 at 15:50











            • I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

              – Jacob Helbo Kristensen
              Feb 6 at 8:00



















            This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

            – Vinícius M
            Feb 5 at 15:50





            This is basically a copy of Chris' answer, but with even less explanation about the command. You probably had a good intention, but re-posting it isn't very helpful. If his answer worked for you, you should simply upvote his answer. =)

            – Vinícius M
            Feb 5 at 15:50













            I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

            – Jacob Helbo Kristensen
            Feb 6 at 8:00







            I would very much like to, but I am 14 points from having access to upvoting and 49 points from commenting his post. And yes my intention was good, so if someone could add my 2 cents to Chris' answer I wouldn't mind. I would hate if someone was in my situation, and didn't manage to discover faillog instead of faillock :)

            – Jacob Helbo Kristensen
            Feb 6 at 8:00




















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f396857%2fincorrect-password-for-linux-user-even-after-changing-it%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

            Сан-Квентин

            Алькесар

            Josef Freinademetz