From: Jeff Dike <jdike@addtoit.com>
To: Stanislav Meduna <stano@meduna.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] /dev/random problems _not_ solved in 2.6.26
Date: Mon, 4 Aug 2008 12:42:46 -0400 [thread overview]
Message-ID: <20080804164246.GA14805@c2.user-mode-linux.org> (raw)
In-Reply-To: <4896F8A1.6020203@meduna.org>
On Mon, Aug 04, 2008 at 02:40:01PM +0200, Stanislav Meduna wrote:
> this is just to let you know that the /dev/random problems
> are still not solved in the 2.6.26 version. A small dictionary
> attack on sshd (in my case 260 tries over 12 minutes)
> are able to produce
>
> auth.log.0:Aug 3 05:30:35 dirk sshd[1825]: fatal: Couldn't obtain random bytes (error
> 604389476)
>
> and the sshd dies (followed by apache on the first subsequent
> SSL request and so on).
Off the top of my head, you need the following:
2.6.26 UML, which you do
rngtools installed in the UML
sufficient entropy on the host
This last one shouldn't be taken for granted. I had problems with
this when debugging the random driver changes - on my laptop with me
typing on it, mousing, disk going, and network traffic going in and
out. It would be worse on a colocated, no-keyboard, no-mouse, server,
which are notorious for this problem.
> Unfortunately I can't help you in tracing the uml process
> or trying patches - this is a virtual server at my provider
> and I don't have any access there. I could try to get
> the .config file.
You could ask them about how their servers get their randomness.
If nothing else works, I suppose a nasty workaround might be to
replace /dev/random with dev/urandom, but that has security
implications.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-08-04 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 12:40 [uml-devel] /dev/random problems _not_ solved in 2.6.26 Stanislav Meduna
2008-08-04 16:42 ` Jeff Dike [this message]
2008-08-05 19:37 ` Stanislav Meduna
2008-08-05 21:32 ` Brock, Anthony - NET
2008-08-06 8:13 ` Stanislav Meduna
2008-08-07 9:49 ` [uml-devel] /dev/random problems .. or FP registers corruption?! Stanislav Meduna
2008-08-07 12:13 ` Stanislav Meduna
2008-08-08 12:35 ` [uml-devel] FP registers corruption Stanislav Meduna
2008-08-25 21:51 ` Jeff Dike
2008-08-26 7:20 ` Stanislav Meduna
2008-08-26 17:46 ` Jeff Dike
2008-08-26 18:07 ` Stanislav Meduna
2008-08-26 18:44 ` Jeff Dike
2008-08-26 18:51 ` Stanislav Meduna
2008-08-27 14:59 ` Jeff Dike
2008-09-08 12:13 ` Stanislav Meduna
2008-09-09 22:56 ` Stanislav Meduna
2008-09-12 20:27 ` Stanislav Meduna
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=20080804164246.GA14805@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=stano@meduna.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox