Your message dated Sun, 10 May 2026 11:00:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#873047: libgfshare: gfsplit SIGSEGV if /dev/urandom is
not accessible
has caused the Debian Bug report #873047,
regarding libgfshare: gfsplit SIGSEGV if /dev/urandom is not accessible
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
873047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873047
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgfshare
Version: 2.0.0-2
Severity: normal
Tags: patch
Hi,
gfsplit SIGSEGV if /dev/urandom is not accessible as it doesn't fallback
to the (correctly named!) gfshare_bad_idea_but_fill_rand_using_random; it
prints a warning to stderr.
Patch attached.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
diff --git a/tools/gfsplit.c b/tools/gfsplit.c
index 9aadb22..c02c4d4 100644
--- a/tools/gfsplit.c
+++ b/tools/gfsplit.c
@@ -164,6 +164,7 @@ main( int argc, char **argv )
if (access("/dev/urandom", R_OK) == 0) {
gfshare_fill_rand = gfsplit_fill_rand;
} else {
+ gfshare_fill_rand = gfshare_fill_rand =
gfshare_bad_idea_but_fill_rand_using_random;
fprintf(stderr, "\
%s: Cannot access /dev/urandom, so using rand() instead (not secure!)\n\
", progname);
--- End Message ---
--- Begin Message ---
Version: 1.0.3-1
On Sat, 27 Jan 2018 at 21:51:20 +0000, Simon McVittie wrote:
If [enforcing a crash on inability to read /dev/urandom was]
the intention, it would be better if it was clearly deliberate
by calling abort() or fprintf() + exit().
This was implemented in 1.0.3 upstream, closing the bug.
smcv
--- End Message ---
