| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is based on Ulrich Drepper's implementation in GLIBC, but hacked up to work
in uClibc. The differences from the GLIBC version are as follows:
- b64_from_24bit() has been converted into a macro
- Usage of GLIBC-isms (such as libc_freeres_ptr) have been removed
It is enabled by the UCLIBC_HAS_SHA256_CRYPT_IMPL configuration symbol. You must
have UCLIBC_HAS_CRYPT_IMPL enabled as well.
Signed-off-by: William Pitcock <nenolod@dereferenced.org>
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
(cherry picked from commit 3ac5fd7ecaeb6721d812c2b93e446bf9a31acdde)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is based on Ulrich Drepper's implementation in GLIBC, but hacked up to work
in uClibc. The differences from the GLIBC version are as follows:
- b64_from_24bit() has been converted into a macro
- Usage of GLIBC-isms (such as libc_freeres_ptr) have been removed
It is enabled by the UCLIBC_HAS_SHA512_CRYPT_IMPL configuration symbol. You must
have UCLIBC_HAS_CRYPT_IMPL enabled as well.
Signed-off-by: William Pitcock <nenolod@dereferenced.org>
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
(cherry picked from commit 4c24dabb9cea4c8148d7a7efc7a1df694424c483)
|
|
|
|
|
|
|
|
|
| |
By using a function table, we can more cleanly support new crypt
implementations, such as SHA256 ($5$) and SHA512 ($6$).
Signed-off-by: William Pitcock <nenolod@dereferenced.org>
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
(cherry picked from commit 40c426ae8f032d794d15f4a7fca8dc17cdc9899d)
|
|
|
|
|
| |
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
(cherry picked from commit 4a2b0641a3818ad14b886907368b6f6735615f6d)
|
| |
|
|
|
|
| |
I had clearly run search/replace on that were cluttering things up.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(IEEE Std 1003.1-2001) states that crypt need not be reentrant.
-Erik
|
|
|
|
|
|
|
| |
DES validation suite. setkey_r, encrypt_r, and __des_crypt_r are not really
reentrant now, and that should be fixed (or we should drop crypt_r and friends
which are not supported by SuSv3).
-Erik
|
| |
|
|
|
|
|
| |
static to avoid symbol leakage.
-Erik
|
| |
|
|
-Erik
|