This message addresses *all* users, rather than report originator alone.
openssl-0.9.7e's Makefile contains -notall for do_irix-shared. This
option is not understood by the SGI IRIX 5.3 IDO (IRIX development
option) cc. Later versions (SGI MIPSPRO) might be different.
Changing it into -none
Proposed change passes regression tests on IRIX 6.5, fix is commited to
0.9.7 and HEAD branches.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
New SHA implementations were introduced in 0.9.8 development branch.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List
Threading support for AIX appears in latest 0.9.7 [and HEAD] snapshots.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated
Support for hpux*-ia64-gcc appears first in 0.9.8 development branch.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated
AIX support was fixed/refined in latest 0.9.7 and HEAD branches.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List
You're hitting compiler bug. It's not OpenSSL problem...
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
It's merely cosmetics: .sl works as well as .so. The issue is addressed
in 0.9.8 development branch.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
[Andy Polyakov]
It's merely cosmetics: .sl works as well as .so. The issue is
addressed in 0.9.8 development branch.
Actually, when we try to get both hppa and ia64 binaries working, it
is important that the hppa libraries are called .so, and the i164
libraries are using .so. If not, the
It's an old [by now] compiler bug. If the problem persists, ask vendor
for patch or drop optimization level according to instructions in
INSTALL file.
__
OpenSSL Project http://www.openssl.org
This was fixed at some point...
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Submitted code is incorporated into development branch.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
This problem was fixed at some point.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
AIX issues were addressed in later 0.9.7 and HEAD branches.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Dismissed as non-reproducible.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Dismissed as partially non-reproducible and partially as fixed at other
occasions.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Resolved as duplicate of #963.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Fixed in latest 0.9.7 snapshots.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Fixed in latest 0.9.7 snapshots.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Duplicate of #942.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL
I'm sorry, but we can't possibly resolve local OS configuration
problems. perl: cannot execute is such problem and you should bring it
up with your system administator.
__
OpenSSL Project
Resolved as non-OpenSSL issue.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Dismissed as duplicate of #963.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
It's merely cosmetics: .sl works as well as .so. The issue is
addressed in 0.9.8 development branch.
Actually, when we try to get both hppa and ia64 binaries working, it
is important that the hppa libraries are called .so, and the i164
libraries are using .so. If not, the program will not
[Andy Polyakov]
Both pa-risc and ia64 linkers look for both .so and .sl and once program
is linked with some shared object it will require that particular one.
And at run-time shared object extension has no meaning whatsoever, it's
the contents matching ABI for current process, which
Both pa-risc and ia64 linkers look for both .so and .sl and once program
is linked with some shared object it will require that particular one.
And at run-time shared object extension has no meaning whatsoever, it's
the contents matching ABI for current process, which determines if any
[appro - Mon Dec 27 17:22:14 2004]:
Fixed in latest 0.9.7 snapshots.
Can you send me the URL to download the 0.9.7 snapshots. Also please
let me know the steps to install it.
thanks
srinivas
__
OpenSSL Project
Can you send me the URL to download the 0.9.7 snapshots. Also please
let me know the steps to install it.
Thanks
Srinivas
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Polyakov via
RT
Sent: Monday, December 27, 2004 11:22 AM
To: Seeda, Srinivas
i try to make a dgst of a 40Gb file, but when the openssl binary try to
fopen the file, it's fail ..
i think the problem was the fopen, maybe it's dont use the open (2) with
the option O_LARGEFILE..
can you fix it ?
Well, in certain sense it's by design. At the very least we try to
Formally this puts us, OpenSSL developers, in rather tight situation.
Indeed, as we can't possibly have access to *all* platforms OpenSSL can
or *could* be compiled at, statements like this solves my problem in my
out-of-date setup and I don't know how it affects others [who are most
I have encountered a problem when using openssl to encrypt binary files
on cygwin.
Here is how to reproduce the problem:
1) When you install cygwin, make sure that the format for text files is
set to DOS
2) Encrypt a binary file (e.g. a .zip file, let's call it file.zip):
openssl enc
Essentail parts of the report in question were apparently addressed at
earlier occasions.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
if you had not been, by chance, familiar with that particular platform,
you still could have replied with a brief mail asking me to figure it out.
My intend was to merely point out the issue to you developers. Maybe
I should have stated more explictly that of course if you needed further
I'm sorry, but we can't possibly resolve all the crazy local OS
configuration problems. I mean this looks very much like problem with
your OS setup problem and you really be better talking to your system
administator.
__
OpenSSL
Your problem is most likely has everything to do with the fact that your
working directory is mounted textmode. If it's mounted binmode, then
it's still most likely your local cygwin setup/configuration problem, as
I can't reproduce the problem. The latter means that you should rather
bring it up
The issue was resolved at openssl-dev, outside RT.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Your problem is most likely has everything to do with the fact that your
working directory is mounted textmode. If it's mounted binmode, then
it's still most likely your local cygwin setup/configuration problem, as
I can't reproduce the problem. The latter means that you should rather
bring it up
Dismissed as duplicate of #963.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Essential parts of report are addressed in latest snapshot.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
On Thu, 23 Dec 2004, Andy Polyakov wrote:
aes-586.pl module is committed to CVS now [see
http://cvs.openssl.org/rlog?f=openssl/crypto/aes/asm/aes-586.pl]. Take
Special note about instruction choice in commentary section for
consideration even for AMD64. Merry Christmas to everybody:-) A.
Hey, if you don't have a clue, just say so. I am the sys admin. Talking to
myself isn't really helpful. I worked around this problem long ago...The
original post to your (quite less than helpful) listserv was Sept 8th.
Nice response time!
JP
On 12/27/04 4:33 PM, Andy Polyakov via RT [EMAIL
41 matches
Mail list logo
