12-05-2007
Restricted Login ID
I have a task to create a new id that going to used by vendor. The ID profiles are:
1)The ID to be created is MUST be restricted sharing.
2)create for their own user account
3)unable to read/navigate/view other directories
4)unable to write to other directories
able to create their own directory
I have used the 'rsh shell' but it disallows the "cd" command. Is there any other options?
Your cooperation is highly appreciated.
Thanks in advance
10 More Discussions You Might Find Interesting
1. Cybersecurity
On AIX 4.3.3 , how telnet access will be allowed to few users only whereas other will not be able to telnet the server? (6 Replies)
Discussion started by: amit
6 Replies
2. Cybersecurity
A few of the other employees here need to learn "vi" in order to use crontab to schedule / unschedule jobs on one of our production servers. I tried to set up a login on one of my Linux boxes for them to use "vimtutor", but scrapped it and decided to try for something more secure, since there are... (1 Reply)
Discussion started by: LivinFree
1 Replies
3. UNIX for Dummies Questions & Answers
HI
I was wondering how do i get in to the restricted mode in solaris
>
I can get into the ok prompt ok> or the fourth monitor mode but not the restricted mode >
any ideas
thanks (3 Replies)
Discussion started by: xNYx
3 Replies
4. UNIX for Dummies Questions & Answers
Hey,
Could someone please help me distinguish between a captive account and a restricted shell?
Many thanks,
L. (0 Replies)
Discussion started by: crispy
0 Replies
5. UNIX for Advanced & Expert Users
I am having trouble getting restricted SAM to work by allocating Privileges to a "group". I can make it work by allocaing to the userid's, but would preferre to use the "group" option.
Running B.11.11
Tried the following....
1) Created a user group in /etc/group first
2) Used the... (1 Reply)
Discussion started by: Andrek
1 Replies
6. Programming
Hi all. I am trying to use restricted pointers to allow the gcc compiler optimize the code, but I have not been able to make it work so far. I am testing with this code:
#include <stdlib.h>
#include <stdio.h>
#include <time.h>
#include <sys/time.h>
void vecmult(int n, int * restrict a, int... (0 Replies)
Discussion started by: carl.alv
0 Replies
7. UNIX for Dummies Questions & Answers
Hi Expert,
I have 2 questions.
Scenario: Users login via ssh from other location, using putty. or any other equivalent ssh tunnel. All users has been assigned as sudoers due to testing environment.
1. How to disable sudoers from editing /etc/sudoers
e.g
$ sudo vi /etc/sudoers
2.... (3 Replies)
Discussion started by: regmaster
3 Replies
8. AIX
I've created a specific FTP user restricted to only it's home dir. Eg as below:
User: ftp01
Home Dir: /home/ftp01
As I want this user to only able to access his home dir only, I've created /etc/ftpaccess.ctl and refresh the inetd daemon:
useronly: ftp01
readwrite: /home/ftp01
It... (1 Reply)
Discussion started by: shiniraz
1 Replies
9. AIX
Hello
I have a user with a Restricted Shell on a Aix 5.3. My question is about if I can add one more path on the home directory.
I mean the user have in his home directory. for example /test/my_application/logs but I need that this user can view another log that is on another path, if this... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
10. AIX
Hello everyone
I need to create a restricted user or a special user. Here is what I need.
I have this path
next to profiles I have server1, server2, server3.......
The user that I have to create I need that he can move between server1. server2, server3 because in every one have logs... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
LEARN ABOUT REDHAT
passwd
PASSWD(5) File formats PASSWD(5)
NAME
passwd - password file
DESCRIPTION
Passwd is a text file, that contains a list of the system's accounts, giving for each account some useful information like user ID, group
ID, home directory, shell, etc. Often, it also contains the encrypted passwords for each account. It should have general read permission
(many utilities, like ls(1) use it to map user IDs to user names), but write access only for the superuser.
In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the
hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user-community.
These days many people run some version of the shadow password suite, where /etc/passwd has *'s instead of encrypted passwords, and the
encrypted passwords are in /etc/shadow which is readable by the superuser only.
Regardless of whether shadow passwords are used, many sysadmins use a star in the encrypted password field to make sure that this user can
not authenticate him- or herself using a password. (But see the Notes below.)
If you create a new login, first put a star in the password field, then use passwd(1) to set it.
There is one entry per line, and each line has the format:
account:password:UID:GID:GECOS:directory:shell
The field descriptions are:
account the name of the user on the system. It should not contain capital letters.
password the encrypted user password or a star.
UID the numerical user ID.
GID the numerical primary group ID for this user.
GECOS This field is optional and only used for informational purposes. Usually, it contains the full user name. GECOS means
General Electric Comprehensive Operating System, which has been renamed to GCOS when GE's large systems division was sold
to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The gcos
field in the password file was a place to stash the information for the $IDENTcard. Not elegant."
directory the user's $HOME directory.
shell the program to run at login (if empty, use /bin/sh). If set to a non-existing executable, the user will be unable to
login through login(1).
NOTE
If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist.
If the encrypted password is set to a star, the user will be unable to login using login(1), but may still login using rlogin(1), run
existing processes and initiate new ones through rsh(1), cron(1), at(1), or mail filters, etc. Trying to lock an account by simply chang-
ing the shell field yields the same result and additionally allows the use of su(1).
FILES
/etc/passwd
SEE ALSO
passwd(1), login(1), su(1), group(5), shadow(5)
1998-01-05 PASSWD(5)