Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14885 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2018-12-03 10:03 -0500 |
| Last post | 2018-12-03 10:03 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: $RANDOM not Cryptographically secure pseudorandom number generator Greg Wooledge <wooledg@eeg.ccf.org> - 2018-12-03 10:03 -0500
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-12-03 10:03 -0500 |
| Subject | Re: $RANDOM not Cryptographically secure pseudorandom number generator |
| Message-ID | <mailman.5083.1543849494.1284.bug-bash@gnu.org> |
On Mon, Dec 03, 2018 at 09:56:33AM -0500, Chet Ramey wrote: > There has to be a compelling reason to change this, especially at a point > so close to a major release. > > You might be expecting too much from bash's random number generator. Is > the problem that its period is at most 2**16? For its intended uses, the > cycle length is acceptable. Do you disagree? I suspect he doesn't share the same understanding of the "intended uses" of bash's $RANDOM as the rest of us. It's meant for displaying a random wallpaper image from a directory, or for playing a random audio file from a directory. Or for playing a number guessing game with a 6 year old. It is emphatically NOT for generating passwords.
Back to top | Article view | gnu.bash.bug
csiph-web