From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: libxcrypt 4.4.4-1
Date: Fri, 05 Apr 2019 01:59:00 -0000 [thread overview]
Message-ID: <20190404214849.20490-1-yselkowitz@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* libcrypt2-4.4.4-1
* libcrypt-devel-4.4.4-1
libxcrypt is a modern library for one-way hashing of passwords. It
supports a wide variety of both modern and historical hashing methods:
yescrypt, gost-yescrypt, scrypt, bcrypt, sha512crypt, sha256crypt,
md5crypt, SunMD5, sha1crypt, NT, bsdicrypt, bigcrypt, and descrypt. It
provides the traditional Unix crypt and crypt_r interfaces, as well as a
set of extended interfaces.
This switches our crypt(3) implementation to an externally maintained
one used nowadays by modern Linux distributions. As this version uses
a different definition of struct crypt_data, it is not ABI compatible
with its predecessor, and therefore applications will need to be rebuilt
to use this version.
In addition, the encrypt(3) and setkey(3) APIs are removed from this version,
as done also by newer Linux distributions, as they only support weak ciphers
which should no longer be used nowadays.
--
Yaakov
reply other threads:[~2019-04-05 1:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190404214849.20490-1-yselkowitz@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).