On 6/1/20 4:51 PM, Bruno Haible wrote:
>> I could add text along
>> these lines if this sounds like a good idea.
>
> Yes, that would sound good.
Done via the attached patch.
>From af3ff63e457ddb6ba29295e3d5b78a93d834cb8e Mon Sep 17 00:00:00 2001
From: Paul Eggert <egg...@cs.ucla.edu>
Date: Mon, 1 Jun 2020 17:02:54 -0700
Subject: [PATCH] getentropy, getrandom: compare to crypto/gc-random
---
doc/glibc-functions/getentropy.texi | 4 ++++
doc/glibc-functions/getrandom.texi | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/doc/glibc-functions/getentropy.texi b/doc/glibc-functions/getentropy.texi
index 2f66ada63..1689a7763 100644
--- a/doc/glibc-functions/getentropy.texi
+++ b/doc/glibc-functions/getentropy.texi
@@ -41,3 +41,7 @@ additional techniques such as hedging.@footnote{Ristenpart T, Yilek
S@. @url{http://pages.cs.wisc.edu/~rist/papers/sslhedge.pdf, When good
randomness goes bad: virtual machine vulnerabilities and hedging
deployed cryptography}. NDSS 2010.}
+
+Related modules include @code{getrandom}, which has a more-flexible
+but more-complex API, and @code{crypto/gc-random}, which is likely a
+better match for code already using the other @code{crypto} APIs.
diff --git a/doc/glibc-functions/getrandom.texi b/doc/glibc-functions/getrandom.texi
index adf7aefcc..a2a259f04 100644
--- a/doc/glibc-functions/getrandom.texi
+++ b/doc/glibc-functions/getrandom.texi
@@ -49,3 +49,7 @@ additional techniques such as hedging.@footnote{Ristenpart T, Yilek
S@. @url{http://pages.cs.wisc.edu/~rist/papers/sslhedge.pdf, When good
randomness goes bad: virtual machine vulnerabilities and hedging
deployed cryptography}. NDSS 2010.}
+
+Related modules include @code{getentropy}, which has a simpler but
+more-limited API, and @code{crypto/gc-random}, which is likely a
+better match for code already using the other @code{crypto} APIs.
--
2.17.1
