Hi,
Since the upgrade from 0.9.7g to 0.9.8a on Debian, we're getting
alot of bug reports about applictions that give an error that
they can't load zlib.so.
When calling SSL_library_init(), it will try to load zlib.so,
which doesn't have to exist. It should try to open zlib.so.1
instead because
[EMAIL PROTECTED] - Tue Nov 1 10:15:07 2005]:
The fix is:
s/chop/chomp/
I don't agree, as chomp won't take away the ending space when the
variable does get a value. Try the following patch for size and tell
me how that worked for you:
cvs diff: Diffing util
Index: util/mk1mf.pl
On Tue, Nov 01, 2005 at 10:18:42AM +0100, Kurt Roeckx via RT wrote:
So this looks like an error that doesn't get cleared, and I have
to wonder who should clear it. I don't think COMP_zlib() should
return that it was actually succesful in opening the library,
so it should atleast return
Andy Polyakov wrote:
Could be. But should it be run automatically
during make? I guess no...
No, but I'd like to *see* some test program and I'd like to hear
explicit statement that the implementation passes this test. As you
might recall we have tested AES by encypting with software and
[guest - Wed Oct 19 12:58:28 2005]:
[EMAIL PROTECTED] - Wed Oct 19 11:47:39 2005]:
On a SuSE 9.0 machine, however, with gcc 3.3.1 and glibc 2.3.2 make
test deadlocks after:
The following command should have some OK's and some failures
There are definitly a few expired certificates
[Code and binaries can be downloaded from
http://www.it.uc3m.es/pervasive/wce_lite_compat/ ]
This patch makes some fixes to the last OpenSSL official version 0.9.8a.
First of all you have to realize that we're reluctant to accept
functional patches to released code. Meaning that if you want
Could be. But should it be run automatically
during make? I guess no...
No, but I'd like to *see* some test program and I'd like to hear
explicit statement that the implementation passes this test. As you
might recall we have tested AES by encypting with software and
decrypting with engine and
via RT wrote:
...
On a SuSE 9.0 machine, however, with gcc 3.3.1 and glibc 2.3.2 make
test deadlocks after:
The following command should have some OK's and some failures
There are definitly a few expired certificates
../util/shlib_wrap.sh ../apps/openssl verify -CApath ../certs
I'll change a few bits in this patch (make sure to open the console, not stdin)
and make a small adjustment to make source changes count for m68k-amigaos as
well
(the clib I use is available for those OS versions too, it seems) so there's
no rush.
--
Johan Gill, [EMAIL PROTECTED]
Your patch corrected the problem, thank you On 01-Nov-05 at 2:29 am, in message [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] - Tue Nov 1 10:15:07 2005]: The fix is: s/chop/chomp/I don't agree, as chomp won't take away the ending space when the variable does get a value. Try the
Your patch corrected the problem, thank you
On 01-Nov-05 at 2:29 am, in message
[EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] - Tue Nov 1 10:15:07 2005]:
The fix is:
s/chop/chomp/
I don't agree, as chomp won't take away the ending space when the
variable does get a
Ted Mittelstaedt schrieb:
From: Christoph Martin [EMAIL PROTECTED]
openssl has evolved to a very important library in Linux distribution. A
lot of cryptographic applications link to it including system libraries
like pam modules and apache modules. Now it becomes more and more
difficult to get
Hi
The latest code crashes on Solaris Intel 5.8, this is the log output of
compilation.
making all in engines...
gmake[4]: Entering directory
`/home/srbpkg/srbpkg/ssl/32/openssl-0.9.8a/engines'
gmake[4]: Nothing to be done for `all'.
gmake[4]: Leaving directory
Johan Gill wrote:
I'll change a few bits in this patch (make sure to open the console, not stdin)
and make a small adjustment to make source changes count for m68k-amigaos as
well
(the clib I use is available for those OS versions too, it seems) so there's
no rush.
Is anyone still using m68k
The approach I took with wcecompat and integration with OpenSSL was to make
OpenSSL have as little special knowledge of CE as possible. This means that
wcecompat emulates missing ANSI/Posix functionality so that OpenSSL simply
continues to program to the standard interfaces. Wcecompat should be
The approach I took with wcecompat and integration with OpenSSL was to make
OpenSSL have as little special knowledge of CE as possible.
And my suggestion is to identify unnecessary code in given context and
instead of striving for patching holes, just eliminate the redundant
code. E.g. [at
Hi Martin,
Comments inline.
On October 28, 2005 09:54 am, Martin Del Vecchio wrote:
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
Sam,
What happens when you put the directive no-asm for config?
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of sharma via RT
Sent: Tuesday, November 01, 2005 11:31 AM
Cc: openssl-dev@openssl.org
Subject: RE: [openssl.org #1190] bug report
Hi
The
18 matches
Mail list logo
