Sponsored Content
Operating Systems Solaris Solaris user Security implementation Post 302278802 by Asteroid on Wednesday 21st of January 2009 07:20:08 AM
Old 01-21-2009
Solaris user Security implementation

Hi gurus,

Need you help here:
How we can implement
  • [1]
    Quote:
    User logout After 15 mins of inactivity.

I have edited /etc/default/login as TIMEOUT=60
But user is not Logged out after 60 sec inactivity. How we can implement this?


  • [2]
    Quote:
    LOGIN should be blocked after Max logins attempts
e.g 3 bad passwords and the user is locked. And it is locked for certain period e.g 20 min.

  • [3]
    Quote:
    Last 10 passwords are unique
    .
The Passwords selected by User must not match his previous passwords (up to last 10 password).
  • [4]
    Quote:
    Password selection must be atleast one char from lower, upper, numeric and special chars.
Password selection is forced to be exactly a regular expression having all above chars.

We have to enforce the security on SUN machine, by implementing above conditions.
Any help will be appriciated.
Thanks and Regards
@Asteroid

[/LIST]
 

8 More Discussions You Might Find Interesting

1. Programming

Solaris Timer Implementation

I've a problem with a Solaris program implementation: My code uses a timer procedure and when i try to execute date -a XXXX or rdate, my aplication stops. I can't use ntp and need to set the machine time. Here is my procedure. If you know how you can help me, please, do it. static void... (2 Replies)
Discussion started by: ulisses0205
2 Replies

2. UNIX for Advanced & Expert Users

User security

Need urgent help!!! Hi, I have an application that runs under a regular unix ID 'prod1'. I want to disable direct login for 'prod1' via ssh or telnet. But I do want some users to be able to su to prod1 and do application maintainence tasks. How can I accomplish that? Also the above scnerio is... (5 Replies)
Discussion started by: sajjad02
5 Replies

3. UNIX for Dummies Questions & Answers

/etc/security/user file in AIX

Dear Gurus, Can the /etc/security/user file be edit manually in AIX. I would like to change the histsize in the default. Currently is set to 0. Please advise whether i can just edit it manually, whether it would cause any harm? thank You Very much. (0 Replies)
Discussion started by: cteoh88
0 Replies

4. UNIX for Dummies Questions & Answers

/etc/security/user two default entries

If there are two default entries in the /etc/security/user file, which settings are effective, the first one or the second one? For example: would maxage 0 or 12 be effective? default: loginretries = 0 histexpire = 0 histsize = 0 minage = 0 maxage = 0 maxexpired = -1 default:... (1 Reply)
Discussion started by: Dan2
1 Replies

5. UNIX for Advanced & Expert Users

any reason for a user without a homedir - security/config/application?

Hi, Can I just quick pick everyone brain here about the following: There is a security audit going on at the company I work for and one of the things that needed to be resolved was that there were a lot of users who don't have a home directory. As this is a fairly large environment of over... (5 Replies)
Discussion started by: Solarius
5 Replies

6. AIX

Security user Can't change the groups.

Dears Security users in AIX don’t have permission to change the group of the user thru Smitty Users When they try to change the group of the users to any group they'll get permission denied Security profile in Smitty : User... (10 Replies)
Discussion started by: ITHelper
10 Replies

7. UNIX for Dummies Questions & Answers

Pop the users one by one in sudo cat /etc/security/user

Hi Everyone, When I runthe query in ssh shell sudo cat /etc/security/user , I see half of the users cut down from the display screen. what I want to do is using the somthing like "pop" that when I hit the enter key every time the screen should move to the next user? does some one has any idea how... (4 Replies)
Discussion started by: starter2011
4 Replies

8. Cybersecurity

Stream Content Security with user:pass

Hello, I have a linux based streaming server and I do not want to make it public. I am looking for a solution to make my streaming content secured with username & password for each individual. If i had been dealing with a webpage application, it would have been easy for me: To create .htpasswd... (5 Replies)
Discussion started by: baris35
5 Replies
SHADOW(5)                                                  File Formats and Conversions                                                  SHADOW(5)

NAME
shadow - shadowed password file DESCRIPTION
shadow is a file which contains the password information for the system's accounts and optional aging information. This file must not be readable by regular users if password security is to be maintained. Each line of this file contains 9 fields, separated by colons (":"), in the following order: login name It must be a valid account name, which exist on the system. encrypted password Refer to crypt(3) for details on how this string is interpreted. If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, the user will not be able to use a unix password to log in (but the user may log in the system by other means). This field may be empty, in which case no passwords are required to authenticate as the specified login name. However, some applications which read the /etc/shadow file may decide not to permit any access at all if the password field is empty. A password field which starts with an exclamation mark means that the password is locked. The remaining characters on the line represent the password field before the password was locked. date of last password change The date of the last password change, expressed as the number of days since Jan 1, 1970. The value 0 has a special meaning, which is that the user should change her password the next time she will log in the system. An empty field means that password aging features are disabled. minimum password age The minimum password age is the number of days the user will have to wait before she will be allowed to change her password again. An empty field and value 0 mean that there are no minimum password age. maximum password age The maximum password age is the number of days after which the user will have to change her password. After this number of days is elapsed, the password may still be valid. The user should be asked to change her password the next time she will log in. An empty field means that there are no maximum password age, no password warning period, and no password inactivity period (see below). If the maximum password age is lower than the minimum password age, the user cannot change her password. password warning period The number of days before a password is going to expire (see the maximum password age above) during which the user should be warned. An empty field and value 0 mean that there are no password warning period. password inactivity period The number of days after a password has expired (see the maximum password age above) during which the password should still be accepted (and the user should update her password during the next login). After expiration of the password and this expiration period is elapsed, no login is possible using the current user's password. The user should contact her administrator. An empty field means that there are no enforcement of an inactivity period. account expiration date The date of expiration of the account, expressed as the number of days since Jan 1, 1970. Note that an account expiration differs from a password expiration. In case of an account expiration, the user shall not be allowed to login. In case of a password expiration, the user is not allowed to login using her password. An empty field means that the account will never expire. The value 0 should not be used as it is interpreted as either an account with no expiration, or as an expiration on Jan 1, 1970. reserved field This field is reserved for future use. FILES
/etc/passwd User account information. /etc/shadow Secure user account information. /etc/shadow- Backup file for /etc/shadow. Note that this file is used by the tools of the shadow toolsuite, but not by all user and password management tools. SEE ALSO
chage(1), login(1), passwd(1), passwd(5), pwck(8), pwconv(8), pwunconv(8), su(1), sulogin(8). shadow-utils 4.5 01/25/2018 SHADOW(5)
All times are GMT -4. The time now is 02:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy