From: David Craven <david@craven.ch>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] services: Add 'dropbear-service'.
Date: Thu, 7 Jul 2016 19:54:23 +0200 [thread overview]
Message-ID: <CAL1_imm_usAMVg+6A4hgCAd4hFqVp82Wm8o6B3_htuKZj=+J_A@mail.gmail.com> (raw)
In-Reply-To: <20160707172517.GA5283@jasmine>
That's my understanding too. From a quick glance at the source it
falls back onto stuff from /proc /sys. I guess there are weaker links
in a system dough, but I'm also no expert.
On a side note there are the matsano crypto challanges that are pretty
cool, in case you haven't heard of them, I never got to the
implementing/cracking prngs dough, simply not enough time...
[0]
https://github.com/mkj/dropbear/blob/master/dbrandom.c#L205
http://cryptopals.com/
next prev parent reply other threads:[~2016-07-07 17:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 20:56 [PATCH 1/2] gnu: lsh: Move to (gnu packages ssh) David Craven
2016-07-04 20:56 ` [PATCH 2/2] services: Add 'dropbear-service' David Craven
2016-07-07 17:25 ` Leo Famulari
2016-07-07 17:54 ` David Craven [this message]
2016-07-09 14:39 ` David Craven
2016-07-09 18:32 ` Leo Famulari
2016-07-09 21:31 ` David Craven
2016-07-09 22:41 ` Leo Famulari
2016-07-09 22:43 ` Leo Famulari
2016-07-09 23:03 ` David Craven
2016-07-09 23:34 ` David Craven
2016-07-11 8:33 ` Ludovic Courtès
2016-07-13 13:09 ` David Craven
2016-07-13 15:58 ` David Craven
2016-07-13 16:25 ` David Craven
2016-07-05 6:01 ` [PATCH 1/2] gnu: lsh: Move to (gnu packages ssh) Efraim Flashner
2016-07-05 6:24 ` Efraim Flashner
2016-07-05 11:47 ` David Craven
-- strict thread matches above, loose matches on Subject: below --
2016-07-13 16:13 [PATCH 0/2] Dropbear service take two David Craven
2016-07-13 16:13 ` [PATCH 2/2] services: Add 'dropbear-service' David Craven
2016-07-15 16:00 ` Ludovic Courtès
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='CAL1_imm_usAMVg+6A4hgCAd4hFqVp82Wm8o6B3_htuKZj=+J_A@mail.gmail.com' \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.