From: Zack Weinberg <zackw@panix.com>
To: libc-alpha@sourceware.org
Cc: carlos@redhat.com, fweimer@redhat.com, nmav@redhat.com
Subject: [PATCH 0/3] Cryptography cleanup
Date: Mon, 30 Apr 2018 16:27:00 -0000 [thread overview]
Message-ID: <20180430162731.2971-1-zackw@panix.com> (raw)
This is an expanded version of the patch I posted a couple weeks back
to add a --disable-crypt configure option. There are now three
patches in the series, each with only one purpose:
Zack Weinberg (3):
Reshuffle manual sections on cryptography and random numbers.
Deprecate DES encryption functions.
New configure option --disable-crypt.
INSTALL | 11 +
Makeconfig | 9 +-
NEWS | 20 ++
config.make.in | 1 +
configure | 18 +
configure.ac | 11 +
conform/Makefile | 11 +-
crypt/Makefile | 5 +-
crypt/crypt.h | 22 +-
elf/Makefile | 27 +-
elf/tst-linkall-static.c | 4 +-
manual/Makefile | 4 +-
manual/arith.texi | 2 +-
manual/conf.texi | 2 +-
manual/crypt.texi | 508 +++++---------------------
manual/des.texi | 195 ++++++++++
manual/install.texi | 12 +
manual/math.texi | 586 +-----------------------------
manual/random.texi | 753 +++++++++++++++++++++++++++++++++++++++
manual/string.texi | 6 +-
manual/time.texi | 2 +-
posix/unistd.h | 15 +-
stdlib/stdlib.h | 9 +-
sunrpc/Makefile | 9 +
sunrpc/rpc/des_crypt.h | 11 +-
25 files changed, 1194 insertions(+), 1059 deletions(-)
create mode 100644 manual/des.texi
create mode 100644 manual/random.texi
--
2.17.0
next reply other threads:[~2018-04-30 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 16:27 Zack Weinberg [this message]
2018-04-30 16:27 ` [PATCH 1/3] Reshuffle manual sections on cryptography and random numbers Zack Weinberg
2018-05-01 2:46 ` Rical Jasan
2018-04-30 16:27 ` [PATCH 3/3] New configure option --disable-crypt Zack Weinberg
2018-04-30 16:27 ` [PATCH 2/3] Deprecate DES encryption functions Zack Weinberg
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=20180430162731.2971-1-zackw@panix.com \
--to=zackw@panix.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nmav@redhat.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).