From: Damien Miller <djm@mindrot.org>
To: openssl-dev@openssl.org
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Couldn't obtain random bytes in sshd - problem in RAND_poll?
Date: Thu, 7 Aug 2008 18:51:00 +1000 (EST) [thread overview]
Message-ID: <alpine.BSO.1.10.0808071849060.23125@fuyu.mindrot.org> (raw)
In-Reply-To: <489994DF.1050400@meduna.org>
On Wed, 6 Aug 2008, Stanislav Meduna wrote:
> So what should the applications calling openssl actually
> do if this happens? Now the ssh/apache/... simply exit,
> which is bad (it left me without an access to a remote
> box...).
Exiting is the best behaviour - continuing without a good source
of randomness may compromise cryptographic protocols and even
long-term private keys (e.g. if DSA is used).
-d
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2008-08-07 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 9:08 [uml-devel] Couldn't obtain random bytes in sshd - problem in RAND_poll? Stanislav Meduna
2008-08-06 11:11 ` Tomas Mraz
2008-08-06 12:11 ` Stanislav Meduna
2008-08-06 12:55 ` David Schwartz
2008-08-07 8:51 ` Damien Miller [this message]
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=alpine.BSO.1.10.0808071849060.23125@fuyu.mindrot.org \
--to=djm@mindrot.org \
--cc=openssl-dev@openssl.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