Sponsored Content
Top Forums Shell Programming and Scripting How to store the passwords securely and use in scripts? Post 303034031 by Neo on Wednesday 17th of April 2019 12:04:32 AM
Old 04-17-2019
The approach to manage risk in IT should be based on a risk analysis.

For example, a person running their own blog who has not much to lose if their DB password is compromised has a much different risk profile than a bank doing financial transactions.

Security controls come with "costs" and so the controls used should be appropriate to the risk profile of the system.

All WordPress blocks, Wikipedia Wikis and indeed most all CMS apps freely available on the network store DB password as clear text in config files which with various standard unix / linux file system permissions and controls.
These 2 Users Gave Thanks to Neo For This Post:
 

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
prpwd(4)						     Kernel Interfaces Manual							  prpwd(4)

NAME
prpwd - protected password authentication database files used for trusted systems SYNOPSIS
DESCRIPTION
An authentication profile is maintained for each user on the system. A user profile is kept in a protected password database file that is accessible only to the System Administrator. The protected password database files contain among other things the encrypted password for the user account. On a trusted system, the passwords are hidden from normal users. The protected password database files do not obviate the need for the and the files. Users must be defined in the file in order to use the system. The protected password database file for a user contains the user name and user id to provide a correlation to the user's entry. These must match or the user account will be treated as invalid. Protected password database files are maintained in the hierarchy. This directory contains other directories each named with a single let- ter from the alphabet. User authentication profiles are stored in these directories based on the first letter of the user account name. This enables an efficient search operation to locate the file for a specific user name. For instance, the authentication profile for the account is located in the directory and can be accessed by opening the file Fields defined in a file are user specific values. These values override the system default values. Trusted programs check first for the existence of user specific parameters before using a system default value. A protected password database file contains keyword field identifiers and, depending on the field type, a value for that field (certain field types do not require an explicit value). The exact syntax for field specifications is described in authcap(4). Field specification is consistent for all system authentication databases. The keyword field identifiers supported by the protected password database file and their associated function are given in the following descriptions: This is the user name for the account which must match the name of the file and the user name from the corresponding entry. This is the user ID for the account which must match the user id field of the corresponding entry. This field contains the encrypted password for the account if the account has a password. This field contains the owner of the account. If this field exists and contains a value greater than zero (typically 1), and the boot authenticate flag is set in the system default file, then this user has authority to boot the system. If the boot authenticate flag is not set in the system default file then this field is not used. This field contains the audit ID for the user. This field contains the audit flag for the user. This field specifies the minimum password change time in seconds. If non-zero, the password cannot be changed until the specified number of seconds since the last successful password change have passed unless the person changing the password is authorized to override this constraint. This field specifies the maximum length for system-generated passwords. It should be less than the system-wide maximum value defined by the constant This field is a time_t value that specifies when the account password will expire. When a password expires, system authentication pro- grams will request that the password be changed when the user logs into the system. If the password lifetime expires before the password is changed, the account will be locked. This field is a time_t value that specifies the lifetime of a password. If this time is reached, the account will be locked and can only be unlocked by an authorized system administrator. This field is a time_t value that indicates the time of the last successful password change. This field should only be set by programs that can be used to change the account password. This field is a time_t value that indicates the time of the last unsuccessful password change. This field should only be set by programs that can be used to change the account password. This field is the time_t time in seconds that the account will be usable. After this time interval the user will no longer be allowed to login. This field is different from the field in that the field is the time from the last password change. is not affected by the changing of the password. This value, in seconds, is the maximum time allowed between logins. If the time between the last login and the current time exceeds this value, the account is locked and the user can no longer logon. This value, in seconds, is the time at which a warning will appear prior to the expiration of the user's password. This value is a flag that controls the ability of the user to pick a password for the account. This permits an account to be configured so that a user can not pick a password but instead has a pass- word generated by the system for the account. This flag field controls the ability of a user to generate a password for the account. The system is capable of generating passwords containing random letters, characters, or words. This flag field controls whether password triviality checks are performed on any user chosen passwords. Triviality checks performed include verifying that the password does not represent a login or group name, a palindrome, or a word recognized by the spell(1) program. This flag controls the ability of the user to choose a null password for the account. This field records the user id of the last person to change the account password if that user was not the same as the account's user. This is used to warn the user at login time if the account password has been changed possibly without the knowledge of the user. This field holds the random number the user must supply to login after the account is reset by the system administrator. This field is removed after a successful login. This flag field controls the ability of the user to generate random characters for a password. This flag field controls the ability of the user to generate random letters for a password. This field contains a comma separated list of time-of-day specification entries that controls when the user account can be used for login. This field is a time_t value that contains the system time of the last successful login to the account. This field is a time_t value that contains the system time of the last unsuccessful login to the account. This field is a character string that identifies the name of the terminal or remote host associated with the last successful login to the account. A remote host specification consists of the ASCII representation of the Internet address of the host. This field is con- verted into an Internet address and is converted to a hostname using gethostbyaddr(3). This field contains a count of the number of unsuccessful login attempts to the account. This field is reset when a successful login to the account occurs. This field is a character string that identifies the name of the terminal or remote host associated with the last unsuccessful login attempt to the account. This field specifies the maximum number of consecutive unsuccessful login attempts to the account that are permitted until the account is locked. This flag field is used to administratively lock an account. A user cannot login to a locked account. Notes The getprpwent(3) routines are used to parse the protected password database files into a structure that can used by programs. A flag in the structure indicates whether a particular field in the structure and hence the field is defined. System default values are also pro- vided in the structure. These values are derived from the field and can be used by programs in the absence of a user specific value. EXAMPLES
The following is an example of a typical protected password database file: perry:u_name=perry:u_id#101: :u_pwd=aZXtu1kmSpEzm: :u_minchg#0:u_succhg#653793862:u_unsucchg#622581606:u_nullpw: :u_suclog#671996425:u_suctty=tty1: :u_unsuclog#660768767:u_unsuctty=tty1: :u_maxtries#3:chkent: This protected password database file is for the user The user ID for is 101. This value must match the entry for this user. The account has a password and its encrypted form is specified by the field. The database file specifies a minimum password change time of 0, indicating the password can be changed at any time. Furthermore, the account is permitted to have a null password The account has a maximum consecutive unsuccessful login threshold of 3 attempts indicating that the account will be locked after three failed attempts The remaining fields provide account information such as the last successful and unsuccessful password change times as well as the last successful and unsuccessful login times and terminal names. WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. AUTHOR
was developed by HP. SEE ALSO
login(1), users(1), getprpwent(3), authcap(4), default(4). TO BE OBSOLETED prpwd(4)
All times are GMT -4. The time now is 06:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy