From: "Zvi Gutterman" <zvi@safend.com>
To: "'Muli Ben-Yehuda'" <muli@il.ibm.com>,
"'Kyle Moffett'" <mrmacman_g4@mac.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'Jonathan Day'" <imipak@yahoo.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: /dev/random on Linux
Date: Tue, 16 May 2006 16:54:00 +0300 [thread overview]
Message-ID: <00fc01c678f0$30c77520$2c02a8c0@Safend.com> (raw)
In-Reply-To: <20060516082859.GD18645@rhun.haifa.ibm.com>
Hello All,
I did not get any answer from Matt and was sure that it was of no interest.
This was my mistake, sorry for not sending it earlier to more people.
I will be very happy to discuss any aspect of the paper and we do suggest
ways we think can improve the /dev/random security (a very simple issue for
example is implementing quotas on the consumption of random numbers)
Thanks,
Zvi
-----Original Message-----
From: Muli Ben-Yehuda [mailto:muli@il.ibm.com]
Sent: Tuesday, May 16, 2006 11:29 AM
To: Kyle Moffett
Cc: Alan Cox; Jonathan Day; linux-kernel@vger.kernel.org; Zvika Gutterman
Subject: Re: /dev/random on Linux
On Tue, May 16, 2006 at 04:15:19AM -0400, Kyle Moffett wrote:
> On May 15, 2006, at 22:50, Muli Ben-Yehuda wrote:
> >On Mon, May 15, 2006 at 11:41:07PM +0100, Alan Cox wrote:
> >>A paper by people who can't work out how to mail linux-kernel or
> >>vendor-sec, or follow "REPORTING-BUGS" in the source,
> >
> >Zvi did contact Matt Mackall, the current /dev/random maintainer,
> >and was very keen on discussing the paper with him. I don't think
> >he got any response.
>
> So he's demanding that one person spend time responding to his
> paper?
Who said anything about demanding? he wanted to discuss the paper. He
received no response (AFAIK). Please don't read more into it.
> The "maintainer" for any given piece of the kernel is the
> entry in MAINTAINERS *and* linux-kernel@vger.kernel.org *and* the
> appropriate sub-mailing-list.
For security related information, it is sometimes best not to tell the
whole world about it immediately (although you should definitely tell
the whole world about it eventually). It should've probably been
posted to lkml when mpm didn't respond, I agree. I'll take the blame
for not suggesting that to Zvi.
Cheers,
Muli
next prev parent reply other threads:[~2006-05-16 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:39 /dev/random on Linux Jonathan Day
2006-05-15 22:41 ` Alan Cox
2006-05-16 2:50 ` Muli Ben-Yehuda
2006-05-16 8:15 ` Kyle Moffett
2006-05-16 8:28 ` Muli Ben-Yehuda
2006-05-16 8:52 ` Kyle Moffett
2006-05-16 13:54 ` Zvi Gutterman [this message]
2006-05-16 20:17 ` Theodore Tso
2006-05-16 20:37 ` Chase Venters
2006-05-17 21:32 ` Theodore Tso
2006-05-16 10:24 ` Alan Cox
2006-05-16 12:46 ` Pavel Machek
2006-05-16 15:04 ` Christopher Friesen
2006-05-16 14:58 ` Michael Buesch
2006-05-16 15:08 ` Johannes Berg
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='00fc01c678f0$30c77520$2c02a8c0@Safend.com' \
--to=zvi@safend.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=imipak@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=muli@il.ibm.com \
/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