12-17-2009
Quote:
Originally Posted by
incredible
1st question to you.. isn't your server 1 checks for password history?
and according to the error messages, your 1st 8 char should have at leasta special char or numeric, which does not match
1. Yes server1 check password history too [HISTORY=3]
2. my password have number "9" at 9th char, but why we can use this password in server1 ??
my password example: ->> abcdeFgh9Jk
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hi all of you..............
I am using openldap on ubuntu server . i want to apply password policy for user's to set password length , expire date , ......etc.
can anybody guide me to configure this. (1 Reply)
Discussion started by: jagnikam
1 Replies
2. Red Hat
Today i was going through some of security guides written on linux .
Under shadow file security following points were mentioned.
1)The encrypted password stored under /etc/shadow file should have more than 14-25 characters.
2)Usernames in shadow file must satisfy to all the same rules as... (14 Replies)
Discussion started by: pinga123
14 Replies
3. Red Hat
Hi,
I am running NIS server on redhat linux 5 and I want to implement password restrictions for the yppasswd, how can I do it.Please help me.
I can implement password restriction for passwd by configuring /etc/pam.d/system-auth and setting crack_lib.so but I don't know how to implent the same... (3 Replies)
Discussion started by: ktrimu
3 Replies
4. Solaris
hi folk,
i try to setup a new password policy for our solaris box user, below are the /etc/default/passwd/, but then when i tried to create a user, it didn't ask for numeric character, and the new password also didn't ask for special characters.
# useradd testing
# passwd testing
New... (7 Replies)
Discussion started by: dehetoxic
7 Replies
5. Ubuntu
Hi linux expert,
i would like to create a script for listing all user with there password policy. It should be in the following format:
Last password change : Sep 19, 2011
Password expires : never
Password inactive : never
Account... (2 Replies)
Discussion started by: yprudent
2 Replies
6. Red Hat
Hi Experts,
i would like to know the description of the following:
Minimum: 0
Maximum: 90
Warning: 7
Inactive: -1
Last Change: Never
Password Expires: Never
Password Inactive: Never
Account Expires: Never
Does this means that... (2 Replies)
Discussion started by: yprudent
2 Replies
7. Solaris
Hello All,
I have Sun DSEE7 (11g) on Solaris 10.
I have run idsconfig and initialized ldap client with profile created using idsconfig.
My ldap authentication works. Here is my pam.conf
# Authentication management
#
# login service (explicit because of pam_dial_auth)
#
login ... (3 Replies)
Discussion started by: pandu345
3 Replies
8. Ubuntu
Hello Team,
I am using Lubuntu & have DRBL remote boot setup with open Ldap authentication. Currently there is no password expire policy. I want to set Password Policy so that user's password will expire after a month & they will get prompt to change their password.
Using PAM we can do it,... (1 Reply)
Discussion started by: paragnehete
1 Replies
9. AIX
I need help. I have set a password policy. But I want to dis allow setting user name as password.
My policy is as below...
min length =8
min diff=2
min alpha=2
max repeats=2
dictionary= /usr/share/dict/words
Still user can set his username as password (i.e. Jackie1234).
Code tags for... (11 Replies)
Discussion started by: powerAIX
11 Replies
10. Red Hat
Hi,
I am unable to enforce password complexity policy for root user. (other users are working) on RHEL 6.2. Anything wrong with system-auth parameters? PLease help..
vi /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time... (1 Reply)
Discussion started by: suresh3566
1 Replies
LEARN ABOUT SUNOS
asadmin-stop-instance
asadmin-stop-instance(1AS) User Commands asadmin-stop-instance(1AS)
NAME
asadmin-stop-instance, stop-instance - stops the specified server instance and all the services associated with it
SYNOPSIS
stop-instance [--user admin_user] [--password admin_password] [--host local_host] [--port 4848] [--local=false] [--domain domain_name]
[--secure|-s]instance_name
Use the stop-instance to stop the instance with the instance name specified. The stop-instance can be run both locally and remotely. The
named instance must already exist within the given domain; and the instance must be running.
OPTIONS
--user administrative user associated for the instance.
--password administrative password corresponding to the administrative user.
--host host name of the machine hosting the administrative instance.
--port administrative port number associated with the administrative host.
--local determines if the command should delegate the request to administrative instance or run locally.
--domain name of the domain.
--passwordfile file containing passwords appropriate for the command (e.g., administrative instance).
--secure if true, uses SSL/TLS to communicate with the administrative instance.
OPERANDS
instance_name name of the instance to be stopped.
Example 1: Using stop-instance in local mode
asadmin> stop-instance --local --domain domain1 server1
Instance server1 stopped
Where: the server1 instance associated with the domain1 domain is stopped locally.
Example 2: Using stop-instance in remote mode
asadmin> stop-instance --user admin --password bluestar --host localhost --port 4848 server1
Instance server1 stopped
Where: the server1 instance associated with the named user, password, host and port is deleted from the remote machine.
EXIT STATUS
0 command executed successfully
1 error in executing the command
INTERFACE EQUIVALENT
Server Instance page
asadmin-delete-instance(1AS), asadmin-start-instance(1AS), asadmin-create-instance(1AS), asadmin-restart-instance(1AS), asadmin-start-
appserv(1AS), asadmin-stop-appserv(1AS), asadmin-start-domain(1AS), asadmin-stop-domain(1AS)
J2EE 1.4 SDK March 2004 asadmin-stop-instance(1AS)