Group::- <- anyone in the same group is still denied u1% umask 700 mkdir /f setfacl -m user:u2:rwx /f To demonstrate the setfacl and getfacl commands, consider three users, 'u1,' 'u2,' and 'u3.' We are looking at folder '/f' owned by 'u1.' 'u1' will grant access only to 'u2,' leaving 'u3' out. This provides the best accounting, restricting, and upgradable path. In short though, make the authentication for accessing the folder come through the operating system user authentication method.

'password123') then PAM can enforce complexity and length on passwords. If you think passwords used will be too weak (e.g. ssh, X11, console, serial, ftp, Subversion), then learn about the complex world of PAM (Pluggable Authentication Modules) and restrict their options. If your are concerned that there are too many ways for someone to use an account (e.g. Note that 'the password' you desire is tied to the account doing the access. You also have some advanced tricks with the setfacl(1) and getfacl(1) commands. In situation #1, you have Unix permissions via the chmod(1) command available to you. You want to keep everybody, anywhere, anytime, out of a folder without permission.You want to keep other users on a system out of a folder.You are asking about a specific solution to an unspecified problem. Standard Unix permissions or extended permissions do provide some reasonable level of protection though. The real answer is that using a password to protect a folder does not work.

Put password on folder