Password rules not effective Post: 302728025

Sponsored Content

Special Forums Cybersecurity Password rules not effective Post 302728025 by rbatte1 on Wednesday 7th of November 2012 08:42:24 AM

11-07-2012

Moderator

Password rules not effective

I was looking for a good list of words to exclude people from using as passwords, i.e. those that could be guessed easily. I'm working through a whole bunch of suggestions from skullsecurity.org, but I managed to find this page that seems to suggest I have more options than I thought.

I have a server built at AIX 6.1.3.0, but recently brought up to AIX 6.1.7.5, so I think I qualify, but there have been no changes to /etc/security/user by the update. Smilie

Adding a record in the default: stanza for minloweralpha has no effect. Smilie

Back on quest for a dictionary list, the suggestions on the document are shown for excluding the sequence "123" from a user selected password, but I can't get that to work either. Does anyone have it working and can point out why I am being a fool? Smilie

My personal stanza in /etc/security/user has a dictionlist definition and I can prove that it is effective for excluding specific words, such as password but I'd prefer to craft some woolly rules to exclude our usual suspects like "July2012" etc.

Am I just missing something obvious? I have just installed bos.data from the original media, which has given me a /usr/share/dict/words file full of all sorts of stuff, but they are all explicit exclusions and I still can't get either of the above to work. Smilie

..... and why does : wall : appear as a question box now?

Many apologies and thanks, in advance,

Robin
Liverpool/Blackburn
UK

Last edited by rbatte1; 11-08-2012 at 08:41 AM..

rbatte1

View Public Profile for rbatte1

Visit rbatte1's homepage!

Find all posts by rbatte1

7 More Discussions You Might Find Interesting

1. Cybersecurity

Changing effective user

I would like to give execution rights for a script to one user. (that's the easy part...) When that user is running the script, I would like the effective user ID to be that of the file-owner. Is this possible?

2. UNIX for Dummies Questions & Answers

Variables for Effective Username?

Hey all, I'm glad to have found this forum as I'm trying to dive head first into Solaris 8 - been working with it for a few months now and am finally getting a bit comfortable with the layout and concepts. In any case, on to the questions... :D I was wondering how I would go about displaying...

3. UNIX for Dummies Questions & Answers

most effective search ?

what's the most efficient and effective search for a file in a dir ? I see many guys use this # find - print or something as such ? and sometimes pipe it to something else ? Is there a better way of using "grep" in all of this ? thanks simon2000

4. UNIX for Dummies Questions & Answers

Changing the Effective Group ID

Here is my situation. On a RedHat 7.3 box, I have a user named jody. When I log in with jody and type in "id", I get the expected output: uid=1(jody) gid=1(jody) groups=1(jody), 510(test) However, I cannot figure which "id" option allows me to change the effective gid. I tried the options...

5. UNIX for Dummies Questions & Answers

Server wide password enforcement rules? 90 day force change.

Using Solaris 9 and 10. What we want to do is set up global rules for our password files to restrict all users, not only new ones set up with the rules but also the ones that have been sitting on the system for years. Is there a global way to force all users to change their password every 90...

6. UNIX for Dummies Questions & Answers

rules for new password?

What are the rules for choosing a new password when the old one expires? I notice when I try to use a password that is similar to my previous one then it won't take it. Got me wondering what the exact rules are- as in, how different does it have to be from previous passwords.

7. UNIX for Dummies Questions & Answers

Real and Effective IDs

Can anyone explain me in details of Real and Effective IDs

LEARN ABOUT ULTRIX

auth

auth(5) File Formats Manual auth(5)

Name
auth - auth database

Description
The database is a repository of security-relevant information about each user of the system. This database contains the encrypted password
associated with the user's account in addition to a list of assorted capabilities. The database is stored as an database in the files and
Records are retrieved with the library routine. Access to the database is restricted to the superuser and members of the group

Auth records may be converted to an ASCII representation whose format is:
1000:4KvidFYwovnwp3j8lll78dC1:1920129:3600:2678400:03:0:1000:0:00:00
The first field is the UID of the entry that is used as the key into the database. Then follows:

Encrypted Password
This is the user's encrypted password. Whether this password or the one from the file is actually used is determined by the
security level that the system is running at.

Password Modification Time
This is the time(2) the password was last set.

Minimum Password Lifetime
This is the minimum number of seconds which must elapse between setting passwords.

Maximum Password Lifetime
This is the maximum period of time for which the password will be valid.

Account Mask These are capabilities pertaining to the account itself. They are:

1 A_ENABLE: this account is enabled.
2 A_CHANGE_PASSWORD: The user can change his or her password.
4 A_ENTER_PASSWORD: The user is not required to use machine-generated passwords.

Audit ID Positive integer identifier used in generating audit records for the user.

Audit Control See the reference page, SET_APROC_CNTL section for more information.

Audit Mask Determines which events will be audited for the user. See the and reference pages for more information.

Restrictions
Only the superuser and members of the group may read information from the auth database. Only the superuser may modify the auth database.

Files
See Also
audcntl(2), getauthuid(3), getpwent(3), edauth(8)

auth(5)