ug.fail_point.random_fortuna_seeded: return(1) -> off
>
> ...
> 9e5eb30f
>
>
> Best,
> Conrad
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP
> On 13 Sep 2015, at 16:45, Sean Bruno <sbr...@freebsd.org> wrote:
> Any chance you can turn TSO off if its on and see what your results are?
Only TSO4 was on. I turned it off; no difference.
M
--
Mark R V Murray
___
freebsd-current
> On 8 Sep 2015, at 19:02, Mark R V Murray <ma...@freebsd.org> wrote:
>
>
>> On 8 Sep 2015, at 17:22, Sean Bruno <sbr...@freebsd.org> wrote:
>>
>>
>>>>>
>>>>> I’m also seeing breakage with the em0 device; this isn’t a kern
> On 8 Sep 2015, at 00:44, Sean Bruno <sbr...@freebsd.org> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
> On 09/07/15 14:10, Mark R V Murray wrote:
>>
>>> On 5 Sep 2015, at 17:11, Garrett Cooper <yaneurab...@gmail.com>
n Communications Inc'
device = 'LNE100TX'
class = network
subclass = ethernet
sym0@pci0:6:1:0:class=0x01 card=0x80001092 chip=0x008f1000 rev=0x04
hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = '53c875J'
class = mass storage
sub
easy as …
# ifconfig em0 down ; service ipfw restart ; ifconfig em0 up
:-)
I’m running CURRENT, r287538. This last worked of me a month or so ago at my
previous build.
M
--
Mark R V Murray
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 22 Aug 2015, at 06:03, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Please fix.
On its way.
M
--
Mark R V Murray
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
On 22 Aug 2015, at 13:49, Mark R V Murray m...@grondar.org wrote:
On 22 Aug 2015, at 06:03, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Please fix.
On its way.
Fixed.
A git commit was in the wrong review (D3197 instead of D3354). This is now
committed as svn commit
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random: device_detach():' missing between the 'umass0'
and 'da0' messages in the last 4 lines.
No. At attach time, the RNG grabs some probe entropy. At detach time it does
nothing.
M
--
Mark R V
On 16 Nov 2014, at 18:21, Ian Lepore i...@freebsd.org wrote:
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random: device_detach():' missing between the 'umass0'
and 'da0' messages
.
I’m also trying to find out why, but I don’t know enough about USB or
mass-storage devices to know why, so this may take me a while. In the
meanwhile, I’ll try to help by pointing out things I do know.
M
--
Mark R V Murray
___
freebsd-current
with SX locks? Hmm. I do use those for attach and detach for
RNG sources. Could it be that that stick of yours is somehow getting
involved in the RNG source locks?
M
--
Mark R V Murray
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
Hi Folks,
Please could the wisdom-of-crowds apply its collective attention to this?
Thanks!
M
Begin forwarded message:
From: Mark R V Murray m...@grondar.org
Subject: New /dev/random code for review please.
Date: 4 May 2014 18:28:43 BST
To: sect...@freebsd.org Team sect...@freebsd.org
AND this
gave a noticeable simplification of script code.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
kern.random.
Are there considerations to extend the HW-rng-implementation by optional
post processing?
Yes. This was discussed in Cambridge recently, and will no doubt be brought
up again in Malta. There are indeed plans to post-process the output of
rdrand.
M
--
Mark R V Murray
signature.asc
On 8 Sep 2013, at 01:36, Glen Barber g...@freebsd.org wrote:
Either way, I think this commit needs to be reverted until properly
fixed and tested.
The hyperbole is getting a little thick.
How about
sysctl kern.random.sys.seeded=1
??
M
--
Mark R V Murray
signature.asc
Description
, that has always been there by intent. That is how etc/rc.d/initrandom is
supposed to work.
In checking the man page I've released that connection needs to be clarified.
I've (re)set the seeded bit, so behaviour is as it was. I'll look for a way
to set this bit from the kernel config file.
M
--
Mark R V
/ was still broken for
arm and mips architectures.
Sorry for the misunderstanding on my part. delphij corrected me on
this.
No worries, thanks!
Keep up the good work!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
please see if you can get the output of sysctl -a | grep random
at that point?
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
a change to sys/dev/random/randomdev_soft.c;
Around line 82, please change from .seeded = 0 to .seeded = 1.
If that works, then your report above with the Entropy device is blocking.
is trying to read random numbers before /dev/random is secure; this is a BAD
security problem.
M
--
Mark R V
On 7 Sep 2013, at 19:36, Sean Bruno sean_br...@yahoo.com wrote:
On Sat, 2013-09-07 at 18:39 +0100, Mark R V Murray wrote:
On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote:
trying to enable random on my DIR-825 kernconf I get this on boot:
Configuration file: /etc/cfg
On 7 Sep 2013, at 19:49, Sean Bruno sean_br...@yahoo.com wrote:
On Sat, 2013-09-07 at 19:40 +0100, Mark R V Murray wrote:
Looks like it does indeed work if that is set to 1.
This DIR-825 config, should be loading random as a module, not
built
into the kernel due to size limitations
On 7 Sep 2013, at 20:12, Sean Bruno sean_br...@yahoo.com wrote:
On Sat, 2013-09-07 at 19:56 +0100, Mark R V Murray wrote:
Ok. Right now, the mips kernel doesn't build unless I have random
built
in, we were using it as a module previously.
I'm testing a fix, but if you want to help
have a hardware PRNG to start seeding things with?
This has some merit; but I need to thing about how to do it. Per-architecture
block/no-block defaults are going to get messy unless done properly.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
, but please bear in mind that things are suboptimal right now.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
(hopefully random crud) to the device
and it seeds itself with what it gets. At file close after the write,
it unblocks.
So at the minimum, you can unblock Yarrow by doing
$ echo '' /dev/random
... as soon as the device is active. There is your knob.
M
--
Mark R V Murray
signature.asc
26 matches
Mail list logo
