The /etc/passwd file stores essential information required during login. In other words, it stores user account information. The /etc/passwd is a plain text file. It contains a list of the system’s accounts, giving for each account some useful information like user ID, group ID, home directory, shell, and more. The /etc/passwd file should have general read permission as many command utilities use it to map user IDs to user names. However, write access to the /etc/passwd must only limit for the superuser/root account.
| Tutorial details | |
|---|---|
| Difficulty level | Easy |
| Root privileges | No |
| Requirements | Linux terminal |
| OS compatibility | BSD • Linux • Unix • WSL |
| Est. reading time | 5 minutes |
- nixCraft is a one-person operation. I create all the content myself, with no help from AI or ML. I keep the content accurate and up-to-date.
- Your privacy is my top priority. I don’t track you, show you ads, or spam you with emails. Just pure content in the true spirit of Linux and FLOSS.
- Fast and clean browsing experience. nixCraft is designed to be fast and easy to use. You won’t have to deal with pop-ups, ads, cookie banners, or other distractions.
- Support independent content creators. nixCraft is a labor of love, and it’s only possible thanks to the support of our readers. If you enjoy the content, please support us on Patreon or share this page on social media or your blog. Every bit helps.
Understanding /etc/passwd file fields
The /etc/passwd contains one entry per line for each user (user account) of the system. All fields are separated by a colon (:) symbol. Total of seven fields as follows. Generally, /etc/passwd file entry looks as follows:

(Fig.01: /etc/passwd file format – click to enlarge)
/etc/passwd file format
From the above image:
- Username: It is used when user logs in. It should be between 1 and 32 characters in length.
- Password: An x character indicates that encrypted password is stored in /etc/shadow file. Please note that you need to use the passwd command to computes the hash of a password typed at the CLI or to store/update the hash of the password in /etc/shadow file.
- User ID (UID): Each user must be assigned a user ID (UID). UID 0 (zero) is reserved for root and UIDs 1-99 are reserved for other predefined accounts. Further UID 100-999 are reserved by system for administrative and system accounts/groups.
- Group ID (GID): The primary group ID (stored in /etc/group file)
- User ID Info (GECOS): The comment field. It allow you to add extra information about the users such as user’s full name, phone number etc. This field use by finger command.
- Home directory: The absolute path to the directory the user will be in when they log in. If this directory does not exists then users directory becomes /
- Command/shell: The absolute path of a command or shell (/bin/bash). Typically, this is a shell. Please note that it does not have to be a shell. For example, sysadmin can use the nologin shell, which acts as a replacement shell for the user accounts. If shell set to /sbin/nologin and the user tries to log in to the Linux system directly, the /sbin/nologin shell closes the connection.
I hope you understood /etc/passwd file format to keep track of every registered user that has access to a system. Therefore, knowing the structure is essential for security reasons. Now, let us see some common examples of commands.
Task: See Linux User List
/etc/passwd is only used for local users. To see list of all users, simply use the cat command or more/less command:
$ cat /etc/passwd
The following is an example of an /etc/passwd file from Linux system powered by Alpine Linux:
root:x:0:0:root:/root:/bin/ash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin adm:x:3:4:adm:/var/adm:/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/mail:/sbin/nologin news:x:9:13:news:/usr/lib/news:/sbin/nologin uucp:x:10:14:uucp:/var/spool/uucppublic:/sbin/nologin operator:x:11:0:operator:/root:/sbin/nologin man:x:13:15:man:/usr/man:/sbin/nologin postmaster:x:14:12:postmaster:/var/mail:/sbin/nologin cron:x:16:16:cron:/var/spool/cron:/sbin/nologin ftp:x:21:21::/var/lib/ftp:/sbin/nologin sshd:x:22:22:sshd:/dev/null:/sbin/nologin at:x:25:25:at:/var/spool/cron/atjobs:/sbin/nologin squid:x:31:31:Squid:/var/cache/squid:/sbin/nologin xfs:x:33:33:X Font Server:/etc/X11/fs:/sbin/nologin games:x:35:35:games:/usr/games:/sbin/nologin cyrus:x:85:12::/usr/cyrus:/sbin/nologin vpopmail:x:89:89::/var/vpopmail:/sbin/nologin ntp:x:123:123:NTP:/var/empty:/sbin/nologin smmsp:x:209:209:smmsp:/var/spool/mqueue:/sbin/nologin guest:x:405:100:guest:/dev/null:/sbin/nologin nobody:x:65534:65534:nobody:/:/sbin/nologin nginx:x:100:101:nginx:/var/lib/nginx:/sbin/nologin vnstat:x:101:102:vnstat:/var/lib/vnstat:/bin/false redis:x:102:103:redis:/var/lib/redis:/bin/false
To search for a username called tom, use the grep command:
$ grep tom /etc/passwd
OR
$ grep -w '^tom' /etc/passwd
Sample outputs:
tom:x:1000:1000:Vivek Gite:/home/vivek:/bin/bash
Using the /etc/passwd file
Want to find out multiple users? Try the egrep command as follows:
$ egrep -w '^(tom|jerry|fox)' /etc/passwd
## OR pass the '-E' ##
$ grep -E -w '^(root|vivek|www-data)' /etc/passwd
Of course, one can get entries from /etc/passwd using the getent command too. For example:
$ getent passwd
$ getent passwd {user1} {user2}
$ getent passwd vivek
$ getent passwd vivek root

