Hi Steve,
Could you please help me out?
I tried to re-read that part of user-guide but no success.
I know how to generate fingerprint but once i create new static library out
of libcrypto.a and libssl.a.
And I do generate the finger print of that new library but don't know how
to proceed further
On 24/06/2016 15:24, Sahil Gandhi wrote:
Hi Steve,
Could you please help me out?
I tried to re-read that part of user-guide but no success.
I know how to generate fingerprint but once i create new static
library out of libcrypto.a and libssl.a.
And I do generate the finger print of that new
On 06/24/2016 03:10 AM, Sahil Gandhi wrote:
> Hi Jakob,
>
> Could you please elaborate it? I am not getting it.
> I might missing something but I did not get it.
>
> Many Thanks Jakob for replying.
>
> -Sahil
>
> On Fri, Jun 24, 2016 at 11:57 AM, Jakob Bohm
On 24/06/2016 07:59, Sahil Gandhi wrote:
Hi All,
I have built Openssl-fips-2.0.10.tar on* RHEL Linux* (/_*Same happens
with Solaris 10*_/). Then I built Openssl-1.0.1p using respective fips
object module (i.e. Openssl-fips-2.0.10.tar).
Once I have built Openssl-1.0.1p, libcrypto.a and
Hi Jakob,
Could you please elaborate it? I am not getting it.
I might missing something but I did not get it.
Many Thanks Jakob for replying.
-Sahil
On Fri, Jun 24, 2016 at 11:57 AM, Jakob Bohm wrote:
> On 24/06/2016 07:59, Sahil Gandhi wrote:
>
>> Hi All,
>>
>> I have
Hi All,
I have built Openssl-fips-2.0.10.tar on* RHEL Linux* (*Same happens with
Solaris 10*). Then I built Openssl-1.0.1p using respective fips object
module (i.e. Openssl-fips-2.0.10.tar).
Once I have built Openssl-1.0.1p, libcrypto.a and libssl.a has been created.
I need to join these 2
You can look into modifying the window size for transmission (likely
devastating your throughput, considering it will have to drop from around
usual 64K to about a tenth of the size - mostly notably with the increase
of ACKs and header repetition with each packet ... falls too far and it
will
less headache static linking to SSLEAY32 and LIBEAY32 :), depending on how
many windows versions you want to support, static linking to WS2_32 and
CRYP32 may also be useful (though linking all 4 nearly tripled the binary
for what we needed to have included), but don't have to worry about what