From: Kurt Garloff <garloff@suse.de>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: /dev/random: really secure?
Date: Tue, 19 Dec 2000 12:49:48 +0100 [thread overview]
Message-ID: <20001219124948.P17777@garloff.suse.de> (raw)
In-Reply-To: <20001218213801.A19903@pcep-jamie.cern.ch> <200012182133.QAA02136@tsx-prime.MIT.EDU>
In-Reply-To: <200012182133.QAA02136@tsx-prime.MIT.EDU>; from tytso@MIT.EDU on Mon, Dec 18, 2000 at 04:33:13PM -0500
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Mon, Dec 18, 2000 at 04:33:13PM -0500, Theodore Y. Ts'o wrote:
> Note that writing to /dev/random does *not* update the entropy estimate,
> for this very reason. The assumption is that inputs to the entropy
> estimator have to be trusted, and since /dev/random is typically
> world-writeable, it is not so trusted.
It should not be world-writeable, IMHO. So the only one who can feed entropy
there is root, who should know aht (s)he's doing ...
Here (SuSE Linux 7.x), it is 644:
crw-r--r-- 1 root root 1, 8 Dec 17 22:41 /dev/random
crw-r--r-- 1 root root 1, 9 Dec 17 22:41 /dev/urandom
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-12-19 12:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 21:50 Karel Kulhavy
2000-12-18 0:18 ` David Schwartz
2000-12-18 8:21 ` Karel Kulhavy
2000-12-18 20:38 ` Jamie Lokier
2000-12-18 21:33 ` Theodore Y. Ts'o
2000-12-18 22:15 ` Andreas Dilger
2000-12-19 9:27 ` Daniel Stone
2000-12-19 11:49 ` Kurt Garloff [this message]
2000-12-19 12:48 ` Peter Samuelson
2000-12-19 16:51 ` Theodore Y. Ts'o
2000-12-19 17:39 ` Pavel Machek
2000-12-18 21:58 ` David Schwartz
2000-12-18 8:49 ` David Feuer
2000-12-18 9:22 ` Martin Mares
2000-12-19 6:49 ` Philipp Rumpf
2000-12-20 3:41 Bernd Eckenfels
2000-12-20 17:58 ` Jamie Lokier
2000-12-20 3:49 Bernd Eckenfels
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=20001219124948.P17777@garloff.suse.de \
--to=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@MIT.EDU \
/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
all inboxes | Powered by JetHome®