FWIW, storing the password in an environment variable makes the information available to all users with access to a bsd ps on the box.
Are you able to use sudo? You could store the passwords in a central set of files, readable only by specific groups.
Create specific system users and allocate them to the appropriate groups.
You can then allow certain users to run your various scripts as the specific system users. Your script then goes and looks up the file in question for the DB and uses the password contained within.
This also gives you the ability to create a script for retrieving passwords inline for users with the appropriate rights (say admins only?) to use in _any_ script they want.
The local policy is set in our LAN so that passwords have to be 8 characters and contain a capital letter, a small letter and a special character. Is Unix able to restrict users passwords to certain lengths and characters. (1 Reply)
I'm finding the following command very tedious to type in all the time, so I created a one line bash script called mount.bash with the following contents:
mount -t cifs //mark/C\$ -o unc=//mark\\C$,ip=10.1.1.33,user=Administrator,password=$1 /mnt/mark
I don't like the fact that I have to put... (5 Replies)
Hi Unix experts....
I am in the process checking user and root password of more than 1000 servers manulay.
I am very pissed of checking these many servers manualy.
Could some one of you help me how can i check the passwords just by runing some scripts..!
Need Help Guys..! :confused: (5 Replies)
Hi All ,
I need to call a script runscript_B.sh on server A, the runscript_B.sh script locating in server B.
The runscript_B.sh in calls another script runscript_A on server A itself.
it seend, i need to be connect from Server A to Server B using ssh.
I have tryed like this in... (3 Replies)
Hi,
Can anyone tell me how to call a oracle package from a Unix shell script? I want to pass some input parameters to package and it will return me the output which I want to use further in my shell script. I want to know the way to capture the output values in my shell script. Please send some... (1 Reply)
Dear Members,
I have a table REQUESTS in Oracle which has an attribute REQUEST_ACTION. The entries in REQUEST_ACTION are like, ME, MD, ND, NE etc.
I would like to create a script which will will call other scripts based on the request action.
Can we directly read from the REQUEST_ACTION... (2 Replies)
I've been using various versions of UNIX and Linux since 1993, and I've never run across one that showed your password as you type it in when you log in, or one that stored passwords in plain text rather than encrypted. I'm writing a script for work for a security audit, and two of the... (5 Replies)
I want to store the passwords in a global file, so that all the users will not use them to login but a process should use it. One way is to keep the passwords in a .ini file and execute the file in the start of the script and use that variable.
But with this, one can echo the variable in the... (15 Replies)
Discussion started by: karumudi7
15 Replies
LEARN ABOUT PLAN9
newuser
NEWUSER(8) System Manager's Manual NEWUSER(8)NAME
newuser - adding a new user
SYNOPSIS
rc /sys/lib/newuser
DESCRIPTION
To establish a new user on Plan 9, add the user's name to /adm/users by running the newuser command on the console of the file server (see
users(6) and fs(8)). Next, give the user a password using the changeuser command on the console of the authentication server (see
auth(8)). At this point, the user can bootstrap a terminal using the new name and password. The terminal will only get as far as running
rc, however, as no profile exists for the user.
The rc(1) script /sys/lib/newuser sets up a sensible environment for a new user of Plan 9. Once the terminal is running rc, type
rc /sys/lib/newuser
to build the necessary directories in /usr/$user and create a reasonable initial profile in /usr/$user/lib/profile. The script then runs
the profile which, as its last step, brings up 81/2(1). At this point the user's environment is established and running. (There is no
need to reboot.) It may be prudent at this point to run passwd(1) to change the password, depending on how the initial password was cho-
sen.
The profile built by /sys/lib/newuser looks like this:
bind -a $home/bin/rc /bin
bind -a $home/bin/$cputype /bin
font = /lib/font/bit/pelm/euro.9.font
switch($service){
case terminal
prompt=('term% ' ' ')
fn term%{ $* }
exec 81/2
case cpu
bind -b /mnt/term/mnt/81/2 /dev
prompt=('cpu% ' ' ')
echo -n $sysname > /dev/label
fn cpu%{ $* }
news
case con
prompt=('cpu% ' ' ')
news
}
Sites may make changes to /sys/lib/newuser that reflect the properties of the local environment.
Use the -c option of mail(1) to create a mailbox.
SEE ALSO passwd(1), 81/2(1), namespace(4), users(6), auth(8), fs(8)NEWUSER(8)