The /etc/passwd file keeps track of every user that has access to a system, and we can query it using the getent or grep command.
How to see /etc/passwd file permission
The permission on the /etc/passwd file should be read only to users (-rw-r--r-- OR 0644) and the owner must be root:
$ ls -l /etc/passwd
Sample outputs:
-rw-r--r-- 1 root root 2659 Sep 17 01:46 /etc/passwd
Use the stat command to see details about the file:
$ stat /etc/passwd
Outputs:
File: /etc/passwd Size: 3445 Blocks: 8 IO Block: 4096 regular file Device: fd02h/64770d Inode: 25954390 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2021-05-24 01:34:01.794296901 +0530 Modify: 2021-05-08 00:33:40.430038177 +0530 Change: 2021-05-08 00:33:40.434038185 +0530 Birth: -
Reading /etc/passwd file
You can read /etc/passwd file using the while loop and IFS separator as follows:
#!/bin/bash # seven fields from /etc/passwd stored in $f1,f2...,$f7 # while IFS=: read -r f1 f2 f3 f4 f5 f6 f7 do echo "User $f1 use $f7 shell and stores files in $f6 directory." done < /etc/passwd
Your password hashes is in the /etc/shadow file
So far, so good, right? But, where are my encrypted hashed passwords? Good question. Your encrypted password hashes are in the /etc/shadow file. There was no significant problem with this general read permission in the good old days. Everybody could read the encrypted passwords, but the hardware was too slow to crack a well-chosen password, and the basic assumption used to be that of a friendly user community. Therefore, we use /etc/shadow files on Linux and other Unix-like operating systems for security reasons.
How do I know am I using shadow files for passwords on my machine?
Almost all modern Linux and UNIX-like operating systems use shadow password suites. If your /etc/passwd files has asterisks (*) instead of encrypted (more like hash) passwords, then it is safe to assume that the encrypted passwords hashes are in /etc/shadow file. Please note that this file is only readable by the superuser only. Verify file permissions using the ls command or stat command:
$ ls -l /etc/shadow
$ stat /etc/shadow
Common commands that uses /etc/passwd files
Here is a list of commands that manipulate /etc/passwd file. Hence read the man pages using the man command or help command:
- passwd command
- su command
- sulogin command
- getent command
- login command
- pwck command
- pwunconv command
- chpasswd command
- chsh command
- chfn command
- useradd command
- userdel command
- id command
Conclusion
Please note that there are three main types of user account: the superuser, system users, and regular users. For example:
- root – The superuser (admin user).
- nginx – The system user used by Nginx web server.
- vivek – Regular user account.
A Linux user must have a primary group and may be a member of one or more supplementary groups as defined in the /etc/group.
The /etc/passwd file stores all user names and accounts on the Linux or Unix-like system. In other words, user account information is in the /etc/passwd file. Hence, you can confirm and read the documentation by reading the following man pages with the help of the man command:
$ man 5 passwd
- Understanding /etc/passwd File Format
- /etc/shadow file format
- Linux and Unix /etc/group file










