crypt(3c) [hpux man page]

crypt(3C)																 crypt(3C)

NAME

       crypt  - generate hashing encryption

SYNOPSIS

   Obsolescent Interfaces
DESCRIPTION

   crypt():
       is  the	password encryption function.  It is based on a one way hashing encryption algorithm with variations intended (among other things)
       to frustrate use of hardware implementations of a key search.

       key is a user's typed password.	salt is a two-character string chosen from the set this string is used to perturb the hashing algorithm in
       one of 4096 different ways, after which the password is used as the key to encrypt repeatedly a constant string.  The returned value points
       to the encrypted password.  The first two characters are the salt itself.

   Obsolescent Interfaces
       generate hashing encryption.

WARNINGS

       The return value for points to data whose content is overwritten by each call.

       and are obsolescent interfaces  supported only for compatibility with existing DCE applications. New multithreaded applications should use

SEE ALSO

       crypt(1), login(1), passwd(1), getpass(3C), passwd(4), thread_safety(5).

STANDARDS CONFORMANCE

																	 crypt(3C)

crypt(3C)																 crypt(3C)

NAME

       crypt  - generate hashing encryption

SYNOPSIS

   Obsolescent Interfaces
DESCRIPTION

   crypt():
       is  the	password encryption function.  It is based on a one way hashing encryption algorithm with variations intended (among other things)
       to frustrate use of hardware implementations of a key search.

       key is a user's typed password.	salt is a two-character string chosen from the set this string is used to perturb the hashing algorithm in
       one of 4096 different ways, after which the password is used as the key to encrypt repeatedly a constant string.  The returned value points
       to the encrypted password.  The first two characters are the salt itself.

   Obsolescent Interfaces
       generate hashing encryption.

WARNINGS

       The return value for points to data whose content is overwritten by each call.

       and are obsolescent interfaces  supported only for compatibility with existing DCE applications. New multithreaded applications should use

SEE ALSO

       crypt(1), login(1), passwd(1), getpass(3C), passwd(4), thread_safety(5).

STANDARDS CONFORMANCE

																	 crypt(3C)