Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15027
| Path | csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail |
|---|---|
| From | Ole Tange <tange@gnu.org> |
| Newsgroups | gnu.bash.bug |
| Subject | Re: $RANDOM not Cryptographically secure pseudorandom number generator |
| Date | Wed, 2 Jan 2019 02:29:24 +0100 |
| Lines | 36 |
| Approved | bug-bash@gnu.org |
| Message-ID | <mailman.6674.1546392582.1284.bug-bash@gnu.org> (permalink) |
| References | <CA+4vN7zoPwhL5E82pDb=20yk4Dxdj=iRJiY2mmsbAtN1yqSeZw@mail.gmail.com> <868cc2da-cf67-298f-4640-ab1afcf857e0@case.edu> <CA+4vN7wkuCya7FES1HXiyFTF3a=pkVSdhVCthmjR29OwCAKZng@mail.gmail.com> <fa0b238c-9cb5-a840-ec6b-15cfd11d15cd@case.edu> <CA+4vN7zP26E6o13ysfppv8zjMWDV5BgQNQ1i6GP-3pg_ewVVeA@mail.gmail.com> <4bc5800d-0dfb-17a5-0b20-9f4bef5a60b6@case.edu> <CA+4vN7yTJRqc=8eCJWQMXu7nZu7ZreLTEp56SC-LTavSVW-d1A@mail.gmail.com> <CAOSMAus5OvX91r-y8K3Bw7e-T1aj9U72+uE64iM346AV+uSwAA@mail.gmail.com> <CA+4vN7wS_PPH60j_gw2t_2kokds0eZxCzgqAydqiNz5=JLTMxw@mail.gmail.com> <8d46616b-7618-be59-3651-1a01bc3bf7e6@case.edu> |
| NNTP-Posting-Host | lists.gnu.org |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset="UTF-8" |
| X-Trace | usenet.stanford.edu 1546392582 5500 208.118.235.17 (2 Jan 2019 01:29:42 GMT) |
| X-Complaints-To | action@cs.stanford.edu |
| Cc | Eduardo Bustamante <dualbus@gmail.com>, bug-bash <bug-bash@gnu.org> |
| To | Chet Ramey <chet.ramey@case.edu> |
| Envelope-to | bug-bash@gnu.org |
| X-Google-DKIM-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cfFOg68sshkuBwH5MhctMHMN8vOWWpM6T1ckEUrjX1I=; b=AyRFOcc+Qo1A750W6oZ7lXvFnH48WI0V8VhSLFOq2k2TPJ7dtezEfIklizv4PblrRB 5dpkRYYu3Mx03djdWP5oGgdgPDBSOOHgIYHj9+s2tLM1PZGCuC1ZirQtAfPxt30f7Sts hzNuo2G23E/3gKGWOog88H1X1uOYZ+yPnXrSP8siv7YEpRJmOZglj3rsWUlN2LAamL29 4ejvY5Xc+tlQs3AbPoPEaIhN/cHGdldKf4s9Q7afCqg1K/8PLp6Nduiu1DRE79mLjIVd KU2lX2jfGfXmrGQiSuyf6wbl2mQQ+paHhUm5uW6tmZlpdgIzZOdFavzey2aNxrrCqpEp 6LzA== |
| X-Gm-Message-State | AA+aEWaQHiU7Xp7sNSEHk59QCYd5R9h60pvqZaub4fExp/ZKIINf7f+0 Qj7tZ59/Q5/PJajkBjzpcPDHfMhoXX97ipqIEMk= |
| X-Google-Smtp-Source | AFSGD/UgIZcX+HlloOEM5SNiOgIQVST4mtpIbA9fCkZpuj7v58pK/PMZ5NzS+a3i+g9bJwpy8loiXir9oIKK6RT/4Wo= |
| X-Received | by 2002:a02:708e:: with SMTP id f136mr27981024jac.118.1546392576889; Tue, 01 Jan 2019 17:29:36 -0800 (PST) |
| In-Reply-To | <8d46616b-7618-be59-3651-1a01bc3bf7e6@case.edu> |
| X-detected-operating-system | by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] |
| X-Received-From | 209.85.166.179 |
| X-BeenThere | bug-bash@gnu.org |
| X-Mailman-Version | 2.1.21 |
| Precedence | list |
| List-Id | Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org> |
| List-Unsubscribe | <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe> |
| List-Archive | <http://lists.gnu.org/archive/html/bug-bash/> |
| List-Post | <mailto:bug-bash@gnu.org> |
| List-Help | <mailto:bug-bash-request@gnu.org?subject=help> |
| List-Subscribe | <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe> |
| Xref | csiph.com gnu.bash.bug:15027 |
Show key headers only | View raw
On Mon, Dec 31, 2018 at 8:12 PM Chet Ramey <chet.ramey@case.edu> wrote: : > Thanks for the patch. I'll take a look after I release bash-5.0. One > question: can you reproduce the same random sequence by using the same > seed? That's for backwards compatibility, even if the sequences themselves > differ. Yes. Seeding with a value will give the same sequence: $ RANDOM=4; echo $RANDOM $RANDOM 21584 22135 $ RANDOM=4; echo $RANDOM $RANDOM 21584 22135 For backwards compatibility integers are supported, but they are really parsed as strings. Strings make it easier to seed with more than 64-bits: RANDOM=`cat GPLv3.txt` So these give the same value on 4.4.23, but differs with the patch applied: RANDOM=$(echo 2^64 | bc );echo $RANDOM RANDOM=$(echo 2^65 | bc );echo $RANDOM RANDOM="foo"; echo $RANDOM RANDOM="bar"; echo $RANDOM RANDOM=2; echo $RANDOM RANDOM=" 2.0"; echo $RANDOM RANDOM=" 2.0noise"; echo $RANDOM /Ole
Back to gnu.bash.bug | Previous | Next — Next in thread | Find similar | Unroll thread
Re: $RANDOM not Cryptographically secure pseudorandom number generator Ole Tange <tange@gnu.org> - 2019-01-02 02:29 +0100 Re: $RANDOM not Cryptographically secure pseudorandom number generator Luuk <luuk@invalid.lan> - 2019-01-02 12:01 +0100
csiph-web