bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: fix list of crypto devices for NetBSD, OpenBSD
Date: Sun, 31 May 2020 01:14:26 +0200	[thread overview]
Message-ID: <1984733.bZ3PVrLcrO@omega> (raw)
In-Reply-To: <20200525193753.12395-1-eggert@cs.ucla.edu>

The list of crypto devices in m4/gc-random.m4 is from 2006.

I get test failures of module 'getrandom' on current versions of
NetBSD and OpenBSD (NetBSD 7.0 and 9.0, and OpenBSD 6.5, to be precise).
These platforms have the quasi-standard /dev/random and /dev/urandom
meanwhile. No more /dev/srandom exists.

This patch fixes the test failures.


2020-05-30  Bruno Haible  <bruno@clisp.org>

	crypto/gc-random: Fix list of crypto devices for NetBSD, OpenBSD.
	* m4/gc-random.m4 (gl_GC_RANDOM): Don't special-case NetBSD and OpenBSD.

diff --git a/m4/gc-random.m4 b/m4/gc-random.m4
index 958c871..15751cb 100644
--- a/m4/gc-random.m4
+++ b/m4/gc-random.m4
@@ -1,4 +1,4 @@
-# gc-random.m4 serial 7
+# gc-random.m4 serial 8
 dnl Copyright (C) 2005-2020 Free Software Foundation, Inc.
 dnl This file is free software; the Free Software Foundation
 dnl gives unlimited permission to copy and/or distribute it,
@@ -12,18 +12,12 @@ AC_DEFUN([gl_GC_RANDOM],
   AC_REQUIRE([AC_CANONICAL_HOST])
 
   case "$host_os" in
-    *openbsd* | *mirbsd*)
+    *mirbsd*)
       NAME_OF_RANDOM_DEVICE="/dev/srandom"
       NAME_OF_PSEUDO_RANDOM_DEVICE="/dev/prandom"
       NAME_OF_NONCE_DEVICE="/dev/urandom"
       ;;
 
-    *netbsd*)
-      NAME_OF_RANDOM_DEVICE="/dev/srandom"
-      NAME_OF_PSEUDO_RANDOM_DEVICE="/dev/urandom"
-      NAME_OF_NONCE_DEVICE="/dev/urandom"
-      ;;
-
     *solaris* | *irix* | *dec-osf* )
       NAME_OF_RANDOM_DEVICE="/dev/random"
       NAME_OF_PSEUDO_RANDOM_DEVICE="/dev/random"



  parent reply	other threads:[~2020-05-30 23:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 19:37 [PATCH] getentropy, getrandom: new modules Paul Eggert
2020-05-30 12:58 ` Bruno Haible
2020-05-30 22:43   ` Paul Eggert
2020-05-31 11:23     ` getrandom vs. crypto/gc-random Bruno Haible
2020-05-31 11:47       ` Bruno Haible
2020-05-31 13:14       ` Jeffrey Walton
2020-05-31 13:23       ` Simon Josefsson
2020-05-31 19:02         ` Bruno Haible
2020-06-01 13:45           ` Jeffrey Walton
2020-06-01 16:53             ` Bruno Haible
2020-06-01 18:13               ` Paul Eggert
2020-06-01 19:01                 ` Bruno Haible
2020-06-01 23:00                   ` Paul Eggert
2020-06-01 23:51                     ` Bruno Haible
2020-06-02  0:04                       ` Paul Eggert
2020-05-30 13:17 ` [PATCH] getentropy, getrandom: new modules Bruno Haible
2020-05-30 14:23 ` Bruno Haible
2020-05-30 23:06   ` sys_random: Work around macOS bug Bruno Haible
2020-05-30 23:28     ` Jeffrey Walton
2020-05-31 10:29       ` Apple platforms Bruno Haible
2020-05-30 15:34 ` [PATCH] getentropy, getrandom: new modules Bruno Haible
2020-05-30 23:14 ` Bruno Haible [this message]
2020-05-31 10:57 ` fix list of crypto devices for Solaris Bruno Haible
2020-05-31 16:26 ` getrandom: Add support for native Windows Bruno Haible
2020-05-31 16:41   ` Jeffrey Walton
2020-05-31 16:49 ` getrandom: doc and test tweaks Bruno Haible
2020-05-31 18:15 ` [PATCH] getentropy, getrandom: new modules Bruno Haible

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1984733.bZ3PVrLcrO@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).