Sponsored Content
Top Forums Shell Programming and Scripting How to store the passwords securely and use in scripts? Post 303034324 by RavinderSingh13 on Tuesday 23rd of April 2019 09:40:47 AM
Old 04-23-2019
Quote:
Originally Posted by rbatte1
Okay, so it's DB2. I think that it is usual for all DB2 users to actually be OS users and you might just need to set up the trust there. You might need to use sudo to run the processes as the nominated OS user that can connect to the database and do the work.

Can you force that through? make sure your sudo rules only allow them to run a specific script as the trusted account that means they can only do what you want, not just a general "Connect me to the database and wheeeee....."
Also, do not allow them to get to the shell prompt as the trusted account else they can probably bypass any rules you want to define. Basically, don't trust them to do anything at all except a very controlled script.

If this is for end users, then you might need to set the sudo rules to use NOPASSWD to permit them without prompting for their own password all the time.
I hope that this helps,
Robin
Thanks Robin for sharing it. Sudo with nonpasswd is really good idea. To be honest I myself did 1 automation few backs only with using this and this facility is cool and safe too.

Thanks,
R. Singh
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to pass passwords to bash scripts?

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)
Discussion started by: siegfried
5 Replies

2. Shell Programming and Scripting

Checking passwords - scripts

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)
Discussion started by: bullz26
5 Replies

3. Solaris

installing solaris securely

Ok, I am trying to install solaris, but I would like as a lean installation as possible (while still having a shread of functionality). If I chose the minimal install I have little if no utilities to do work on the box. My question is what installation method do most admins take? ... (7 Replies)
Discussion started by: liven
7 Replies

4. Shell Programming and Scripting

Oracle Passwords in Unix scripts

Hi Most of the shell scripts I am dealing with have to connect to oracle database . The username password is stored in a environment file which sets the variables for username and password . Set user id do not work on AIX so users who will execute these scripts need to have read or execute... (5 Replies)
Discussion started by: clifford
5 Replies

5. Shell Programming and Scripting

SSH - Passing Unix login passwords through shell scripts

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)
Discussion started by: koti_rama
3 Replies

6. UNIX for Advanced & Expert Users

When did UNIX start using encrypted passwords, and not displaying passwords when you type them in?

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)
Discussion started by: Anne Neville
5 Replies

7. AIX

When did AIX start using /etc/security/passwd instead of /etc/passwd to store encrypted passwords?

Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords? (1 Reply)
Discussion started by: Anne Neville
1 Replies

8. UNIX for Advanced & Expert Users

Store passwords , accounts, IPs, hostnames

Hi, this question is not specially unix related, but I expect advanced and expert unix users to have a solution for this, and I've found no other subforum that fits ;) what do you use to store accounts, customer ids, ip addresses, users and specially passwords, to access them from... (6 Replies)
Discussion started by: funksen
6 Replies
pam_unix(5)							File Formats Manual						       pam_unix(5)

NAME
pam_unix - authentication, account, session, and password management PAM modules for UNIX SYNOPSIS
DESCRIPTION
The UNIX service module for PAM, provides functionality for all four PAM modules: authentication, account management, session management and password management. The module is a shared object that can be dynamically loaded to provide the necessary functionality upon demand. For an interpretation of the module path, please refer to the related information in pam.conf(4). Unix Authentication Module The UNIX authentication component provides functions to verify the identity of a user, and to set user specific credentials compares the user entered password (or password retrieved from the user's smart card) with the password from UNIX password database, including the protected password database for trusted systems. If the passwords match, the user is authenticated. If the user also has secure RPC credentials and the secure RPC password is the same as the UNIX password, then the secure RPC credentials are also obtained. The following options may be passed to the UNIX service module: syslog(3C) debugging information at level. Turn off warning messages. It compares the password in the password database with the user's initial password (entered when the user authenticated to the first authentication module in the stack). If the passwords do not match, or if no password has been entered, quit and do not prompt the user for a password. This option should only be used if the authentication service is designated as optional in the configuration file. It compares the password in the password database with the user's initial password (entered when the user authenticated to the first authentication module in the stack). If the passwords do not match, or if no password has been entered, prompt the user for a password. psd stands for personal security device, for the current implementation there is only one security device: the smart card. It compares the password in the password database with the password stored on the user's smart card. With this option the PAM Framework prompt "Enter PIN:" is used instead of the password prompt. This option is only supported with the authentication or password module types (auth, password) services in the or in the configuration files. When prompting for the current password, the UNIX authentication module will use the prompt, "Password:" unless one of the following sce- narios occur: 1. The option is specified and the password entered for the first module in the stack fails for the UNIX module. 2. The option is not specified, and the earlier authentication modules listed in the file have prompted the user for the pass- word. 3. The option is specified. In this case, the UNIX authentication module will use the prompt "Enter PIN:". In cases 1 and 2, the UNIX authentication module will use the prompt "System Password:". The function sets user specific credentials. If the user had secure RPC credentials, but the secure RPC password was not the same as the UNIX password, then a warning message is printed. If the user wants to get secure RPC credentials, then keylogin(1) needs to be run. Unix Account Management Module The UNIX account management component provides a function to perform account management The function retrieves the user's password entry from the UNIX password database and verifies that the user's account and password have not expired. For trusted systems, this module also validates the allowed access time and access terminal based upon the security configuration. The following options may be passed in to the UNIX service module: syslog(3C) debugging information at level. Turn off warning messages. Unix Session Management Module The UNIX session management component provides functions to initiate and terminate UNIX sessions. For UNIX, updates the last successful or unsuccessful login time in the protected password database for trusted mode. The account management module reads the information to dis- play the previous time the user logged in. The following options may be passed in to the UNIX service module: syslog(3C) debugging information at level. Turn off warning messages. is a NULL function. Unix Password Management Module The UNIX password management component provides a function to change passwords in the UNIX password database. This module must be in It can not be or The following options may be passed in to the UNIX service module: syslog(3C) debugging information at level. Turn off warning messages. It compares the password in the password database with the user's old password (entered to the first password module in the stack). If the passwords do not match, or if no password has been entered, quit and do not prompt the user for the old password. It also attempts to use the new password (entered to the first password module in the stack) as the new password for this module. If the new password fails, quit and do not prompt the user for a new password. It compares the password in the password database with the user's old password (entered to the first password module in the stack). If the passwords do not match, or if no password has been entered, prompt the user for the old password. It also attempts to use the new password (entered to the first password module in the stack) as the new password for this module. If the new password fails, prompt the user for a new password. It prompts the user for the PIN (with the PIN, the PAM Framework can retrieve a password from the smart card) and the old password is retrieved from the smart card. It compares the password in the password database with the user's old password. If the passwords match, it prompts the user for a new password. If the user's password has expired, the UNIX account module saves this information in the authentication handle using The UNIX password module retrieves this information from the authentication handle using to determine whether or not to force the user to update their pass- word. APPLICATION USAGE
On trusted systems, the interfaces implemented in the UNIX service module, are not thread-safe. Otherwise, they are thread-safe. A can- cellation point may occur while a thread is executing any of these interfaces. They are not cancel-safe, async-cancel-safe, nor async-sig- nal-safe. WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. SEE ALSO
keylogin(1), pam(3), pam_authenticate(3), pam_setcred(3), syslog(3C), nsswitch.conf(4), pam.conf(4), pam_user.conf(4). pam_unix(5)
All times are GMT -4. The time now is 11:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy