Why use strong passwords?

2 More Discussions You Might Find Interesting

1. 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...

2. Shell Programming and Scripting

Strong quotes and spaces

We ran into a problem because of a shop that uses Windows and UNIX. The file names that Windows uses have spaces in them. When they get moved to the unix system they still have spaces. This produces a problem in our script that moves them again from one unix system to another. I've made up a...

LEARN ABOUT HPUX

pwd_strengthd

pwd_strengthd(1m)														 pwd_strengthd(1m)

NAME

       pwd_strengthd - The sample Password Management Server

SYNOPSIS

       pwd_strengthd [+/-all[_spaces]] [+/-alp[ha_num]]
       [-c[ache_size]] size [-d[ebug]]
       [-m[in_len]] pwd_min_len [-t[imeout]] minutes
       [-v[erbose]]

OPTIONS

       Allow  passwords  to be all spaces. If this option is not set, the effective registry policy is used.  Disallow passwords to be all spaces.
       If this option is not set, the effective registry policy is used.  Allow passwords to consist only  of  alphanumeric  characters.  If  this
       option is not set, the effective registry policy is used.  Disallow passwords to consist only of alphanumeric characters. If this option is
       not set, the effective registry policy is used.	Specify the number of hash buckets in the password cache. The password cache  is  used	to
       store  generated passwords which are retrieved when the password is strength checked. The password cache is a hash table with a linked list
       for collisions. The size should be set to a reasonable value based on how large the cache will be on average.  The  default  value  if  not
       specified  is  100.  Run in the foreground. Log messages are written to standard output.  Specify the minimum length of a password. If this
       option is not set, the effective registry policy is used.  Specify the time, in minutes, that  generated  passwords  remain  in	the  cache
       before  they are deleted from memory. If this option is not specified, the default time is 30 minutes.  Runs in verbose mode. More detailed
       messages are sent to the logfile $DCELOCAL/var/security/pwd_strengthd.log.  (Use of this option is recommended.)

DESCRIPTION

       DESCRIPTION

       pwd_strengthd is a sample Password Management Server. It exports the rsec_pwd_mgmt application programming interface.

       pwd_strengthd generates passwords and strength-checks them. It enforces	the  security  registry  policy  for  password	strength-checking.
       Administrators can override the security registry policy via the command-line options (alpha_num, all_spaces, min_len.)

       Administrators can subject principals to password-strength and -generation policies by attaching the following ERAs: Specifies the password
       management policy the user must conform to when selecting passwords.  Specifies information required in order to connect  to  the  password
       management server.

       See the OSF DCE Administrator's Guide -- Core Services for more information and examples.  You may want to enhance pwd_strengthd to support
       your site's policies for password strength and generation.

																 pwd_strengthd(1m)

Cybersecurity