On 04/19/2016 10:43 AM, Jakob Bohm wrote:
> On 19/04/2016 16:31, Steve Marquess wrote:
>> On 04/19/2016 09:16 AM, Jakob Bohm wrote:
>>> On 19/04/2016 13:44, Leaky wrote:
Thanks, but I am still scratching my head as to if that is even
possible on
Windows, which would mean you can't ac
On 19/04/2016 16:31, Steve Marquess wrote:
On 04/19/2016 09:16 AM, Jakob Bohm wrote:
On 19/04/2016 13:44, Leaky wrote:
Thanks, but I am still scratching my head as to if that is even
possible on
Windows, which would mean you can't actually compile the FIPS canister on
Windows and meet the secur
On 04/19/2016 09:16 AM, Jakob Bohm wrote:
> On 19/04/2016 13:44, Leaky wrote:
>>> The Security Policy is quite specific on the requirements, which make no
>>> allowance for the common sense (to a software engineer) fact that there
>>> are equivalent multiple ways to accomplish each step (such as un
On 19/04/2016 13:44, Leaky wrote:
The Security Policy is quite specific on the requirements, which make no
allowance for the common sense (to a software engineer) fact that there
are equivalent multiple ways to accomplish each step (such as unzipping
the tarball). You are also specifically requir
> The Security Policy is quite specific on the requirements, which make no
> allowance for the common sense (to a software engineer) fact that there
> are equivalent multiple ways to accomplish each step (such as unzipping
> the tarball). You are also specifically required to begin with the
> offic
On 04/18/2016 08:25 PM, Jakob Bohm wrote:
> On 19/04/2016 01:51, Steve Marquess wrote:
>> On 04/18/2016 04:05 PM, Leaky wrote:
> plus you're constrained by the
> requirements of the Security Policy to build the module with precisely
> the commands:
>
> gunzip -c openssl-fips-2
On 19/04/2016 01:51, Steve Marquess wrote:
On 04/18/2016 04:05 PM, Leaky wrote:
plus you're constrained by the
requirements of the Security Policy to build the module with precisely
the commands:
gunzip -c openssl-fips-2.0.12.tar.gz | tar xvf -
cd openssl-fips-2.0.12
./config
make
Sill
On 04/18/2016 04:05 PM, Leaky wrote:
>>> plus you're constrained by the
>>> requirements of the Security Policy to build the module with precisely
>>> the commands:
>>>
>>> gunzip -c openssl-fips-2.0.12.tar.gz | tar xvf -
>>> cd openssl-fips-2.0.12
>>> ./config
>>> make
>
> Silly question... I
>> plus you're constrained by the
>> requirements of the Security Policy to build the module with precisely
>> the commands:
>>
>> gunzip -c openssl-fips-2.0.12.tar.gz | tar xvf -
>> cd openssl-fips-2.0.12
>> ./config
>> make
Silly question... I know that you should only run the above commands
On 04/18/2016 11:01 AM, Tristan Leask wrote:
> Hi All,
>
> I am currently trying to setup an automated build process for a
> cloned copy of the code. ...
>
> In the link mentioned, it is talked about modifying the perl script
> to change how STDOUT works, however when you are compiling FIPS you
Hi All,
I am currently trying to setup an automated build process for a cloned copy of
the code. I can run through the process manually by issuing all the commands
required from a command line without issue. If I then take all these commands
and put them into a CI job using Jenkins, I then se
11 matches
Mail list logo
