On 09/13/2012 06:08 PM, TJ wrote:
> On 7 September 2012 23:54, Steve Marquess
> wrote:
>> On 09/07/2012 12:24 AM, TJ wrote:
>>> I'm doing a cross platform FIPS build (FIPSv2.0.1 with OpenSSL 1.01c).
>>>
>>> ./Configure no-asm no-hw linux-generic32
>>> make -j1 -C openssl-fips
>>
>> Might as well s
On Fri, Sep 14, 2012, TJ wrote:
> On 7 September 2012 23:54, Steve Marquess
> wrote:
> > On 09/07/2012 12:24 AM, TJ wrote:
> >> I'm doing a cross platform FIPS build (FIPSv2.0.1 with OpenSSL 1.01c).
> >>
> >> ./Configure no-asm no-hw linux-generic32
> >> make -j1 -C openssl-fips
> >
> > Might as
On 7 September 2012 23:54, Steve Marquess
wrote:
> On 09/07/2012 12:24 AM, TJ wrote:
>> I'm doing a cross platform FIPS build (FIPSv2.0.1 with OpenSSL 1.01c).
>>
>> ./Configure no-asm no-hw linux-generic32
>> make -j1 -C openssl-fips
>
> Might as well stop right there as the resulting FIPS module
On 09/07/2012 12:24 AM, TJ wrote:
> I'm doing a cross platform FIPS build (FIPSv2.0.1 with OpenSSL 1.01c).
>
> ./Configure no-asm no-hw linux-generic32
> make -j1 -C openssl-fips
Might as well stop right there as the resulting FIPS module isn't FIPS
140-2 validated. There is no point in using the