Sponsored Content
Top Forums UNIX for Dummies Questions & Answers New Approach Hiding login password from ps -ef Post 302309573 by simonsimon on Wednesday 22nd of April 2009 09:29:23 AM
Old 04-22-2009
Thanx GSalisbury. I am still wondering is there no simple straighforward way to do this.

I am new to UNIX. I am sure there must be a way thru some os permission setting.

I see this is such a basic requirement. WHy would we even need to write a script to do this.

Dont you think the OS should be able to handle this.
Its like in a Database I can easily revoke permissions from a procedure from a specific USER.
Would the OS not have such a provision for a specific user ?

Thanx
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Hiding password from ps

I'm calling a program with a command line arguement containing a password. while the process is running anyone on the system can ps -ef and see the password. Is there a way to prevent this from happening. example PROGRAM USERNAME/PASSWD I've also tried PROGRAM `cat passfile` ... (7 Replies)
Discussion started by: sudojo
7 Replies

2. UNIX for Dummies Questions & Answers

Hiding login/password in process!

Hello, I am trying to figure out away to hide a command from users when performing a ps check. I have a ksh that purges a table in a database. If I perform a >ps -eaf |grep ksh, I get the login id and password. I do not want other users seeing this. Is there a way to hide this. The login... (5 Replies)
Discussion started by: ctcuser
5 Replies

3. Shell Programming and Scripting

Hiding password for FTP in a script

Hi, I have a simple script to ftp from unix to a mainframe to get and put files. Currently I have the password setup in a VARS file and dereference the var in my script. Doing it this way allws me to change the password in only one place but it is still viewable for many people. Is there any... (6 Replies)
Discussion started by: Cass3
6 Replies

4. UNIX for Dummies Questions & Answers

Hiding Password

Hello. A bit of a puzzle here: I have a 3rd party executable, which requires the following parameters: parm1 = program_name, parm2=userid/password, parm3=additional flags. We tried passing password as a variable, but you can do grep, and see what the password actually is I found a bit... (2 Replies)
Discussion started by: Kishinevetz
2 Replies

5. Solaris

SSH Password-less login fails on password expiry.

Hi Gurus I have a few Sol 5.9 servers and i have enabled password less authentication between them for my user ID. Often i have found that when my password has expired,the login fails. Resetting my password reenables the keys. Do i need to do something to avoid this scenario or is this... (2 Replies)
Discussion started by: Renjesh
2 Replies

6. Shell Programming and Scripting

Scripting help/advise on hiding/masking username/password

Hi, I currently have a UNIX script with a function that uses a username and password to connect to the database, retrieve some information and then exit. At the moment, am getting the username and password from a hidden plain text file and permission set to -r--------, i.e. read only to who... (1 Reply)
Discussion started by: newbie_01
1 Replies

7. Shell Programming and Scripting

Remote call not hiding password fields

Not sure on the description, but here is a quick rundown. I have 2 servers, we'll call them serverA serverB On serverB, I am calling a script that inside it has the following: ssh srvdsadm@serverB sudo -u dsadm /opt/apps/DataStage/scripts/autoDeploy.sh ${projName} ${subProjVar}... (1 Reply)
Discussion started by: cbo0485
1 Replies

8. Shell Programming and Scripting

Password hiding in UNIX

Hi guys, I use STTY command to make the password invisible. Now I need to write the password into another file pwd.txt, but in an invisible manner, something like ******. Another thing is to when I echo the content of pwd.txt I get the password I actually typed. Thanks guys. Help me out. (5 Replies)
Discussion started by: mohanalakshmi
5 Replies
mesg(1) 						      General Commands Manual							   mesg(1)

NAME
mesg - Permits or refuses write messages SYNOPSIS
mesg [y | n ] [Tru64 UNIX] The following format is supported for backward compatibility: mesg [[-]y[es] | [-]n[o] ] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: mesg: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPERANDS
Grants permission to other users to send messages to the terminal device. [Tru64 UNIX] You can optionally include a - (hyphen) before y, include es after y, or both. Denies permission to other users to send messages to the terminal device. [Tru64 UNIX] You can optionally include a - (hyphen) before n, include o after n, or both. DESCRIPTION
The mesg command controls whether other users on the system can send messages to you with the talk and write commands. Called without arguments, mesg displays the current terminal message permission setting. [Tru64 UNIX] The shell start-up procedure disallows messages by default. You can override this default action by including the line mesg y in your $HOME/.profile (sh), (csh), or (csh) file. Note [Tru64 UNIX] This default setting described for the shell start-up procedure message permissions assumes that the shell is one started as part of a login session. If the shell got started by some other means, the default depends on what that other program has done. [Tru64 UNIX] Any user can send messages with write if the receiving user has enabled messages. A user with the sysadmin command autho- rization can send messages to any terminal. The terminal device affected is determined by searching for the first terminal in the sequence of devices associated with standard input, standard output, and standard error, respectively. (In other words, the affected device is not the same as the controlling terminal for the session.) [Tru64 UNIX] Message permission has no effect on messages delivered through the electronic mail system. [Tru64 UNIX] If you add mesg y to your $HOME/.profile, you will be able to receive messages from other users via the write command or the talk command. If you add mesg n to your $HOME/.profile, you will not be able to receive messages from other users via the write command or the talk command. The mesg command also accepts the current locale's equivalent of yes and no. These equivalents are determined by the setting of the LC_MESSAGES environment variable. The usage message displays the current locale's equivalent of yes and no. Security Restrictions [Tru64 UNIX] In the trusted configuration of the system, all terminal devices have owner set to the login user and group set to the pseu- dogroup tty. The login command sets terminal modes to 0600 at login time, so you must explicitly use mesg y to enable access from unautho- rized users. NOTES
[Tru64 UNIX] If your current locale defines settings other than yes or no, the mesg command does not accept yes or no as arguments. This causes an error if you use a yes or no argument to mesg in your file. EXIT STATUS
The following exit values are returned: Message reception is allowed. Message reception is denied. An error occurred. EXAMPLES
To allow only appropriately authorized users to send messages to your terminal, enter: mesg no To allow everyone the permission to send messages to your terminal, enter: mesg yes To determine the state of message acceptance of your terminal, enter: mesg This will give one of the following responses, as appropriate: is yes is no ENVIRONMENT VARIABLES
The following environment variables affect the execution of mesg: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. FILES
User profile User profile (csh) User profile (csh) Your current terminal SEE ALSO
Commands: chmod(1), csh(1), Bourne shell sh(1b), POSIX shell sh(1p), stty(1), talk(1), wall(1), write(1) Functions: chmod(2) Standards: standards(5) mesg(1)
All times are GMT -4. The time now is 05:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy