Your IP : 216.73.216.86
ChangeLog 0000644 00000013641 15170773332 0006333 0 ustar 00 2018-01-27 Zack Weinberg <zackw@panix.com>
* Version 4.0.0 released.
* This project no longer maintains a GNU-style ChangeLog file.
See the Git commit history for detailed changes since 3.1.1.
2015-05-13 Björn Esser <besser82@fedoraproject.org>
* release version 3.1.1
* README.bcrypt: whitespace clean-up
* src/crypt-private.h
* configure.ac: add '--enable-Wno-cast-align' to silence 'cast
increases required alignment'
2015-05-12 Björn Esser <besser82@fedoraproject.org>
* release version 3.1.0
* configure.ac: update upstream-contact
* configure.ac: add './configure --enable-bootstrap' to skip some
tests on initial build
* src/Makefile.am
* bootstrap.sh: add bootstrap-script
* LICENSE.bcrypt: add LICENSE for bcrypt
* Makefile.am
* plugins/blowfish/Makefile.am: update crypt_blowfish to v1.3
* plugins/blowfish/blowfish-test.c
* plugins/blowfish/crypt_blowfish.c
* plugins/blowfish/crypt_blowfish.h
* plugins/blowfish/ow-crypt.h
* configure.ac: add '-Wextra' to CFLAGS
* plugins/md5/md5.c: fix '-Werror=strict-aliasing'
* plugins/sha256/sha256.c
* plugins/sha512/sha512.c
* src/cert.c: fix '-Werror=unused-result'
* configure.in --> configure.ac: update Autotools
* Makefile.am
* m4/
* plugins/blowfish/Makefile.am
* plugins/md5/Makefile.am
* plugins/sha256/Makefile.am
* plugins/sha512/Makefile.am
* src/Makefile.am
2011-05-10 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.4
* src/cert.c (get8): Don't save return value we never use.
2009-10-29 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.3
* src/xcrypt.c (__xcrypt_gensalt_r): Fix memory leak [bnc#547893].
2008-11-04 Thorsten Kukuk <kukuk@suse.de>
* plugins/blowfish/blowfish-test.c (run): Fix compiler
warnings [bnc#440134].
2008-09-28 Thorsten Kukuk <kukuk@suse.de>
* src/xcrypt-private.h: Add prototype for _xcrypt_gensalt_sha256_rn
and _xcrypt_gensalt_sha512_rn.
* src/crypt_gensalt.c: Add new gensalt functions.
* src/xcrypt.c: Use gensalt functions for sha512 and sha256.
* src/gensalt-test.c: Enable test cases for sha256 and sha512.
2008-07-16 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.2
* src/xcrypt.c (__xcrypt_gensalt_r): Handle special
MD5 case.
* src/gensalt-test.c: New test case.
* src/Makefile.am: Add gensalt-test as new test case.
2008-06-24 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.1
* plugins/md5/md5.c: Fix undefined macros.
* plugins/sha256/sha256.c: Likewise.
* plugins/sha512/sha512.c: Likewise.
2008-02-15 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0
* plugins/*: Move all crypt releated code into plugins.
* plugins/sha256: New, $5$ aka sha256 hash.
* plugins/sha512: New, $6$ aka sha512 hash.
* src/sha.c: Removed.
* src/sha-crypt.c: Likewise.
* src/xcrypt.h: Add __nonnull.
* src/crypt_util.c: Sync with glibc 2.7.
* src/xcrypt.c: Load all hashes except DES dynamic.
* src/Makefile.am: increase version of shared library.
2006-01-06 Thorsten Kukuk <kukuk@suse.de>
* release version 2.4
* src/Makefile.am: Bump minor version number
* src/crypt_gensalt.c: Sync with crypt_blowfish 1.0.
2005-09-18 Thorsten Kukuk <kukuk@suse.de>
* release version 2.3
* src/x86.S: Remove.
* src/crypt_blowfish.c: Don't use ASM on x86.
2004-06-18 Thorsten Kukuk <kukuk@suse.de>
* release version 2.2
* src/md5-crypt.c (__md5_crypt): Check if realloc
runs out of memory (from glibc CVS).
* configure.in: Remove --noexecstack flag (compiler
can do it better itself).
2003-11-14 Thorsten Kukuk <kukuk@suse.de>
* configure.in: Check for --noexecstack support
2003-10-16 Thorsten Kukuk <kukuk@suse.de>
* release version 2.1
* COPYING: Add all different copyrights.
* src/x86.S: Added, optimized, thread safe version for ix86.
* src/crypt_blowfish.c: Use optimized assember functions on ix86.
* libxcrypt.spec: New.
2003-07-28 Thorsten Kukuk <kukuk@suse.de>
* release version 2.0
* src/crypt_util.c: Include xcrypt-private.h only, add weak aliases.
* src/wrapper.c: Likewise.
* src/crypt_gensalt.c: Rename _crypt_* to _xcrypt_*
* src/crypt_blowfish.c: Likewise.
* src/crypt-entry.c: Include xcrypt-private.h.
* src/crypt.c: Only include xcrypt-private.h.
* src/xcrypt-private.h: Include xcrypt.h, undef xcrypt defines
* src/xcrypt.h: Rename prototypes from crypt* to xcrypt* and
add compat defines.
2003-01-16 Thorsten Kukuk <kukuk@suse.de>
* release version 1.4
* src/blowfish-test.c: Add test with threads.
* src/Makefile.am: Use AM_CFLAGS instead of CFLAGS,
(blowfish_test_LDFLAGS): Add libpthread,
(blowfish_test_CFLAGS): Define number of threads for test.
* src/crypt_util.c: Don't define _LIBC for libc-lock.h,
redefine __libc_lock_t with pthread_mutex_t.
* src/crypt_blowfish.c: Sync with version 0.4.5
2003-01-10 Thorsten Kukuk <kukuk@suse.de>
* release version 1.3
2002-11-04 Thorsten Kukuk <kukuk@suse.de>
* src/crypt_util.c (__init_des_r): Sync with current glibc CVS
(fix initialisation of internal data struct).
* src/md5test.c (main): Sync with current glibc CVS (add test
case for above crypt_util fix).
2002-10-21 Thorsten Kukuk <kukuk@suse.de>
* release version 1.2
* src/crypt_util.c: undef _LIBC after inclusion of libc-lock.h
* src/crypt_blowfish.c: Add support for hppa
* configure.in: bump version number to 1.2
2002-05-27 Thorsten Kukuk <kukuk@suse.de>
* release version 1.1
* src/sha.c: New file.
* src/sha-crypt.c: New file.
* src/md5-private.h: Renamed to ...
* src/xcrypt-private.h: ... to this.
* src/crypt_gensalt.c: Add dummy function for SHA1.
* src/wrapper.c: Call SHA1 functions.
2002-05-14 Thorsten Kukuk <kukuk@suse.de>
* src/xcrypt.h: Add prototpyes for SHA1 functions.
* src/wrapper.c: Don't include md5.h.
* src/md5-crypt.c: Include xcrypt.h instead of md5.h.
* src/md5test.c: Likewise.
* src/md5.c: Likewise.
* src/xcrypt.h: Add prototypes from md5.h.
* src/md5.h: Removed.
2002-04-13 Thorsten Kukuk <kukuk@suse.de>
* release version 1.0
TODO 0000644 00000005027 15170773332 0005250 0 ustar 00 to-do list for libxcrypt
------------------------
* Near future:
* Update all of the default cost parameters
* relevant benchmarking at
<https://pthree.org/2016/06/28/lets-talk-password-hashing/>
* the default used by `crypt_gensalt_*` for new hashes should be
controllable independently from the default used if there is no
rounds= annotation in a setting string
* Make the crypt and crypt_gensalt static state thread-specific?
* if allocated on first use, this would also shave 32kB of
data segment off the shared library
* Factor out all of the repetitive base64 code
* get rid of the de/serialization code in crypt-bcrypt.c that
still does dodgy things with type punning
* Attempt to determine the copyright holders and intended licensing
of the test suite
* Moar tests
* Make sure the symbol versioning macros work with all of the compilers
that anyone needs (they use GCC extensions that clang also supports).
* Longer term:
* Hash algorithms newer than bcrypt tend to want to allocate and
scribble all over a large (tens of megabytes at a minimum) block
of memory, to make brute force hard in a way that GPUs and ASICs
can't easily accelerate. The existing API cannot handle this for
three reasons:
* `crypt_gensalt` only takes a single cost parameter, some
algorithms have several
* With everything except `crypt_ra`, all of the memory is
allocated by the caller and there's no way for algorithms to say
how much they need
* There is no destructor function, even with `crypt_ra` - callers
just pass the block to `free`
So we need to invent a new API that allows for more variety in
cost parameters and allocations. It could also make the "all the
sensitive data, including stack scratch, is in crypt_data which we
auto-erase" feature more robust by adding guard bands and calling
mlock().
* Additional hashes to investigate adding:
* scrypt <https://www.tarsnap.com/scrypt.html>
* Argon2 <https://password-hashing.net/>
* ...?
* Support for "pepper" (an additional piece of information, _not_
stored in the password file, that you need to check a password)
* Reading passphrases from the terminal is finicky and there are
several competing, poorly portable, questionably sound library
functions to do it (`getpass`, `readpassphrase`, etc) -- should we
incorporate one?
* If we do, should it know how to trigger the trusted-path
password prompt in modern GUI environments? (probably)