> 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 > official tarball. Per the Security Policy, you *must* do: > > gunzip -c openssl-fips-2.0.12.tar.gz | tar xf - > > and *not* any functionally equivalent alternative such as: > > tar -zxf openssl-fips-2.0.12.tar.gz >
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 security policy. -- View this message in context: http://openssl.6102.n7.nabble.com/FIPS-compile-issue-with-Perl-on-Windows-tp65574p65591.html Sent from the OpenSSL - User mailing list archive at Nabble.com. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
