On Sat, Jun 09, 2012 at 11:51:41AM +0300, Gleb Kurtsou wrote:
> On (31/05/2012 21:48), Pawel Jakub Dawidek wrote:
> > As learned on someone else's mistakes, I'd like to ask for a review of
> > those changes related to random data handling:
> >
> > http://people.freebsd.org/~pjd/patches/libc_ar
On Tue, Jun 12, 2012 at 01:26:33PM +, FreeBSD Security Advisories wrote:
> IV. Workaround
>
> No workaround is available.
>
> However FreeBSD/amd64 running on AMD CPUs is not vulnerable to this
> particular problem.
>
> Systems with 64 bit capable CPUs, but running the 32 bit FreeBSD/i386
>
On 6/14/12, Greg Lewis wrote:
> On Tue, Jun 12, 2012 at 01:26:33PM +, FreeBSD Security Advisories
> wrote:
>> IV. Workaround
>>
>> No workaround is available.
>>
>> However FreeBSD/amd64 running on AMD CPUs is not vulnerable to this
>> particular problem.
>>
>> Systems with 64 bit capable CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/13/12 15:37, Greg Lewis wrote:
> On Tue, Jun 12, 2012 at 01:26:33PM +, FreeBSD Security
> Advisories wrote:
>> IV. Workaround
>>
>> No workaround is available.
>>
>> However FreeBSD/amd64 running on AMD CPUs is not vulnerable to
>> this
On Thu, Jun 14, 2012 at 02:23:02AM +0200, Oliver Pinter wrote:
> On 6/14/12, Greg Lewis wrote:
> > On Tue, Jun 12, 2012 at 01:26:33PM +, FreeBSD Security Advisories
> > wrote:
> >> IV. Workaround
> >>
> >> No workaround is available.
> >>
> >> However FreeBSD/amd64 running on AMD CPUs is not