Sponsored Content
Operating Systems Solaris Encrypting or maksing password in cron Post 302909660 by Peasant on Friday 18th of July 2014 06:24:40 AM
Old 07-18-2014
You cannot stop root user of being root.

If you have password in file on the server in question, the administrator will know it, possibly other users based on file permissions.

I would recommend using other auth mechanisms for your application (like Kerberos or alike) *AND* having some sort of auditing on the application side in database, so if shit hits the fan, you will know who started it based on audit logs.

On Solaris you might configure auditing for a certain call or script execution which will notify who started what in which time. I am unfamiliar with AIX in this regard, but i'm sure there are similar auditing methods on IBM.

You should also take into consideration that auditing can be very intensive on machines and databases, depending on the depth of auditing.

Hope that helps
Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

encrypting Unix flatfile

Hi, I am new to unix. I have a flat file that needs to be pgp encyrpted in ASCII format and ftped in Ascii format to remote location. Can any one tell me the steps involved in the pgp encryption of the unix file. I will really appreciate if any one can help me with the pgp encryption shell... (1 Reply)
Discussion started by: rkumar28
1 Replies

2. Shell Programming and Scripting

Encrypting a password for shell script

All, I want to encrypt a database system administration password into a file or environment variable. Then, I want to decrypt the password from the file or environment variable so nobody sees the clear text password. For example, I have the database password of developement. I need to... (1 Reply)
Discussion started by: bubba112557
1 Replies

3. AIX

Encrypting password

I have a strange question for someone regarding the AIX 5.2 environment. Here is the scenerio: I have a script that is running a menu full of options. 1. I like food 2. I don't like food Enter Option:_ Enter userID:_ Enter Password:_ (The menu is conversational only so go with me on... (6 Replies)
Discussion started by: Justman
6 Replies

4. UNIX for Advanced & Expert Users

encrypting files in ksh

I have an ascii file that I want to encrypt and save. I have seen this done before, but cannot remember how, nor can I find anything in any of my manuals or online help. Any ideas how to do this? Thanks, Henry (6 Replies)
Discussion started by: hwollman53
6 Replies

5. Solaris

Encrypting a script......

Hiiiiii..... every one..... I have written a script, and i want to make that script confidential.So that, only i can see that script. I am using " crypt " command in solaris 9, to encrypt that script.But when i am executing this... (6 Replies)
Discussion started by: prashantshukla
6 Replies

6. Shell Programming and Scripting

Encrypting the login password on Solaris 10

Hi, Could you pls. help me in encryting a database password on Solaris 10 Box. eg : username : test password : t est123 The request is to encrypt the test123 so that no one can understand the what the password is ? thanks (7 Replies)
Discussion started by: krackjack
7 Replies

7. Shell Programming and Scripting

Encrypting the password

Iam using the teradata... and running the scripts in unix, I wan to encrypt the teradata password in Unix... my hostname is : bprod usename: KRN777 passwrd: passwrd can ant one tell me the exact command to encrypth the passwrd.... thanks, (5 Replies)
Discussion started by: nani1984
5 Replies

8. Shell Programming and Scripting

Encrypting password

Hello All, I need to accept a password from the user and validate it, without having to hard-code it anywhere. Any ideas? (3 Replies)
Discussion started by: optimus_1
3 Replies

9. Shell Programming and Scripting

Help needed regarding cron job scheduler with CyberArk Password security

Hi All, I have a script which will restart some web server and bring it up again. For that I need to retrieve 3 password from CyberArk (Cyber-Ark - Wikipedia, the free encyclopedia) vault. My question is: Is this possible to schedule the script through cron and automatic password... (0 Replies)
Discussion started by: saps19
0 Replies

10. High Performance Computing

Encrypting interconnect

Hi, i've got a qusetion regarding interconnect of compute nodes. In our company we are running a Simulation Cluster which is administrated by the Simulation department. Now our central IT requires to encrypt the interconnect of the compute nodes. Does anybody in that business encrypt... (3 Replies)
Discussion started by: fiberkill
3 Replies
audctl(2)							System Calls Manual							 audctl(2)

