Regarding interoperability between no-asm and asm enabled

Hi, I am using 'DTLS over SCTP' and the OpenSSL version is 1.1.1c. I compiled OpenSSL with target 'linux-arm64ilp32' on armv8. GCC used is aarch64_be_linux-gnuilp32-gcc. So it is ILP32 and Big-end. I compiled two sets of OpenSSL libraries: 1) OpenSSL with no-asm present 2) OpenSSL with no-asm

Does 'no-hw' compile option disables the effect of opening the ASM assembler instruction ?

Hi, If there is no 'no-asm' compile option while building the OpenSSL, then it enables the assembler instruction support for OpenSSL. Whether having 'no-hw' compile option disables the assembler instruction support in above case ? Rgds, Navi

Re: Regarding netinet/sctp.h inclusion in bss_dgram.c

0/2019 10:32, Matt Caswell wrote: > > > > > > On 15/10/2019 07:51, Naveen Shivanna wrote: > >> Hi, > >> > >> After adding 'enable-sctp' compile option, OpenSSL (DTLS) can work with > >> SCTP as transport. > >> > >> OpenSSL bss_d

Regarding netinet/sctp.h inclusion in bss_dgram.c

Hi, After adding 'enable-sctp' compile option, OpenSSL (DTLS) can work with SCTP as transport. OpenSSL bss_dgram.c file includes the kernel /netinet/sctp.h. We have our own custom SCTP implementation (also implements custom BIO METHODS, do not use the default methods), so we need to remove the

[no subject]

Hi, After adding 'enable-sctp' compile option, OpenSSL (DTLS) can work with SCTP as transport. OpenSSL bss_dgram.c file includes the kernel /netinet/sctp.h. We have our own custom SCTP implementation (also implements custom BIO METHODS, do not use the default methods), so we need to remove the