On Mon, Jun 11, 2018 at 1:28 PM, Yann Ylavic wrote:
>
> So we could:
> a/ Replace 2/ with this new RNG,
> b/ Axe 2/ from APR-2 and add the new RNG in apr_crypto,
> c/ Axe 2/ from APR-2 and leave 1/ as the only RNG.
Just committed b/ in r1833359 for easier review, apr_random code not axed yet.
except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ *
On Thu, Jun 7, 2018 at 11:59 AM, Yann Ylavic wrote:
> I'd like to propose a new RNG for APR, based on a design from D.J.
> Bernstein ([1]).
>
> Called "Fast-key-erasure random-number generators" by the author, it
> requires 256bits (32 bytes) of initial entropy only, is fast, and
> ensures Forward
I'd like to propose a new RNG for APR, based on a design from D.J.
Bernstein ([1]).
Called "Fast-key-erasure random-number generators" by the author, it
requires 256bits (32 bytes) of initial entropy only, is fast, and
ensures Forward Secrecy.
The current RNGs available in APR are:
1/ apr_generat
> regarding to random number device in apr - thanks for
> --with-randomdev=foo configure option in 2.0.39. it seems to me that
> there's a bug in the handling. without the patch,
> DEV_RANDOM will end up defined as $apr_randomdev (verbatim).
> (i requested bug databa
regarding to random number device in apr - thanks for
--with-randomdev=foo configure option in 2.0.39. it seems to me that
there's a bug in the handling. without the patch,
DEV_RANDOM will end up defined as $apr_randomdev (verbatim).
(i requested bug databa
Huh, that's odd. I swear I tested this. I'll look into it tomorrow and
place this in patches/apply_to_2.0.39/ if need be.
Thanks,
Cliff
On Wed, 19 Jun 2002 itojun@iijlab.net wrote:
> regarding to random number device in apr - thanks for
> --with-randomdev=foo configure option in
Ben Laurie wrote:
>
> I still say it should be runtime configurable.
>
++1
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
"A society that will trade a little liberty for a little or
On Mon, 17 Jun 2002, hiroyuki hanai wrote:
> Ben Laurie wrote:
> > > you can specify with a ./configure argument which one you want. It will
> > > be part of 2.0.38.
> >
> > I still say it should be runtime configurable.
>
> I strongly agree with Ben.
Well, so do I. But somebody's got to sit do
Ben Laurie wrote:
> > you can specify with a ./configure argument which one you want. It will
> > be part of 2.0.38.
>
> I still say it should be runtime configurable.
I strongly agree with Ben.
hiro hanai
On Sun, 16 Jun 2002, Cliff Woolley wrote:
> On Sun, 16 Jun 2002 itojun@iijlab.net wrote:
>
> > on unix platforms, apr shipped with httpd 2.0.36 asks for truely-
> > random number (/dev/random) instead of so-so random number
> > (/dev/urandom). question: is it really necessary to requ
Cliff Woolley wrote:
On Sun, 16 Jun 2002 itojun@iijlab.net wrote:
on unix platforms, apr shipped with httpd 2.0.36 asks for truely-
random number (/dev/random) instead of so-so random number
(/dev/urandom). question: is it really necessary to require
/dev/random in
On Sun, 16 Jun 2002 itojun@iijlab.net wrote:
> on unix platforms, apr shipped with httpd 2.0.36 asks for truely-
> random number (/dev/random) instead of so-so random number
> (/dev/urandom). question: is it really necessary to require
> /dev/random instead of /dev/urandom
on unix platforms, apr shipped with httpd 2.0.36 asks for truely-
random number (/dev/random) instead of so-so random number
(/dev/urandom). question: is it really necessary to require
/dev/random instead of /dev/urandom? if not, does the following patch
ma
: <[EMAIL PROTECTED]>
>
> > > This is almost the entire problem with random numbers - what is
> > > good enough?
samba's random number generator uses /dev/[u]random whichever
is available; md4 on all files in /tmp, /dev and other locations
where large number
15 matches
Mail list logo
