marlah
asked on
masking script argument passing
I have a commercial package that uses a script to initiate a resident process to set up an interface to a database. This script passes database information (like SID to use for login) as arguments to this process, which all arguments are clearly visible when you do a ps.
The user implementing this script needs more than one instance of this process running, and to do this he also has to additionally supply id and password information as arguments to this program. This is terribly insecure since anyone who manages to do a ps can see the password. Can anyone suggest a way to hide this information without having to muck about in the commercial package's programming (since I am not a programmer and don't have access to their source)?
The user implementing this script needs more than one instance of this process running, and to do this he also has to additionally supply id and password information as arguments to this program. This is terribly insecure since anyone who manages to do a ps can see the password. Can anyone suggest a way to hide this information without having to muck about in the commercial package's programming (since I am not a programmer and don't have access to their source)?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER