On 01/04/2013 03:45 AM, Jeffrey Walton wrote:
Hi All,
I'm wondering how the single pass linker affects symbol resolution. If
I specify:
fipscanister.o libcrpyto.a
the linker will resolve symbols preferring the cryptography from
fipscanister.o, then from libcrpyto.a. After
On Fri, Jan 4, 2013 at 10:56 AM, Steve Marquess
marqu...@opensslfoundation.com wrote:
On 01/04/2013 03:45 AM, Jeffrey Walton wrote:
Hi All,
I'm wondering how the single pass linker affects symbol resolution. If
I specify:
fipscanister.o libcrpyto.a
the linker will resolve symbols
On Fri, Jan 4, 2013 at 11:21 AM, Jeffrey Walton noloa...@gmail.com wrote:
On Fri, Jan 4, 2013 at 10:56 AM, Steve Marquess
marqu...@opensslfoundation.com wrote:
On 01/04/2013 03:45 AM, Jeffrey Walton wrote:
Either the libcrypto.a is from a FIPS
capable OpenSSL build, in which case it
On 01/04/2013 11:36 AM, Jeffrey Walton wrote:
...
OK. So here is the point of confusion for me. 2.5 Relationship to the
OpenSSL API, page 19 of the User Guide:
Applications linked with the FIPS Object Module
and with the separate OpenSSL libraries can use
both the FIPS
On 01/04/2013 11:21 AM, Jeffrey Walton wrote:
...
In my final application, I always link against libcrypto.a. Period. I
never link against fipscanister.o. Period.
That is as it should be. In general the application developer should not
be referencing fipscanister.o, only the sysadmin
