processor microcode update support for Debian GNU/kFreeBSD

2014-07-30 Thread Henrique de Moraes Holschuh
(please CC me, I am not subscribed to debian-bsd@l.d.o). Hello kfreebsd-i386/kfreebsd-amd64 porters, I am the maintainer of intel-microcode and amd64-microcode (non-free), as well as the maintainer and upstream of iucode-tool (contrib). Currently, these three packages are restricted to linux-i3

Re: possible /dev/random compromise (misplaced trust in RDRAND / Padlock entropy sources)

2013-12-15 Thread Henrique de Moraes Holschuh
On Sun, 15 Dec 2013, Robert Millan wrote: > > Backporting the fix to these kernels might be a good idea, probably best > > routed through an stable update upload (and not a security upload). > > This might be a bit complicated due to significant changes in internal > APIs. I'm also unsure if the y

Re: possible /dev/random compromise (misplaced trust in RDRAND / Padlock entropy sources)

2013-12-14 Thread Henrique de Moraes Holschuh
On Sat, 14 Dec 2013, Steven Chamberlain wrote: > On 14/12/13 01:08, Henrique de Moraes Holschuh wrote: > > Yeah, I think Linux went through similar blindness braindamage sometime ago, > > but blind trust on rdrand has been fixed for a long time now, and it never > > trusted a

Re: possible /dev/random compromise (misplaced trust in RDRAND / Padlock entropy sources)

2013-12-13 Thread Henrique de Moraes Holschuh
On Sat, 14 Dec 2013, Robert Millan wrote: > "we are going to backtrack and remove RDRAND and Padlock backends and feed > them into Yarrow instead of delivering their output directly to /dev/random. Yeah, I think Linux went through similar blindness braindamage sometime ago, but blind trust on rdra