lpasswd(1)
π lpasswd β bestie edition π
okay so real talk, this is the General Commands Manual page for lpasswd, and it's basically the "change ur password" girlie for both users and groups. let's get into it π«Ά
β¨ NAME β¨
lpasswd β change group or user password π
πΈ SYNOPSIS πΈ
lpasswd [OPTION]... [name]
π¦ DESCRIPTION π¦
so like, lpasswd changes the password of user or group name. that's the whole vibe. π
if u don't pass the name argument, it just uses the username of the invoking user, easy. but β and this is the plot twist β the name argument gets ignored if lpasswd is run set-uid to a different user. so like, don't try it. π
also, entering an empty password (yes, just pressing Enter like a lil menace) aborts the password setting operation. nothing happens. we go home. π
π OPTIONS π
-F,--plainpassword-fd=fdβ read the password from file descriptor fd, and it's terminated by end of file,'\r', or'\n'. pick ur fave ending ig β¨-f,--password-fd=fdβ read the password hash from file descriptor fd, also terminated by end of file,'\r', or'\n'. yes bestie, hash, not plaintext π-g,--groupβ change the password of group name. by default, the password of user name is what gets changed. so this is ur "actually i meant the group" button π-i,--interactiveβ ask all the questions when connecting to the user database, even if default answers are already set up in the libuser configuration. nosy mode: activated π-P,--plainpassword=passwordβ set the password to password. note that the password can be viewed while runninglpasswdusing tools such asps(1). so likeβ¦ everyone on the box can see it. be so serious rn π-p,--password=encryptedβ set the password to the password represented by the hash encrypted. note that the hash can be viewed while runninglpasswdusing tools such asps(1). still visible!! just less catastrophic π«Ά
β οΈ okay so the-Pand-pthing? that's a real warning, not me being dramatic. anything u pass on the command line can be peeked at viaps(1) whilelpasswdis running. the fd options exist for a reason, bestie. use them. π
π EXIT STATUS π
the exit status is 0 on success, and nonzero on error. classic. no cap. β
π SEE ALSO π
ps(1) β mentioned twice up there because apparently it's the main character of the "oops everyone saw ur password" storyline π
and that's the whole page, bestie!! this one came from the libuser era, dated Jan 12 2005 β so yeah, she's vintage, but the advice is still giving "do not put ur password on the command line" energy fr fr. mwah π β¨
π¦ where this page comes from
- alpine 3.24: libuser-doc 0.64-r2 Β· LGPL-2.0-or-later
- centos-stream 10: libuser 0.64-12.el10 Β· LGPL-2.0-or-later
- centos-stream 9: libuser 0.63-17.el9 Β· LGPLv2+
- centos-stream 9: libuser 0.63-17.el9 Β· LGPLv2+
- debian bookworm: libuser 1:0.64~dfsg-1 Β· LGPL-2.0-or-later
- debian trixie: libuser 1:0.64+git20241106~dfsg-3 Β· LGPL-2.0-or-later
- fedora 43: libuser 0.64-16.fc43 Β· LGPL-2.0-or-later
- fedora 43: libuser 0.64-16.fc43 Β· LGPL-2.0-or-later
- fedora 44: libuser 0.64-17.fc44 Β· LGPL-2.0-or-later
- fedora 44: libuser 0.64-17.fc44 Β· LGPL-2.0-or-later
- opensuse-leap 16.0: libuser 0.64-bp160.1.1 Β· LGPL-2.0-or-later
- opensuse-leap 16.0: libuser 0.64-bp160.1.1 Β· LGPL-2.0-or-later
- opensuse-leap 16.0: libuser 0.64-bp160.1.1 Β· LGPL-2.0-or-later
- opensuse-leap 16.0: libuser 0.64-bp160.1.1 Β· LGPL-2.0-or-later
- ubuntu jammy: libuser 1:0.63~dfsg-4build1 Β· LGPL-2.0-or-later
- ubuntu noble: libuser 1:0.64~dfsg-2build2 Β· LGPL-2.0-or-later
- ubuntu questing: libuser 1:0.64+git20241106~dfsg-3
- ubuntu resolute: libuser 1:0.64+git20241106~dfsg-4build1 Β· LGPL-2.0-or-later
- ubuntu stonking: libuser 1:0.64+git20241106~dfsg-4build1 Β· LGPL-2.0-or-later
- Copyright (C) 2005 Red Hat, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms