From: daw@mozart.cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: Is writing to /dev/ramdom a security flaw (vserver project)
Date: 20 Oct 2001 00:26:45 GMT [thread overview]
Message-ID: <9qqgc5$4ht$1@abraham.cs.berkeley.edu> (raw)
In-Reply-To: <20011019172309.4219c22e9a53@remtk.solucorp.qc.ca>
Jacques Gelinas wrote:
>Is this a security issue if an administrator of a vserver is allowed to write
>in /dev/random ?
If you're talking about write(2), it should be safe, since the entropy
count is not affected. If you're talking about doing an ioctl(2) on
/dev/random, this is risky (since root can modify the entropy counter),
but it looks like all those code paths are protected by a capability
check, so my guess is that you're probably ok this, too.
prev parent reply other threads:[~2001-10-20 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 22:23 Is writing to /dev/ramdom a security flaw (vserver project) Jacques Gelinas
2001-10-19 21:38 ` Christopher Friesen
2001-10-20 0:26 ` David Wagner [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='9qqgc5$4ht$1@abraham.cs.berkeley.edu' \
--to=daw@mozart.cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
/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