From: Joseph Myers <joseph@codesourcery.com>
To: Rical Jasan <rj@2c3t.io>
Cc: Zack Weinberg <zackw@panix.com>, <libc-alpha@sourceware.org>,
<carlos@redhat.com>, <fweimer@redhat.com>
Subject: Re: [PATCH 2/4] Revise manual sections on cryptography and random numbers.
Date: Wed, 09 May 2018 15:47:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1805091543550.16046@digraph.polyomino.org.uk> (raw)
In-Reply-To: <52e9ad02-eefc-11d1-2e04-ce0b0417a9df@2c3t.io>
On Wed, 9 May 2018, Rical Jasan wrote:
> Perhaps someone else can weigh in on whether crypt.h is BSD or GNU.
crypt.h is not in the CSRG BSD history (so not in BSD 4.4, which is what
would typically have been meant by BSD in the manual). See e.g.
<https://github.com/weiss/original-bsd>.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-05-09 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 17:52 [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Zack Weinberg
2018-05-06 17:51 ` [PATCH 3/4] Deprecate DES encryption functions Zack Weinberg
2018-05-08 14:33 ` Florian Weimer
2018-05-08 15:24 ` Zack Weinberg
2018-05-06 17:52 ` [PATCH 4/4] New configure option --disable-crypt Zack Weinberg
2018-05-08 15:00 ` Florian Weimer
2018-05-08 15:22 ` Zack Weinberg
2018-05-06 17:52 ` [PATCH 2/4] Revise manual sections on cryptography and random numbers Zack Weinberg
2018-05-08 14:23 ` Florian Weimer
2018-05-08 15:59 ` Zack Weinberg
2018-05-08 17:51 ` Florian Weimer
2018-05-09 11:36 ` Rical Jasan
2018-05-09 15:47 ` Joseph Myers [this message]
2018-05-06 17:52 ` [PATCH 1/4] Reorganize " Zack Weinberg
2018-05-08 13:29 ` Florian Weimer
2018-05-08 13:37 ` Zack Weinberg
2018-05-08 13:38 ` Florian Weimer
2018-05-09 11:36 ` Rical Jasan
2018-05-08 22:56 ` [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Rical Jasan
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=alpine.DEB.2.20.1805091543550.16046@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rj@2c3t.io \
--cc=zackw@panix.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).