{"id":69,"date":"2008-03-27T02:32:01","date_gmt":"2008-03-26T18:32:01","guid":{"rendered":"http:\/\/www.sysadmindayph.com\/blog\/sshd-kbdint-reuse-of-old-passwords-not-allowed-the-new-password-is-in-the-history-list\/"},"modified":"2008-03-27T02:32:01","modified_gmt":"2008-03-26T18:32:01","slug":"sshd-kbdint-reuse-of-old-passwords-not-allowed-the-new-password-is-in-the-history-list","status":"publish","type":"post","link":"http:\/\/www.sysadmindayph.com\/blog\/sshd-kbdint-reuse-of-old-passwords-not-allowed-the-new-password-is-in-the-history-list\/","title":{"rendered":"sshd-kbdint: Reuse of old passwords not allowed, the new password is in the history list"},"content":{"rendered":"<p>Got a request to reset a password of one of the development server&#8217;s account today. Apparently, one of the batch operators, mistyped the password one to many&#8230; It was locked.<\/p>\n<p>It was an LDAP environment and the SOP is to change the password to a pre-defined default password and then the user will be the one he wants (Anyway, the user has no choice, once he puts the\u00a0 initial password he will be prompted to change it)<\/p>\n<p>The problem is, the server wont allow him to use his old password. He wants to use it again since, he&#8217;s not the only one who uses that (group) account and changing it to his own, well, he have to tell it to everyone else who&#8217;s using the account.. and from what I&#8217;ve heard they are more than a handful.<\/p>\n<p>Anyway, to help him, I checked the \/etc\/default\/passwd and took a peek at HISTORY&#8217;s value. The number here shows how many password the system will remembers (root not included of course). It was set to 10.<\/p>\n<p>Set it temporary to &#8216;0&#8217; and changed the password. After confirming that all is good, changed the HISTORY parameters of \/etc\/default\/passwd back to &#8217;10&#8217; , which is apparently our SOP on password history.<\/p>\n<p>(Machine was a solaris sparc with Solaris 8.10)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Got a request to reset a password of one of the development server&#8217;s account today. Apparently, one of the batch operators, mistyped the password one to many&#8230; It was locked. It was an LDAP environment &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-69","post","type-post","status-publish","format-standard","hentry","category-solaris"],"_links":{"self":[{"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/69","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/comments?post=69"}],"version-history":[{"count":0,"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/69\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/media?parent=69"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/categories?post=69"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/tags?post=69"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}