** Reply to note from "Konstantin Sharenkov via RT" <[EMAIL PROTECTED]> Wed, 26
Oct 2005 11:36:41 +0200 (METDST)
Hi,
> but nt.mak contins line
>
> CFLAG= /MD /Ox /O2 /Ob2 /W3 /WX /Gs0 /GF /Gy /nologo
> -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIAN -DDSO_WIN32
> -D_CRT_SECURE_N
Hi,
> Then when the dynamic linker looks for a symbol, it looks at it
> by name. It will go over all objects to see if it exists in it.
> It will use the symbol from the first library it finds it in.
>
> This means, that a symbol that libA requires, and _should_ get
> from libssl.so.0.9.7
On Fri, Oct 28, 2005 at 09:46:30AM +0200, Andy Polyakov wrote:
>
> Now question to Johnny Lam [who is complaining that we don't bump
> versions] and Christoph Martin [who suggests to add versioning on all
> symbols]. What exactly didn't work for you? As far as I understand both
> NetBSD and Deb
andy,
> (2)
> after install, note:
>
>
> for v0.9.8a:
> otool -L libssl.dylib:
> libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
> libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version
> 0.9.8)
> /usr/local/lib/libgmp.3.dylib (compatibility
Yes, there are two different libubsec.so libraries:
1) The one built in OpenSSL with "./config shared"; this
is the stub library that contains "bind_engine", etc.
2) The one provided by the Broadcom SDK; this is the actual
library that contains "ubsec_bits_to_bytes", etc.
If I pu
Hello,
I have noticed that BIO_do_connect doesn't start the connection upon
call, instead the connection is established on the first BIO_puts, in
my case.
I am not sure if this is a bug or not, but I have traced it to
bss_conn.c, function conn_ctrl, line 470:
--- snip ---
case BIO_C_DO_STATE_MACH
openssl s_server command outputs to stdout messages, indicating current
state of server, such as "ACCEPT", "DONE", "ERROR".
When s_server is run interactively, these messages appear on the console
in time, and user can see it.
But, when s_server is run from some other process via pipe, standard
>>>I've got a segmentation fault in openssl-0.9.8a.
>>>../util/shlib_wrap.sh ./sha512t
>>>make[2]: *** [test_sha] Illegal instruction
>>
>>It's not considered to be bug, but a feature. As documented in FAQ.
>
> It seems to me that it would be better to improve automatic detection
> (for example,
Greetings!
On Fri, 28 Oct 2005, Andy Polyakov via RT wrote:
>
> > I've got a segmentation fault in openssl-0.9.8a.
> > ../util/shlib_wrap.sh ./sha512t
> > make[2]: *** [test_sha] Illegal instruction
>
> It's not considered to be bug, but a feature. As documented in FAQ.
I'm sorry. It's my fault.
Greetings!
I have a question on RAND_pseudo_bytes() semantics.
We've written an engine with our own RAND_METHOD. Our random number
generator is able to return both cryptographically strong data and
cryptographically weak data. Our RNG is able to provide
cryptographically weak data much more faste
> I've got a segmentation fault in openssl-0.9.8a.
> ../util/shlib_wrap.sh ./sha512t
> make[2]: *** [test_sha] Illegal instruction
It's not considered to be bug, but a feature. As documented in FAQ.
> OpenSSL self-test report:
>
> OpenSSL version: 0.9.8a
> Last change: Remove the function
> Probably this is an issue of configuration script. The engine/Makefile
> cannot handle dynamic libraries with HP's .sl extension. In the
> makefile, on the "library:" section, there is even a note reading:
>
> # X This currently only works on systems that use .so as suffix
> # for shared li
> 'make install' fails @
>
> ...
> making install in engines...
> installing 4758cca
> cp: lib4758cca.so: No such file or directory
> ...
> make[1]: *** [install] Error 1
> make: *** [install_sw] Error 1
>
> since ...
>
> ls ./engines/*.dylib
>
Please note that there is explicit question to couple of subscribers
posed in this message. Others should feel free to correct and complement.
Right now, we have it depend on the version number. An please tell
what the correct format for a soname is. On some Unixen, it seems
like the correct
14 matches
Mail list logo
