From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: New function: secure-random-bytes
Date: Mon, 27 Jun 2011 11:10:36 -0500 [thread overview]
Message-ID: <87y60nb6gz.fsf@lifelogs.com> (raw)
In-Reply-To: 4E04CA7B.2020101@cs.ucla.edu
On Fri, 24 Jun 2011 10:33:47 -0700 Paul Eggert <eggert@cs.ucla.edu> wrote:
PE> On 06/24/11 02:57, Ted Zlatanov wrote:
>> Do you think you could you provide three functions,
>> `secure-random-bytes-{urandom,gnutls,openssl}' instead of three versions
>> with the same name?
PE> I dunno, I kind of like the simpler interface.
PE> It's better to have the notion of a random-source,
PE> independent of the notion of generating random bytes from it.
PE> Whether that source should be represenated by an atom or
PE> by something else is a different matter.
At least for GnuTLS it would make sense to put the function that
actually calls GnuTLS at the C level in gnutls.c. Ditto for OpenSSL.
Beyond that, it can be abstracted any way you like :) My way was just a
suggestion.
PE> I suggest using ISAAC-64, which is what coreutils' random-bytes
PE> generators use by default. (Coreutils originally defaulted to
PE> /dev/urandom, but users complained because that was too slow.)
PE> On my list of things to do is to gnulib-ize the coreutils
PE> ISAAC-64 and random-bytes generators, and I can do that if
PE> there's interest.
Works for me. I think you're right about the /dev/urandom performance.
Ted
next prev parent reply other threads:[~2011-06-27 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 7:50 New function: secure-random-bytes Leo
2011-06-24 9:57 ` Ted Zlatanov
2011-06-24 17:33 ` Paul Eggert
2011-06-25 7:26 ` Leo
2011-06-27 16:10 ` Ted Zlatanov [this message]
2013-03-18 10:26 ` Leo Liu
2013-03-18 16:48 ` Paul Eggert
2013-03-18 21:07 ` Romain Francoise
2019-05-15 12:09 ` Julian Scheid
2019-05-16 17:34 ` Paul Eggert
2011-06-24 13:33 ` James Cloos
2011-06-25 7:27 ` Leo
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y60nb6gz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).