If GSCheck is just a tool to check if you remembered to build
code with the buffer overflow checks that Microsoft C can
insert, then you should just treat this as a warning that the
tool doesn't know how to check code from other compilers (in
this case the manual work of the OpenSSL team).
On
> The 32bit OpenSSL 1.1.0i library 'libeay32.dll' fails for
> binscope GSCheck on Windows.
This must be a customised non-standard library, since 1.1.0 does not
build with that name, but as libcrypto-1_1.dll.
Angus
--
openssl-users mailing list
To unsubscribe:
I thibk those are all the .asm modules. If they are, you'll probably want
to Configure with no-asm and rebuild in order to get the C implementations.
-Kyle H
On Wed, Nov 28, 2018, 01:07 Vinay Kumar via openssl-users <
openssl-users@openssl.org wrote:
> Hi All,
>
> The 32bit OpenSSL 1.1.0i
Hi All,
The 32bit OpenSSL 1.1.0i library 'libeay32.dll' fails for binscope GSCheck on
Windows.
E:\libeay32.dll: error BA2022: libeay32.dll was compiled with the following
modules for which a language could not be identified. Ensure these were
compiled with debug information and run BinScope
