In addition to client authentication, another approach would be to use
TLS-SRP to protect against MITM. Without the SRP credentials, the
attacker would not be able to establish the two TLS connections required
for MITM.
On 03/11/2015 09:35 AM, Short, Todd via RT wrote:
This is more of a request
Hi,
While looking at the Configure script, I found that there is the armv4_asm
variable, which seems to promise a speedup for ARM architectures (and the 4
in ARMv4 sounds like it should work everywhere?).
However, further looking at that Configure file, I see it's only used for
In crypto/asn1/a_strex.c routine do_name_ex does not handle case 0 for
separators, this can occur if
one specifies a -nameopt utf8.
Suggested fix: Treat 0 in the same way as XN_FLAG_SEP_CPLUS_SP
___
openssl-dev mailing list
To unsubscribe:
Hi
I have downloaded the openssl 0.9.8zd source.
And I tried below steps to get it install.
1. ./config fipscanisterbuild
I did not get any configuration error.
2. make
I got the below linker error.
make[2]: Entering directory `/home/ratsa02/openssl-0.9.8zd/test'
I can't speak directly to your question on the iphone-cross target, but
can warn you that your mileage will vary when using the ARM assembly
modules. We observed that some algorithms actually run slower when
using the ARM assembly modules. It's been a couple of years and I don't
recall the
Hi,
While looking at the Configure script, I found that there is the
armv4_asm variable, which seems to promise a speedup for ARM
architectures (and the 4 in ARMv4 sounds like it should work
everywhere?).
Yes. v4 denotes only *minimal* requirement. There is conditionally
compiled code that
On Thu Mar 12 22:16:37 2015, santosh.r...@ca.com wrote:
Hi
I have downloaded the openssl 0.9.8zd source.
And I tried below steps to get it install.
1. ./config fipscanisterbuild
I did not get any configuration error.
2. make
I got the below linker error.
make[2]: Entering directory
