Re: [openssl-users] openssl ca pkcs11 UI_set_result_ex:result too large:crypto/ui/ui_lib.c:910:You must type in 4 to 32 characters

2018-10-18 Thread Peter Magnusson
Thanks =) This is similar to other commands, e.g. ssh, tpm2-tools, etc inconsistencies between different flags between different sub-commands. Getting it right the first time is easier said than done and changing command line behaviour later on breaks user scripts etc. //P On Wed, Oct 17, 2018 a

Re: [openssl-users] Openssl Build Error- module unsafe for SAFESEH image/Unable to generate SAFESEH image

2018-10-18 Thread Jakob Bohm via openssl-users
SAFESEH requires any code that sets up Win32/i386 SEH handlers to include special assembler directives to add the handler code address to a special list which the linker then puts in the compiled program for the Windows runtime (NTDLL.DLL etc.) to check to make sure it is only calling back to your

Re: [openssl-users] no-async needs -DOPENSSL_NO_ASYNC nonetheless?

2018-10-18 Thread Steffen Nurpmeso
Matt Caswell wrote in : |On 17/10/2018 22:07, Steffen Nurpmeso wrote: |>| |>|This is definitely an environmental issue. I just installed an Alpine |>|Linux VM. I got the above error consistently when using clang as the |>|compiler (whether or not I added "-DOPENSSL_NO_ASYNC"). I got a |>|succ

Re: [openssl-users] Openssl Build Error- module unsafe for SAFESEH image/Unable to generate SAFESEH image

2018-10-18 Thread sakdev
Thanks for reply Michael. I am sure i gave 32-bit build only. "BuildWinLibs.bat vs2015 x32d clean" This is the comment i gave for build. Here "x32r" means 32-bit release build. Here is the error code(text). rc /fo"tmp32dll/MSVC14.0\libeay32.res" /d CRYPTO ms\version32.rc Microsoft (R)

Re: [openssl-users] Openssl Build Error- module unsafe for SAFESEH image/Unable to generate SAFESEH image

2018-10-18 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of sakdev > Sent: Thursday, October 18, 2018 06:09 > > To resolve this we added /SAFESEH flag in linker flags, and started build. > But build got failed with "Unable to generate SAFESEH image" error. You appear to have ad

[openssl-users] Manually checking against ocsp.comodoca.com producess an error

2018-10-18 Thread Усманов Азат Анварович
Hi! I'm trying to manually check ocsp with ocsp utility with OpenSSL 1.1.1 ,I'm receiving an error openssl version OpenSSL 1.1.1 11 Sep 2018 openssl ocsp -no_nonce -header Host=ocsp.comodoca.com -issuer issuer.crt -cert /home/idis/STAR_ieml_ru.crt -url http://ocsp.comodoca.com/ -CAfile issu

[openssl-users] Openssl Build Error- module unsafe for SAFESEH image/Unable to generate SAFESEH image

2018-10-18 Thread sakdev
Hi, We are using openssl-1.0.2j. For security compliance we scanned libeay32.dll with binscope binary analyzer. Binscope result is showing *“SafeSEHCheck (FAIL)”*. To resolve this we added /SAFESEH flag in linker flags, and started build. But build got failed with "Unable to generate SAFESEH ima