All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ipad@petergarner.net" <ipad@petergarner.net>
To: noloader@gmail.com
Cc: peter garner <peter@petergarner.net>, wireguard@lists.zx2c4.com
Subject: Re: Using OneRNG hardware RNG can I get wireguard to use /dev/random
Date: Fri, 24 Jul 2020 09:58:25 +0100	[thread overview]
Message-ID: <7D62871B-4F42-4B15-AEDA-25352B041FFA@petergarner.net> (raw)
In-Reply-To: <CAH8yC8nCwwx8h8HmTGhsh10Dm4ThQTc=53ESfO=6iAXx4XvqmQ@mail.gmail.com>


>> On 24 Jul 2020, at 09:33, Jeffrey Walton <noloader@gmail.com> wrote:
>> 
>> On Fri, Jul 24, 2020 at 4:28 AM peter garner <peter@petergarner.net> wrote:
>> I've used my OneRNG v3.0 external device to recreate my SSH moduli and
>> am now looking to recreate my wireguard keys.
>> According to the Wireguard docs it uses /dev/urandom:
>> https://gist.github.com/rmoriz/58f1768218a4fbc4b318615bfb85111d
>> fd = open("/dev/urandom", O_RDONLY);
>>       if (fd < 0)
>>               return fd;
>>       ret = read(fd, out, len);
>>       close(fd);
> 
> Unrelated, the kernel-crypto folks recommend using /dev/urandom.
> Wiregaurd is following best practices. Also see
> https://lkml.org/lkml/2017/7/20/993.
> 
> Jeff

Thanks Jeff - all is now clear (that link helped as well). I've been doing some additional research and everything makes sense.







  reply	other threads:[~2020-07-24 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 14:58 Using OneRNG hardware RNG can I get wireguard to use /dev/random peter garner
2020-07-24  8:32 ` Jeffrey Walton
2020-07-24  8:58   ` Ipad@petergarner.net [this message]
2020-07-24  8:55 ` Jason A. Donenfeld

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

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

  git send-email \
    --in-reply-to=7D62871B-4F42-4B15-AEDA-25352B041FFA@petergarner.net \
    --to=ipad@petergarner.net \
    --cc=noloader@gmail.com \
    --cc=peter@petergarner.net \
    --cc=wireguard@lists.zx2c4.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.