svcadm(1M)을 검색하려면 섹션에서 1M 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
crypt_unix(7)
Standards, Environments, Macros, Character Sets, and miscellany
crypt_unix(7)
NAME
crypt_unix - traditional UNIX crypt algorithm
DESCRIPTION
The crypt_unix algorithm is the traditional UNIX crypt algorithm. It is
not considered sufficiently secure for current systems and is provided
for backward compatibility. The crypt_sha512(7), crypt_sha256(7), or
crypt_bsdbf(7) algorithm should be used instead.
The algorithm identifier for policy.conf(5) is __unix__. There is no
entry in crypt.conf(5) for this algorithm.
The crypt_unix algorithm is internal to libc and provides the string
encoding function used by crypt(3C) when the first character of the
salt is not a "$".
This algorithm is based on a one-way encryption algorithm with varia‐
tions intended (among other things) to frustrate use of hardware imple‐
mentations of a key search. Only the first eight characters of the key
passed to crypt() are used with this algorithm; the rest are silently
ignored. The salt is a two-character string chosen from the set [a-zA-
Z0-9./]. This string is used to perturb the hashing algorithm in one of
4096 different ways.
The maximum password length for crypt_unix is 8 characters.
USAGE
The return value of the crypt_unix algorithm might not be portable
among standard-conforming systems. See standards(7).
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitysystem/library _ Interface StabilityCommit‐
ted
SEE ALSO
passwd(1), crypt_gensalt(3C), getpassphrase(3C), crypt(3C), crypt_gen‐
hash_impl(3C), crypt_gensalt_impl(3C), crypt.conf(5), passwd(5), pol‐
icy.conf(5), attributes(7), crypt_bsdbf(7), crypt_sha256(7),
crypt_sha512(7), standards(7)
HISTORY
This algorithm has been included in all releases of SunOS and Solaris.
It was the only algorithm supported by the crypt() function until sup‐
port for pluggable crypt modules was added to Solaris in Solaris 9
12/02 (Update 2). It was the CRYPT_DEFAULT setting in policy.conf
before Solaris 11.0.
Oracle Solaris 11.4 21 Jun 2021 crypt_unix(7)