I'm trying to build openssl-1.0.2 for windows. I successfully built
win32 binaries, but I can't seem to build win64a. I get reasonably far
into the build, but then it fails doing AES nasm calls. Previous nasm
calls succeed.
FWIW, I was able to work around this by disabling asm entirely:
per
First I encountered problems here --
https://mta.openssl.org/pipermail/openssl-dev/2015-March/000806.html
Guessing if this's a openssl command related problem, but now I've
problems in code.
SSL_library_init();
SSL_load_error_strings();
const SSL_METHOD* meth;
meth = TLSv1_2_m
On 03/01/15 20:31, Kurt Roeckx wrote:
On Sun, Mar 01, 2015 at 08:12:25PM +0530, dE wrote:
On 03/01/15 20:07, Kurt Roeckx wrote:
On Sun, Mar 01, 2015 at 05:41:03PM +0530, dE wrote:
Hi!
gethostbyname failure
This probably means that you don't have localhost in /etc/hosts
127.0.0.1 DESKT
Hello,
I'm trying to build openssl-1.0.2 for windows. I successfully built
win32 binaries, but I can't seem to build win64a. I get reasonably far
into the build, but then it fails doing AES nasm calls. Previous nasm
calls succeed.
perl Configure VC-WIN64A --prefix=Output\Win64\Release
ms
Hi!
I am developing a software.
I want to use the OpenSSL ECDSA library to my software.
So, I would like to know if there is a legal problem using ECDSA in Openssl.
For example, patent issues, license etc.
Can I use ECDSA library without legal problem?
Please answ
This was due to a temporary issue on the openssl website. Should all be fixed
so closing this ticket.
Matt
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
