[openssl.org #1494] Re: Openssl Installation Error
To Whom It May Concern: I tried to install the Openssl and failed on the make test step. Would you help me with the error message? Thanks, Lisa Tan, Lead Systems Integrator eServices Strategic Technologies Computing Information Technology Wayne State University 5925 Woodward Ave. Rm# 313 Detroit, MI 48202 Phone: 313-577-2561 Fax: 313-577-0431 Email: [EMAIL PROTECTED] To Whom It May Concern: I tried to install the Openssl and failed on the make test step. Would you help me with the error message? Thanks, Lisa Tan,Lead Systems Integrator eServices Strategic Technologies Computing Information Technology Wayne State University 5925 Woodward Ave. Rm# 313 Detroit, MI 48202 Phone: 313-577-2561 Fax: 313-577-0431 Email: [EMAIL PROTECTED] testlog Description: Binary data
Duplicate mail
Is there any chance that someone down at openssl.org can sort out the duplicate sent mail?! I am getting duplicates on both openssl-dev and openssl-users lists. Please please please Many thanks Constantin
Build of 0.9.8e fails in shared debug-linux-elf
Hi developers, I downloaded the new 0.9.8e and compiled it on various platforms. AIX, HP-UX, Solaris and Windows were ok (debug release), but it failed on (shared) debug-linux-elf in crypto/engine/eng_padlock.c. gcc -I.. -I../.. -I../../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DBN_DEBUG -DREF_CHECK -DCONF_DEBUG -DCRYPTO_MDEBUG -DL_ENDIAN -DTERMIO -g -march=i486 -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -c -o eng_padlock.o eng_padlock.c eng_padlock.c: In function `padlock_xcrypt_ecb': eng_padlock.c:445: error: can't find a register in class `GENERAL_REGS' while reloading `asm' make[3]: *** [eng_padlock.o] Error 1 I configured with: ./Configure shared threads no-idea no-rc5 debug-linux-elf gcc: gcc version 3.3.3 (SuSE Linux) This happens only in debug-mode, release is ok. The only difference in the configuration is that release has -O3 -fomit-frame-pointer, whereas debug has -g -march=i486 Changing -march to i386 or pentium doesn't change the result. can't find a register in class `GENERAL_REGS' while reloading `asm' seems to indicate the the compiler doesn't find enough registers in the CPU to use with given inline-assembler-code. Any Idea how to fix that? Kind regards Robert Robert Lill Engineering Archive + Storage Security Consultant Open Text Werner-von-Siemens-Ring 20 85630 Grasbrunn GERMANY Phone: +49-89-4629-1526 Telefax:+49-89-4629-33-1526 eMail: mailto:[EMAIL PROTECTED] Internet: http://www.opentext.com __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
SSL_CTX_new: No such file or directory
Greetings.
I am getting this error and am trying to find any info that could help
me get past it.
Relevant code snippet:
if(!(d-ssl_ctx=SSL_CTX_new(SSLv23_server_method(
{
perror(SSL_CTX_new:);
}
Error I get:
SSL_CTX_new:: No such file or directory
Do you know why I would get such an error. I had the application
working fine with openssl-0.9.6 and this error started appearing after
I started using openssl-0.9.8c
Thanks for the help !!!
Thomas
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
Re: SSL_CTX_new: No such file or directory
I am getting this error and am trying to find any info that could help
me get past it.
Relevant code snippet:
if(!(d-ssl_ctx=SSL_CTX_new(SSLv23_server_method(
{
perror(SSL_CTX_new:);
}
Error I get:
SSL_CTX_new:: No such file or directory
You should probably be using the openssl-users mailing list, not -dev.
Next, the proper way to grab an openssl error would be something
like this:
char error[255];
unsigned long err;
err = ERR_get_error();
ERR_error_string_n(err, error, sizeof(error));
printf(SSL_CTX_new: %s\n, error);
OpenSSL doesn't use the system errno.
-Brad
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
Problem with check_purpose_ssl_client
Hello, Currently, /check_purpose_ssl_client/ calls /ns_reject /with the flag NS_SSL_CLIENT: *if(ns_reject(x, NS_SSL_CLIENT)) return 0;* Because of that, if a certificate has Netscape S/MIME bit set, but not SSL Client, certificate validation fails. Shouldn't the S/MIME bit considered sufficient on its own in client certificates? In this case the call should be: *if(ns_reject(x, (NS_SSL_CLIENT | NS_SMIME))) return 0;*/ /Regards, Michael/ /
