Stanislav Mikhailenko wrote:
CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON);
SSLeay_add_ssl_algorithms();
SSL_load_error_strings();
ERR_remove_state(0);
ERR_free_strings();
EVP_cleanup();
CRYPTO_cleanup_all_ex_data();
ENGINE_cleanup();
CONF_modules_unload(1);
This code
On Fri October 24 2008, David Schwartz wrote:
>
- - - -
>
> Notice how this assumes that if BIO_sock_error returns zero, the connection
> completed? This is a bogus inference. The absence of an error just means the
> connection attempt has not failed *yet* and tells you nothing about how it
> wil
Gabriel Soto wrote:
> {
> // Create BIO with some random nonexistent host.
> BIO *bio = BIO_new_connect("192.168.9.9:");
>
> if (bio == NULL) {
> // Failed to obtain BIO.
> return false;
> }
>
> // Set as non-blocking.
> BIO_set_nbio(bio, 1);
>
> //
==13777== 128 bytes in 1 blocks are still reachable in loss record 1 of 2
==13777==at 0x4004BEC: realloc (vg_replace_malloc.c:306)
==13777==by 0x8052515: default_realloc_ex (mem.c:86)
==13777==by 0x8052B3E: CRYPTO_realloc (mem.c:331)
==13777==by 0x8062B64: contract (lhash.c:369)
How can
I see which it is linked to?
look at apache error.log
also you can type:
ldd httpd (in bin) to see what libs it using.
When I configure apache I just indicate /usr/local/ssl/lib (which contains
both libssl.a and libssl.so).
do you mean: ./configure ... --enable-ssl --with-ssl=/usr/lo
http://packages.debian.org/search?keywords=openssl
the most recent in unstable is 0.9.8g
also i am using only etch stable. installing only this package 0.9.8g with
unstable will lead to upgrading libc, gcc etc...
pat
__
OpenSS
When I configure apache I just indicate /usr/local/ssl/lib (which contains
both libssl.a and libssl.so). I did not build mod_ssl separately. How can
I see which it is linked to?
Dan_Mitton-2 wrote:
>
> Doesn't this all depend on if you linked mod_ssl.so to the static SSL (.a)
> libraries or
Gabriel Soto wrote:
>
> Greetings.
> I'm a noob trying to code a simple TCP client (Windows, MinGW, OpenSSL
> 0.9.8g). Since it has a GUI, I have to go with non-blocking sockets.
>
> I'm supplying a nonexistent host to test a failure but this is what happens:
> A first call to connect returns natu
On Oct 21, 2008, at 9:12 AM, patrick wrote:
i am running debian etch stable. the version of openssl is too old.
what i did is to download
Are you sure? A lot of linux distro folks keep the upstream version
the same but backport fixes into their packages. An apt-get update /
apt-get up
On Fri October 24 2008, patrick wrote:
> hi mike,
>
> thank you very very much for taking the time to share your knowledge. here's
> the configuration of debian etch:
>
> ld.so.conf =
> include /etc/ld.so.conf.d/*.conf
>
> in ld.so.conf.d = i486-linux-gnu.conf
> # Multiarch support
> /lib/i486-
hi mike,
thank you very very much for taking the time to share your knowledge. here's
the configuration of debian etch:
ld.so.conf =
include /etc/ld.so.conf.d/*.conf
in ld.so.conf.d = i486-linux-gnu.conf
# Multiarch support
/lib/i486-linux-gnu
/usr/lib/i486-linux-gnu
i've put /usr/local/lib
On Thu October 23 2008, patrick wrote:
> hi all,
>
> it's now working (including apache / mod-ssl). i had to:
>
> --
> debian etch
> --
> openssl
> ./config --prefix=/usr/local --openssldir=/etc/ssl shared threads
>
> apache
> ./configure .. --enable-ssl --wit
Hi,
Iam having issue using SSL_connect() API when implementing an SSL client
application. The API fails returning -1 and the error it says is "VERIFY
err : 7 : certificate signature failure".
When I try using s_client using the same root CA, it works fine. I am not
able to understand what is the
hi all,
it's now working (including apache / mod-ssl). i had to:
--
debian etch
--
openssl
./config --prefix=/usr/local --openssldir=/etc/ssl shared threads
apache
./configure .. --enable-ssl --with-ssl=/usr/local
BUT i had to replace the libs in /usr/lib/i6
14 matches
Mail list logo
