From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.7: random.c - potential security problem
Date: Fri, 10 Aug 2001 07:53:04 +0200 [thread overview]
Message-ID: <3B7392DF.231.5D8E1@localhost> (raw)
Hi,
maybe some of you find this interesting: Yesterday I was grepping for
some variable in the source tree when I ended up in
drivers/char/random.c. There I noticed that the driver uses wall time
to re-seed the TCP sequence numbers for example. This means that no re-
seeding takes place if the clock is set back a significant amount of
time, e.g. if the CMOS clock failed or was completely off.
I don't know if the problem is severe, but I thought I tell you.
Regards,
Ulrich
P.S. Not subscribed to this list
next reply other threads:[~2001-08-10 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 5:53 Ulrich Windl [this message]
[not found] <20010810070319.10233.qmail@science.horizon.com>
2001-08-10 7:30 ` 2.4.7: random.c - potential security problem Ulrich Windl
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=3B7392DF.231.5D8E1@localhost \
--to=ulrich.windl@rz.uni-regensburg.de \
--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