10-25-2019
Quote:
Originally Posted by
Peasant
Even if you do all possible magic, a shell access and permissions would still allow user Bob to copy / change / execute the shell code on server1.
This is not a stated requirement of the original poster (OP).
The OP only stated he wanted to have files in a directory which are not executable because they are for reference only.
The user "Bob" already has access to executable copies, per the OP.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone:
I'm trying to make a CRON job that will execute Fridays at 7am. I have the following:
* 7 * * 5
I've been studying up on CRON and I know to have this in a file and then "crontab filename.txt" to add it to the CRON job list.
The CRON part I believe I understand, but I would... (6 Replies)
Discussion started by: Annorax
6 Replies
2. Shell Programming and Scripting
Hi all,
Is there a way to prevent users from being able to execute commands less a select few? For instance, I wish to allow the user to be only able to execute 1 command, which is exec a.sh. He should not be able to do simple stuff such as ls, cd, rm, cat, etc.
Can this be achieved?
... (1 Reply)
Discussion started by: rockysfr
1 Replies
3. UNIX for Advanced & Expert Users
Hi All,
It will be very great if you can help me in this issue. Thanks in advance.
I need to enable FTP on a solaris9 server. I need to create a new user some "xxxxxx" and he can only FTP the files to and from between /tftpboot directory and network devices. Other users should not... (8 Replies)
Discussion started by: santhoshkumar_d
8 Replies
4. UNIX for Dummies Questions & Answers
specifically - I don't need to restrict a user to a single directory - but I want them to be "ROOTED" to their home directory.
so if my home directory is /home/onlyme
when I login - if I do a pwd - I want to see:
/
but in real life I will be in /home/onlyme - it just appears as root to... (10 Replies)
Discussion started by: itobenon
10 Replies
5. UNIX for Dummies Questions & Answers
Hi
I need to restrict one user to see only his home directory and
one more directory how i can do this in his profile.
The OS is Red hat linux
I create a user -- tec
and group calle --tec
one the user log in he will see
/home/tec
and he need to see /opt/load
this dirctory... (6 Replies)
Discussion started by: aboorkuma
6 Replies
6. Linux
Hi Gurus ,
I hope you are doing great .
Other than owner of the file , OTHERS and GROUP should be restricted from read or write a file created by the owner.
OTHERS and GROUP should be only allowed to execute the file.
Thanks in advance. (8 Replies)
Discussion started by: palanisvr
8 Replies
7. Red Hat
Hi
I have a Fedora10 server and i need a particular user to view files only in a particular folder.
All other files in other folders having "read" permission for all shouldn't be accessible to this user.
Please let me know if ther's a way.
Thanks,
HG (5 Replies)
Discussion started by: Hari_Ganesh
5 Replies
8. Solaris
I am using Solaris 10 on SPARC.
SunOS ddw 5.10 Generic_139555-08 sun4u sparc SUNW,SPARC-Enterprise
I have put some text files in a directory '/u01/network'
I want to create a ftp user which can just read the files in the network directory. The ftp user shouldn't be able to navigate or see... (4 Replies)
Discussion started by: fahdmirza
4 Replies
9. Solaris
Hi all,
I want to create a new user and grant him ONLY transfer files access to a specific directory where he can only upload and read the files. He should be restricted to this activity only.
Regards (6 Replies)
Discussion started by: gilldn
6 Replies
10. AIX
hi,
I want to restrict some user access to only 1 directory (including all sub-directories/files in it).
can you please explain me, how can we do this?
example;
Filesystem GB blocks Used Free %Used Mounted on
/dev/hd4 2.61 1.02 1.59 40% /
/dev/hd2 ... (7 Replies)
Discussion started by: aaron8667
7 Replies
chsh(1) General Commands Manual chsh(1)
NAME
chsh - change login shell
SYNOPSIS
chsh [-D binddn] [-P path] [-s shell] [-l] [-q] [-u] [-v] [user]
DESCRIPTION
chsh is used to change the user login shell. A normal user may only change the login shell for their own account, the super user may
change the login shell for any account.
If a shell is not given on the command line, chsh operates in an interactive fashion, prompting the user with the current login shell.
Enter the new value to change the field, or leave the line blank to use the current value. Enter none to remove the current value. The
current value is displayed between a pair of [ ] marks.
The only restrictions placed on the login shell is that the command name must be listed in /etc/shells, unless the invoker is the super-
user, and then any value may be added. An account with a restricted login shell may not change their login shell.
This version of chsh is able to change the shell of local, NIS, NIS+ and LDAP accounts , if the permissions allow it.
OPTIONS
-D, --binddn binddn
Use the Distinguished Name binddn to bind to the LDAP directory. The user will be prompted for a password for simple authentica-
tion.
-P, --path path
The passwd file is located below the specified directory path. chsh will use this files, not /etc/passwd. This is useful for exam-
ple on NIS master servers, where you do not want to give all users in the NIS database automatic access to your NIS server and the
NIS map is build from special files.
-s, --shell
Specify your login shell.
-l, --list-shells
Print the list of shells listed in /etc/shells and exit.
-q, --quite
Don't be verbose.
-u, --usage
Print a usage message and exit.
--help
Print a more verbose help text and exit.
-v, --version
Print version information and exit.
FILES
/etc/passwd - user account information
/etc/shells - list of valid login shells
SEE ALSO
chfn(1), passwd(5), shells(5)
AUTHOR
Thorsten Kukuk <kukuk@suse.de>
pwdutils February 2004 chsh(1)