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 libssl
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 librar
Dear Users,
I have released version 5.33 of stunnel.
This release fixes a memory leak. Upgrade is highly recommended.
The ChangeLog entry:
Version 5.33, 2016.06.23, urgency: HIGH
* New features
- Improved memory leak detection performance and accuracy.
- Improved compatibility with the curr
On Jun 23, 2016, at 1:44 PM, Jakob Bohm wrote:
> On 23/06/2016 18:25, Russ Loucks wrote:
>> We have an application running on Windows 8.1 (HP) tablets that is mostly
>> statically linked except for a few libraries, including the SSLEAY32 and
>> LIBEAY32 libraries.
>>
>> We're using version 1.
On 23/06/2016 18:25, Russ Loucks wrote:
We have an application running on Windows 8.1 (HP) tablets that is
mostly statically linked except for a few libraries, including the
SSLEAY32 and LIBEAY32 libraries.
We're using version 1.0.2 of the OpenSSL libraries.
We ship our executable and these t
We have an application running on Windows 8.1 (HP) tablets that is mostly
statically linked except for a few libraries, including the SSLEAY32 and
LIBEAY32 libraries.
We're using version 1.0.2 of the OpenSSL libraries.
We ship our executable and these two libraries and then set a PATH entry in
Hi OpenSSL users,
I have come across an issue which is reported in the below ticket:
http://rt.openssl.org/Ticket/Display.html?id=4582
(Please log in as guest with password guest if prompted)
0.9.8 is no longer supported by OpenSSL. So I am posting in this forum.
Can you guys help me o
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Salz, Rich
> Sent: Thursday, June 23, 2016 06:14
> To: openssl-users@openssl.org
> Cc: Dominik Straßer
> Subject: Re: [openssl-users] openssl shared libs
>
Mirko Fit (mirko@onespin.com) wrote:
> > Now my company
Look at Intel SGX, available since Skylake CPU.
Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
Original Message
From: Salz, Rich
Sent: Thursday, June 23, 2016 08:17
To: openssl-users@openssl.org
Reply To: openssl-users@openssl.org
Cc: Dominik Straßer
Subject: Re:
> Now my company is (T) and we don't want to leak (V)'s session key.
> You may assume that our binary is protected state of the art agains debugger
> attacks and stuff.
> So the only question is if the shared openssl library makes the tool more
> vulnerable?
You cannot prevent someone from chan
Here's my scenario in detail:
We have 3 parties:
(V) Vendor of intellectual property
(U) User of intellectual property (may not see the IP, but use it with
some tools and see the output)
(T) Tool provider (may decipher the IP and use it, but not show it to (U))
According to IEEE-1735 we do the
11 matches
Mail list logo