What are the differences between system calls and Library functions?
– system call is a call of a service to be done by the kernel, it’s executed in the kernel address space.
– a library function call is done by “importing” (linking) the (library/function) code to the user’s program, and it’s executed in the user address space.
What is the need for /etc/shadow file, when there is /etc/shadow file?
Can the password be maintained in /etc/paswd file itself?
please tell me why Developers implemented two files /etc/passwd and /etc/shadow/
Actually the Passwd stored in the etc/shadow is the exact password which is encrypted and also the developer haven’t implemented two files the /etc/passwd is the symbolik link to the /etc/shadow
the /etc/passwd file will contain the details for the user created (uid, gid, home dir, login shell etc), whereas the /etc/shadow file will contain information specific to the password set for the users.
/etc/password is readable by all (useful for the 5th field: User ID Info).
Placing an encrypted password there would enable cracking.
/etc/shadow is not readable by anyone (other than the owner:root, or processes with SETUID root) . This prevents any attempts at password cracking.
like Gabe said
surya – There may be other reasons, but one reason is that the /etc/shadow file is not readable by any user except root. Whereas the /etc/passwd has legitimate reasons to be read by other users. Even though the passwords can be encrypted directly in /etc/passwd, that is still less secure than have even the encrypted passwords hidden.
I have been asked to create a new user on an HP-UX 7.05 machine circa 1990.
Editing the /etc/admin file in Motif to add my user account resulted in that user having denied access. the user name was as added as a user to /etc/groups. I used a new UID fot the user.
Any clues as to what i did wrong?
Thanks
That was /etc/passwd
First let me tell tht i am newbie into the linux arena.
Please educate me how uupdated pwds of the users are been changed in /etc/shadow which has only read perminssions
Praveen Joy.
Good question.
A concept called SUID is used here.
“The SUID permission makes a script to run as the user who is the owner of the script, rather than the user who started it.”
The “passwd” command is present located under “/usr/bin”. Check the permissions for this file using.
ll /usr/bin/passwd
(Note that an extra ‘s’ is added to the rwx permissions)
For any further queries, mail to s.manoj89@gmail.com
What does it mean if the password (2nd field) leaves blank or shows as “*”? Thanks.
If the second field in /etc/passwd file is set with “*” then the password is disabled for the respective user
So what does it mean? Is the user account can still login?
In the ETC/Passwd file what functionality are the five accounts used for : Shutdown, Sync, Halt, News and Netdump ? Are these logins or are they just command files? And why don’t they have a Nologin at the end of their paths?
Thanks Jerry
In RHEL, every process runs under a particular user. Users corresponding to certain processess dont have the need to login. So, they have been assigned with a nologin shell. We can use the option “-s /sbin/nologin” while creating the user/while using “usermod”.
nologin is shell which displays a message that an account is not available. It is intended as a replacement shell field for accounts that have been disabled or only use by system internally.
In general the /etc/password and associated shadow files are very *nix dependent. ( AIX, HP-UX, linux… )
Praveen: passwords are updated by the passwd command.
Jenny: the star in the password field means “password is in shadow file”. If the password filed is null ( i.e. :: ) account is not passworded (bad)!
what can i do??
Similar to Jenny’s question… what if the second field (password) in the /etc/passwd file is “*” but the /etc/shadow file is not in use?
If the /etc/shadow file is not there, a login attempt will first refer the /etc/passwd file which will in turn try to search for the /etc/shadow file. When it is not able to find that file, it will throw an error saying that the permission is denied(to login)
how to line for only ftp user?
example
user:x:1000:(www-data id):(?):(?)
is true?
Hi, a am migrating from Solaris 8 to Solaris 10, and i have a lot of users that i want to migrate. Is there a quick way to do this not by hand one by one?
I was thinking that maybe copying the /etc/passwd, /etc/shadow and /etc/group files would do the job?
Please see this faq about migrating user accounts.
how to read the password and compair it with the one that is in the /etc/passwd or /etc/shadow
anybody knows how to expire user’s password whos entry is there in /etc/passwd file
passwd -f userid
@sparta_tushar,
Use chage command.
Kindly define all 7th points beriefly like Username Password UID GID Comments Home Directory Shell with respect of /etc/passwd File
Any one can aswer …..kindly do ASAP
If any of you have access to root than you wouldn’t be asking how to view/expire/delete, etc the password in the shadow file. There is absolutely no need to if you are root. If you want to expire a password it would be more efficient to su into the user (of course assuming you are root), and passwd yourself your own password. Again, there is no need to see an encrypted password for whatever reason. Just by glancing at the things some of you want to do makes me wonder whether you guys are either trying to hack into someone’s account, or play a prank on them, etc…
pleas tel me in what format passwords are stored in shadow file?means i want ask you that what encryption is used in shadow file to store password?
thanks
nice notes for engg students
Hi,
We are using solaris 10 on jumpstart. We have tried to change the passwrod for root since we have forgotten it. But know the system cannot find user root.
Can you help us to recreate root user? Is there anyway?
Thanks.
I have a question about the /etc/passwd file
I have a number of users accessing a system and while my security is very good by use of firewall and strict permissions on all files I would like to stop users from viewing the /etc/passwd file purely because I don’t want my clients to know who my other clients are.
Is there any way, other than using chroot to do this?
we can change the permission of the file /etc/passwd using the command chmod
thanks sir
sir tell me predefined accounts
for example
Alex:
There are several reasons that the /etc/password file is read all.
Most expect a cooperative community of users.
There are many other issues you need to address to prevent users from knowing who other users are. like ls /home
It would seem that your users have telnet access. Have you looked into “jail” shell.
or removing shell access to from your users.
PS since this is much more complected that /etc/password please start a new thread.
Vipin:
To see predefined users for the distribution you are using (they are all different)
see /etc/passwd however
note that users like like nobody, daemon, have user numbers below 100
may have the default shell of something like /usr/bin/false which prevents these users from logging in.
hi sir i want file access permission by using simble -c,b,c,i,p and s
Application crashes on solaris if there is an empty line at the end of /etc/passwd, Please let me know why this happens.
Can any one explain below mentioned entry? Is it ok to remove or its kind a wild card?
?:x:60020:1::/home/?:/bin/sh
Although you have not mentioned what system you are seeing this on,
I believe this is an error on the part of someone who tried to mkuser
I have a question about the /etc/passwd file:
Usually a normal user do not have direct permission to write in a passwd/shadow file.
Though when user changes his passsword then ultimately he is altering the /etc/passwd or /etc/shadow file.
What is the mechanism behind this?
Good question.
A concept called SUID is used here.
“The SUID permission makes a script to run as the user who is the owner of the script, rather than the user who started it.”
The “passwd” command is present located under “/usr/bin”. Check the permissions for this file using.
ll /usr/bin/passwd
(Note that an extra ‘s’ is added to the rwx permissions)
For any further queries, mail to s.manoj89@gmail.com
Hi,
We are having a problem with our controller card log-in, one of the staff was resign and change the root user password, hoping you could help us recover it. by the way we could log-in as other user “apadmin” but we need to use as “root” since we need to configure sometimes the controller. hoping for your help and quick response…… thanks a lot and godbless
Notice that the command to change your password is
-r-sr-xr-x 1 root wheel 70352 Jun 18 22:39 /usr/bin/passwd
Owned by root and the s in the permissions is the SETUID bit.
This means that, when you run this program, your User ID is set to root,
and since root is the owner of the /etc/passwd you can update it!
The same it true of:
at, atq, atrm, batch, chfn, chpass, chsh, crontab, cu, ipcs, login,
lppasswd, newgrp, quota, rlogin, rsh, su, sudo, top, uucp,
uuname, uustat, uux
My hosting company expects me to SSH using password authentication (rather than key) . I have edited ssh_config and sshd_config to switch passwordauthentication to yes, but do I need somehow to get the password into the shadow file – the server response does not even prompt me for a password – it just refuses the connect attempt.
can u explain how the /etc/shadow and /etc/passwd directories are used in the authentication process?why are they two files used instead of one?how can i convert a system to use the /etc//shadow file to the store password?
thanks
an example of absolute pathname is shown as: /home/student/myprogs while a relative pathname can be shown as : ../../documents what are differences between absolute and relative pathname and what is advantages.
ABDUL AWAL: Pease read paragraph “Your password is stored in /etc/shadow file”
ABDUL AWAL: Assuming you are referring to the above:
“#6 Home directory: The absolute path to the directory the user will be in when they log in….”
I seems unwise to use a relative path in the /etc/passwd file.
i say just thanks to every user of linux to every teacher of linux to every lover of linux
please send easy note easy commands of linux to me i will be pray for u are
just send good and easy way to improve my linux knowledge
Excellent work dude…. Thanks..
i don’t understand what is the setting s -bit and t- bit ??????
why it is relevant???
What if two users have the same UID and GID?
Then they ARE the SAME user!
Actually I have learned that they are not the same user. In fact they can have separate home directories as well as passwords so they’re not the same.
ALexP,
Your are correct.
In addition to the password and home directories being unique, the UserId and command/shell are unique.
They are the same user with regard to file ownership as this is done by UID and GID.
Other authorizations like sudoers (who can execute what “priveledged commands” usually restricted to the SUper user ) have both username and UID as options for the user.
ftpd users a separate authorization scheme only by username.
mail is also username (not UID) dependent.
findgerd, talk, write, who all seem to use username.
So I guess the real answer is … depends!
Hi,
I just wanted to know that how do I identify that a user is locked on the following OS
1) Linux: Is it gauranteed to be a single exclamation mark (!) before the encrypted password in shadow file across all flavours of linux
2) Solaris: I am aware that it also has a shadow file. But want to confirm whther ! is the token for locked user
3) HP-UX: What is the token
4) AIX: AIX doesn’t has any shadow file. How do I come to know who all users are locked like I can do by reading /etcshadow file on other platforms.
Why there is another file (in Fedora)
/etc/passwd-
Not in fedora but also in Redhat ,Its for backup purpose ,if the /etc/passwd file is modified somehow , then it can be backed up from /etc/passwd-
Hi, every time when i change or reset user’s password it also changed the permissions in /etc/shadow which deny or lock-out database user’s, this is very risky as i’m working in a production server. could you please help.
hi
I am new to unix.If passwords are stored into /etc/shadow file and this file is readable by super user only then how user are log in into system i.e they must have access to password file for matching password .plz help me
Thank you for this informative post. Just what i have needed to understand login relation with passwd. Also well written users with a lack of unix knowledge.
Best one so far, keep it up!
List from the /etc/passwd the UID and the user having the highest UID
Dear site owner,
Thanks for nice site! Keep it updated ;)
How do I change my user account password on my computer? I am using linux a friend put it on my computer for me but I wish to chage the password and dont know how to do it? can anyone help me?
“I wish to change it” seeks to indicate that you can log on.
use
passwd
You will be prompted for your current password.
This prevents someone else from changing your password if you walked away and were still logged in.
Detailed info on your system is in the man pages since different versions of *unix are different in their requirements.
man passwd
Very nice and usefull information
thanks a lot
I appriciate this one..
Blessings…
what is pico in linux
pico is a little tiny editor.
nano is even littler and tinyer editor
The is a id thru which i can login but when i check it in /etc/passwd, its not there.
Any one knows the reason?
What flavor of unix are you using? linux, bsd darwin (Mac) aix hpux …
What distribution are your using?
how can i generate that encrypted passwds …
means i want to assign a passwd to a user eg. laka is qwerty
then how can i encrypt dis string(qwerty)
as i want to make a entry of dis encrypted passwd in the shadow file manually…
plzz help me out… :)
On FreeBSD machines a special program is run by vipw(8) after you
edit the /etc/master.passwd file. That special program is what generates
/etc/passwd as well as some special database files that speed up various
lookups of account information (e.g. mapping a uid to a username). What
is the name of that special program?
Thanks in advance :)
A user can change his own password.. That being the case, how does the passwd file which is owned by root, get modified??
I was asked this question in an interview and it left me puzzled. Any ideas people!?
Excellent question.
Short answer: While there are slight variations dependent on the specific version of unix the basic approach is the same and has the same answer for many “privileged” operations that can be performed by a user on their own objects.
under redhat-linux-gnu
which passwd displays /usr/bin/passwd
ls -l /usr/bin/passwd
-rwsr-xr-x 1 root root 27936 Aug 11 2010 /usr/bin/passwd
notice that the password program is owned by root and that the mode (aka permissions) include the “sticky” bit. This causes the password program to have the effective user ID of root when it runs. See http://en.wikipedia.org/wiki/Setuid
thanks! btb,. I was asked wrt Solaris. I answered the question in an uncertain tone.. “sticky bit”. But the devil’s son smiled as if in mockery.. and i quit answering further. damn that fellow!!
Excellent question.
Short answer: While there are slight variations dependent on the specific version of unix the basic approach is the same and has the same answer for many “privileged” operations that can be performed by a user on their own objects.
under redhat-linux-gnu
which passwd displays /usr/bin/passwd
ls -l /usr/bin/passwd
-rwsr-xr-x 1 root root 27936 Aug 11 2010 /usr/bin/passwd
notice that the password program is owned by root and that the mode (aka permissions) include the “SETUID” bit. This causes the password program to have the effective user ID of root when it runs. See http://en.wikipedia.org/wiki/Setuid
Similar to Jenny’s question… what if the second field (password) in the /etc/passwd file is “*” but the /etc/shadow file is not in use?
What does it mean if the second field (password) in the /etc/passwd file is “!” but the /etc/shadow file is not in use and the 7th field is /usr/bin/ksh?
Anyone know what this means in Linux SLES 11 and can it be removed – audit says it should be there:
[root@imnalx0277 etc]# cat /etc/passwd |grep +
+::::::
Excuse me – “+” should not be there
Which file stores Group members and User’s Login Shell
[framework@[192_168_15_244] framework]$ cat /etc/shadow
root:UbgIcihE85Xz.:10933:0:99999:7:::
daemon:*:10933:0:99999:7:::
bin:*:10933:0:99999:7:::
sys:*:10933:0:99999:7:::
sync:*:10933:0:99999:7:::
operator:*:10933:0:99999:7:::
sshd:*:10933:0:99999:7:::
messagebus:*:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default::10933:0:99999:7:::
framework:$1$Cewr2/zS$SnxBS8yTMZeIgf/Tk//Xo/:14033:0:99999:7:::
how to figure out the real password of the account ROOT?
Can you please tell me about its windows counter-part. I am curious to understand the same mechanism for windows.
I’ll be very much thankful for explanation.
Good information.
Thanks
Hi, i am a bit clueless with this qns:
1) what about does the login shell of operator do?
2) what is the r/s between operator and root?
3) what do you think is the purpose of operator userid in centos system?
Hi to all,
I want to know that how can i change the database password in etc/passwd file?
how to find if the user is present or not?
Hi,
thanks a lot
What is the meaning of “passwd” in Unix?
hi everyone. I’m learning about unix. I have a question is how to auto login into an account without typing account and password.
Example my account is “working” and password is “Leona1234”
thanks
One mistake in the article: It does state that /etc/passwd holds only local users, but then goes on to state that “To see a list of all users, enter: cat /etc/passwd”. You’ve just said that /etc/passwd holds only local users. To see a list of all users, you need to use the command “getent passwd”, not “cat /etc/passwd”.
why do all system users have access to file /etc/passwd?and
what are the structures of the files /etc/group and /etc/shadow?
thank u for this information…!!!!
I have a password file where the password part starts $6$Yct0VL8AzUzydaAX$… and is very long (106 characters total) Any idea what format this is ?
what is the encryption used to store passwords in /etc/shadow, I would like to use them.
Apologies if this is a little OT – but your post has the best info on this file and I *think* this is my issue.
I am helping a client migrate mail accounts and content from a poorly configured addon domain in a cpanel environment to a new domain host.
The accounts, passwords and content have been copied across and IMAP is still working with old passwords and names, however they cannot access old emails from pre-migration. They receive new mail ok.
I found that the path links (section 6 in your post) in the “/etc/domain/passwd” file still point to the old host paths (/home/olddomainuser/mail/olddomainname/username).
I think this is their issue but need to know if updating these paths is safe or will it cause a flow-on issue with other scripts.
Our host (Netregistry) is pathetic at support and I’m left trying to fix this issue for the client myself.
I’m also concerned that the user IDs and groups may be different so am not game to edit as they are currently receiving new emails but just can’t see old content.
For additional info: webmail shows a correct count including old emails, however when going through pages of webmail pre-migration, they come up with “no messages in this mailbox” thats in any webmail client too – roundcube, squirrel, horde.
It’s like a index file or checksum file needs repairing too maybe…
Can any ninjas out there shed some light on this?
Many thanks and great description of the file structure in your post thankyou
1. What is the user id and group id of for your username (found in the passwd file)?
2. What is the user id and group id of the root user (found in the passwd file)?
3. What hash function is used to generate the hash value for your username and password
that is stored in the shadow file?
4. What is salt and stored hash value of the password for your username (found in the
shadow file)?
5. What command can you use to regenerate and verify the stored hash value for the
password for your username?
Really helpful! Thanks!
Yes client can login if
public key is previously transferred from client to server side at
~/.ssh/authorized_keysAssuming that transfer is already done, private-public key login using ssh client is like this:
ssh -i ~/.ssh/id_rsa user@ipaddress~/.ssh/id_rsais default location on client side of file containing private key…
The /etc/passwd file keeps track of all Linux user accounts on the server and I needed to understand it. Your page was very much useful. Better than man pages. Thank you kind Sire.
Thank you, Vivek Sensei. Sayōnara.
yes was helpful
me gusta mucho
When trying to bypass maintenance pw.
Ctl d redirects me to the advanced menu.
Still no access to root