NAME
audctl() - start or halt the auditing system and set or get audit files SYNOPSIS
Remarks This function is provided purely for backward compatibility. HP recommends that new applications use the command to configure the auditing system. See audsys(1M). DESCRIPTION
sets or gets the auditing system "current" and "next" audit files, and starts or halts the auditing system. This call is restricted to processes with the privilege. cpath and npath hold the absolute path names of the "current" and "next" files. mode specifies the audit file's permission bits. cmd is one of the following specifications: The caller issues the command with the required "current" and "next" files to turn on the auditing system. If the auditing system is cur- rently off, it is turned on; the file specified by the cpath parameter is used as the "current" audit file, and the file specified by the npath parameter is used as the "next" audit file. If the audit files do not already exist, they are created with the mode specified. The auditing system then begins writing to the specified "current" file. An empty string or NULL npath can be specified if the caller wants to designate that no "next" file be available to the auditing system. If the auditing system is already on, no action is performed; is returned and is set to The caller issues the command to retrieve the names of the "current" and "next" audit files. If the auditing system is on, the names of the "current" and "next" audit files are returned via the cpath and npath parameters (which must point to character buffers of sufficient size to hold the file names). mode is ignored. If the auditing system is on and there is no available "next" file, the "current" audit file name is returned via the cpath parameter, npath is set to an empty string; is returned, and is set to If the auditing system is off, no action is performed; is returned and is set to The caller issues the command to change both the "current" and "next" files. If the audit system is on, the file specified by cpath is used as the "current" audit file, and the file specified by npath is used as the "next" audit file. If the audit files do not already exist, they are created with the specified mode. The auditing system begins writing to the specified "current" file. Either an empty string or NULL npath can be specified if the caller wants to designate that no "next" file be available to the auditing system. If the auditing system is off, no action is performed; is returned and is set to The caller issues the command to change only the "current" audit file. If the audit system is on, the file specified by cpath is used as the "current" audit file. If the specified "current" audit file does not exist, it is created with the specified mode. npath is ignored. The auditing system begins writing to the specified "current" file. If the audit system is off, no action is performed; is returned and is set to The caller issues the command to change only the "next" audit file. If the auditing system is on, the file specified by npath is used as the "next" audit file. cpath is ignored. If the "next" audit file specified does not exist, it is created with the specified mode. Either an empty string or npath can be specified if the caller wants to designate that no "next" file be available to the auditing system. If the auditing system is off, no action is performed; is returned, and is set to The caller issues the command to cause the auditing system to switch audit files. If the auditing system is on, it uses the "next" file as the new "current" audit file and sets the new "next" audit file to cpath, npath,and mode are ignored. The auditing system begins writing to the new "current" file. If the auditing system is off, no action is performed; is returned, and is set to If the auditing system is on and there is no available "next" file, no action is performed; is returned, and is set to The caller issues the command to halt the auditing system. If the auditing system is on, it is turned off and the "current" and "next" audit files are closed. cpath, npath, and mode are ignored. If the audit system is already off, is returned and is set to Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
Upon successful completion, a value of is returned. Otherwise, is returned and the global variable is set to indicate the error. EXAMPLES
In the following example, is used to determine whether the auditing system is on, and to retrieve the names of the audit files that are currently in use by the system. char c_file[PATH_MAX+1], x_file[PATH_MAX+1]; int mode=0600; if (audctl(AUD_GET, c_file, x_file, mode)) switch ( errno ) { case ENOENT: strcpy(x_file,"-none-"); break; case EALREADY: printf("The auditing system is OFF "); return 0; case default: fprintf(stderr, "Audctl failed: errno=%d ", errno); return 1; } printf("The auditing system is ON: c_file=%s x_file=%s ", c_file, x_file); return 0; ERRORS
fails if one of the following is true: The caller does not have the privilege, or one or both of the given files are not regular files and cannot be used. The or cmd was specified while the auditing system is off. User attempt to start the auditing system failed because auditing is already on. Bad pointer. One or more of the required function parameters is not accessible. The cpath or npath is greater than in length, the cpath or npath specified is not an absolute path name. No available "next" file when cmd is or AUTHOR
was developed by HP. SEE ALSO
audomon(1M), audsys(1M), audit(5), privileges(5). TO BE OBSOLETED audctl(2)
All times are GMT -4. The time now is 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy