On Mon, Aug 17, 2015, Patil, Ashwini IN BLR STS via RT wrote:
Hi Mr. Stephen N. Henson,
Thankyou so much for the reply.
We would like to use the option1 mentioned by you. But unfortunately the
dll's were not generated, only static lib's were generated.
Please guide if we have
On Mon, Aug 17, 2015, Patil, Ashwini IN BLR STS via RT wrote:
Hi Mr. Stephen N. Henson,
Thankyou so much for the reply.
We would like to use the option1 mentioned by you. But unfortunately the
dll's were not generated, only static lib's were generated.
Please guide if we have
Hi Mr.Henson,
Thankyou so much.
But when nmake -f ms\nt.mak command was given below static libs where
successfully generated.
m. Compiled FIPS compliant OpenSSL fipslibeay32.lib, ssleay32.lib
libeaycompat32.lib are located at C:\openssl-1.0.2c-fips-compliant\out32
But when
Hi Mr.Henson,
Thankyou so much.
But when nmake -f ms\nt.mak command was given below static libs where
successfully generated.
m. Compiled FIPS compliant OpenSSL fipslibeay32.lib, ssleay32.lib
libeaycompat32.lib are located at C:\openssl-1.0.2c-fips-compliant\out32
But when
On Mon, Aug 17, 2015, Patil, Ashwini IN BLR STS wrote:
Please let me know if I need to make changes in ntdll.mak file to generate
the corresponding fipslibeay32.dll .
As I need to include this dll in my test application to turn on the fips
module.
There is no fipsleay32.dll
--On Wednesday, August 05, 2015 5:54 PM +0200 Kurt Roeckx k...@roeckx.be
wrote:
On Wed, Aug 05, 2015 at 06:54:33AM -0700, Quanah Gibson-Mount wrote:
Yesterday, I was alerted by a member of the list that my emails to
openssl-dev are ending up in their SPAM folder. After examining my
emails as
The ciphers man page contains the following text in the description of the
SUITEB cipher strings:
If used these cipherstrings[sic] should appear first in the cipher list
and anything after them is ignored.
In actual fact, if anything appears after them, they are completely ignored.
On Fri, Jul 31, 2015 at 05:37:20PM +, Viktor Dukhovni wrote:
Which ciphers are actually needed by PSK users? My hope is that
at this point RC4 and 3DES are not. It is highly likely that CBC
AES-CBC is needed, perhaps also Camellia, but the question is I
think worth asking.
So what's
TLS_RSA_PSK_WITH_RC4_128_SHA RSA-PSK-RC4-SHA
TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA RSA-PSK-3DES-EDE-CBC-
SHA
Remove.
On a related note (for those also reading the TLS WG list), any thoughts on
deprecating any or all of the kDHr, kDHd, kECDHr, kECDHe ciphers?
Hi Mr. Stephen N. Henson,
Thankyou so much for the reply.
We would like to use the option1 mentioned by you. But unfortunately the dll's
were not generated, only static lib's were generated.
Please guide if we have missed any steps.
=
Hi Mr. Stephen N. Henson,
Thankyou so much for the reply.
We would like to use the option1 mentioned by you. But unfortunately the dll's
were not generated, only static lib's were generated.
Please guide if we have missed any steps.
=
11 matches
Mail list logo
