Kinichiro Inoguchi

>If it don't include Plan 9 C compiler outputs some errors like: > ... >Yes. Plan 9 C compiler makes an error if it find type mismatch; pointer to signed...

@lufia, I have one question (not forcing) for this PR. Are you thinking about build from tarball (.tar.gz) ? This PR seems that it enables building from git repository, but...

@lufia Makefile.am "EXTRA_DIST" is used to include files into tarball.

Verification for chain of certs is done while handshake phase, and I don't think libtls has the way to show it. Not by API though, you can use openssl s_client...

OpenSSL 1.0.2 (already EOS, though) exits with status 0, too. This behavior appears to remain since OpenSSL 1.0.1. Here is the log by OpenSSL 1.0.2t. ``` $ eopenssl version OpenSSL...

In this case, command shows error message since Public Key Algorithm value is invalid. But it displays the rest of information in spite of after detecting that bad value. Command...

Hi, Can you try to edit openssl/ocsp.h like below, before building test.c ? ``` //extern const ASN1_ITEM OCSP_BASICRESP_it; _declspec(dllimport) ASN1_ITEM OCSP_BASICRESP_it; ``` Also, you need to replace the include files...

Thanks for your confirmation. This seems Windows specific issue, and this doesn't affect to other platforms. I had already tried to see test.c runs fine on Fedora. To solve this...

After "TLS 1.2 Handshake [length 0010], Finished", you had write:errno=54 (Connection reset by peer). On my fedora28 with libressl 2.8.0, I didn't see any error with s_client, like below. ```...

Same kind of issue #515 was caused by security tool.