From: Kris Kennaway <[EMAIL PROTECTED]>
kris> Could you give me a pointer to the patch? I'd like to fix this, and we
kris> won't be bringing 0.9.6 into 4.1-STABLE for a month or so.
http://www.openssl.org/source/cvs/crypto/evp/encode.c.diff?r1=1.8&r2=1.9&hideattic=1&sortbydate=0
If that doesn't
From: zhu qun-ying <[EMAIL PROTECTED]>
qyzhu> Error build under NT 4, VC6
qyzhu>
qyzhu> cl /Fotmp32dll\rand_win.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox /O2
qyzhu> /Ob2 /Gs0 /GF /Gy /nologo -DWIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIAN -DBN_ASM -DMD
qyzhu> 5_ASM -DSHA1_ASM -DRMD160_ASM /Fd
> Error build under NT 4, VC6
>
> cl /Fotmp32dll\rand_win.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox /O2
> /Ob2 /Gs0 /GF /Gy /nologo -DWIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIAN -DBN_ASM -DMD
> 5_ASM -DSHA1_ASM -DRMD160_ASM /Fdout32dll /GD -D_WINDLL -D_DLL -c .\crypto\rand
> \rand_win.c
> r
> That should teach me to put in new code... It seems like the include
> files that come with VC6 do not have LMSTR. Instead, the type name is
> LPTSTR, and the strings should *not* be preceded by a L.
Ah, I see. Microsoft changed the header between VC6 and the platform
SDK. The MSDN docs des
From: Jeffrey Altman <[EMAIL PROTECTED]>
Subject: Re: ANNOUNCE: OpenSSL 0.9.6 Beta 2
Date: Mon, 18 Sep 2000 7:23:01 EDT
Message-ID: <[EMAIL PROTECTED]>
jaltman> > Error build under NT 4, VC6
jaltman> >
jaltman> > cl /Fotmp32dll\rand_win.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox
/O2
ja
Sun ultra-5 with solaris 2.6
OpenSSL 0.9.6-beta2 17 Sep 2000
built on: Mon Sep 18 10:38:15 GMT 2000
platform: solaris-sparcv9-gcc
options: bn(64,32) md2(int) rc4(ptr,char) des(idx,cisc,16,long)
idea(int) blowfish(ptr)
compiler: gcc -fPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-mcpu=ul
OpenSSL 0.9.6-beta2 17 Sep 2000
built on: Mon Sep 18 19:52:26 SGT 2000
platform: solaris-sparcv9-gcc
options: bn(64,32) md2(int) rc4(ptr,char) des(idx,cisc,16,long) idea(int) blowf
ish(ptr)
compiler: gcc -fPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -mcpu=ultr
asparc -O3 -fomit-frame-po
fyi... redhat linux 5.2 on a 486sx - note that the build on this same
machine was successful for beta1
cheers,
Sean
==
[sean@esme openssl-0.9.6-beta2]$ ./config
Operating system: i486-whatever-linux2
Configuring for linux-elf
IsWindows=0
CC=gcc
CFLAG =-fPI
From: zhu qun-ying <[EMAIL PROTECTED]>
qyzhu> cc -I.. -I../../include -KPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-xtarget=ultra -xarch=v8plus -xO5 -xstrconst -xdepend -Xa -DB_ENDIAN -DBN_DIV2W
-DULTRASPARC -DMD5_ASM -DMD5_BLOCK_DATA_ORDER -c \
qyzhu> -o asm/md5-sparcv8plus.
Richard Levitte - VMS Whacker wrote:
> Very odd. Yes, if those -x switches were illegal, the compiler is
> probably old. But I find it really off that asm/md5-sparcv8plus.o
> didn't get built. Could you check if you got it or md5-sparcv9.o
> somewhere at all?
No. the file fail to compiled. :
From: Lutz Jaenicke <[EMAIL PROTECTED]>
Lutz.Jaenicke> On Sun, Sep 17, 2000 at 11:51:55PM +0200, Richard Levitte wrote:
Lutz.Jaenicke> > Also, new (non-default) targets for HP-UX have been added. Since
Lutz.Jaenicke> > they are non-default, they won't get chosen implicitely, so they
Lutz.Jae
On Mon, Sep 18, 2000 at 05:03:24PM +0200, Richard Levitte - VMS Whacker wrote:
> Lutz.Jaenicke> Provided the "-ldld" change is applied to "Configure",
> Lutz.Jaenicke> I have success for HP-UX 10.20 (which is only 32 bits)
> Lutz.Jaenicke> for the appended configurations (gcc is 2.95.2).
>
> Cool
Subject: Invest $25 to get $500,000 in every 4 to 5 months!!
Dear Friend:
AS SEEN ON NATIONAL TV :
''Making over half million dollars every 4 to 5 months
from your
home for an investment of only $25 U.S. Dollars expense
one
time''
THANX TO THE CO
Hi!
I have just finished some manual pages about SSL_CIPHER handling to be
added to doc/ssl.
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik
Hi there,
I've been able to run the tests of 0.9.6 beta 2 for a couple of
platforms not listed in the status file yet. The results are below:
OSF/1 5.0A
--
OpenSSL 0.9.6-beta2 [engine] 17 Sep 2000
built on: Mon Sep 18 15:32:13 BST 2000
platform: alpha-cc
options: bn(64,64) md2(int) rc4(
Isn't this contributing by a US citizen? ;-)
--
Peter 'Luna' Runestig (fd. Altberg), Sweden <[EMAIL PROTECTED]>
PGP Key ID: 0xD07BBE13
Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13
AOL Instant Messenger Screenname: PRunestig
_
On Sat, Sep 16, 2000 at 09:48:36PM -0400, Bodo Moeller wrote:
> Do connections between s_server (using default DH parameters)
> and s_client work on that platform, using 'openssl s_server'
> from the previous OpenSSL installation and 'openssl s_client'
> from the new one (without that patch, of co
> From: Francesco Gennai <[EMAIL PROTECTED]>
> Francesco.Gennai> If you means just to donwload and build the "engine"
> Francesco.Gennai> kit, then yes I can do it !
Ok,
I have successfully built the "engine" kit.
There is only one warning in a module during comiplation phase,
but I don't remebe
i believe i have found a bug in BF_cbc_encrypt() in 0.9.5a.
still not sure if it was repaired in 0.9.6beta2, i hope to test
this with 0.9.6beta2 sooner (if you can, please).
from cbc definition:
P1 P2 Pi
I've had some time to start looking at the engine code, and the first
thing I notice is that the various engines fill in the functions they
don't provide by getting hold of the "standard" engine, and copying them
across. It seems to me that this isn't very future-proof - what we
really want is for
> i believe i have found a bug in BF_cbc_encrypt() in 0.9.5a.
> still not sure if it was repaired in 0.9.6beta2, i hope to test
> this with 0.9.6beta2 sooner (if you can, please).
>
> from cbc definition:
>
>P1 P2 Pi
>
> as far as I understand, the problem is rather severe.
> - the problem is still present in 0.9.6beta2.
> - the issue with blowfish will be present for little endian machines
> (like i386). the source of the problem is the (mis)use lf
> n2l()/l2n() in bf_cbc.c.
Hi,
here's a code at 0.9.5a apps/pkcs12.c print_attribs()
case V_ASN1_OCTET_STRING:
hex_prin(out, av->value.bit_string->data,
probably it can be fixed easy
thanx for great tool,
Vadim
__
OpenSSL Project
>> as far as I understand, the problem is rather severe.
>> - the problem is still present in 0.9.6beta2.
>> - the issue with blowfish will be present for little endian machines
>>(like i386). the source of the problem is the (mis)use lf
>>n2l()/l2n() in bf_cbc.c.
Test passed on Slackware 7.0 (kernel 2.2.17)
OpenSSL 0.9.6-beta2 17 Sep 2000
built on: Mon Sep 18 23:14:24 SGT 2000
platform: linux-elf
options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) idea(int)
blowfish(idx)
compiler: gcc -fPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
for Mingw32 under NT:
It fails at this stage after using the new rand_win.c, the same place that fail
on beta1.
... ...
ranlib out/libcrypto.a
(cd ./..; PERL=perl make -f Makefile.ssl asm/lib.cpp)
make[1]: Makefile.ssl: No such file or directory
make[1]: *** No rule to make target `Makefile.ssl'.
On Mon, Sep 18, 2000 at 07:06:50PM +0200, Lutz Jaenicke wrote:
> On Sat, Sep 16, 2000 at 09:48:36PM -0400, Bodo Moeller wrote:
>> Do connections between s_server (using default DH parameters)
>> and s_client work on that platform, using 'openssl s_server'
>> from the previous OpenSSL installation
From: Jun-ichiro itojun Hagino <[EMAIL PROTECTED]>
itojun> cbc test vector on
itojun> http://www.counterpane.com/vectors.txt
itojun> was generated with the above setting (little-endian
itojun> machine, ssleay code) and looks incorrect to me.
Let's see, you seem t
>itojun>cbc test vector on
>itojun>http://www.counterpane.com/vectors.txt
>itojun>was generated with the above setting (little-endian
>itojun>machine, ssleay code) and looks incorrect to me.
>Let's see, you seem to be saying that the test vectors that
>Cou
From: [EMAIL PROTECTED]
itojun> i see (checked original blowfish paper)...
itojun> BF_encrypt() takes host byteorder values, while most
itojun> of the other algorithms takes values in network
itojun> byteorder. it makes it very hard to use BF_encrypt()
itojun>
>I've now extended blowfish.pod to be a little bit more informative on
>the quirks of BF_encrypt() and BF_decrypt().
thanks, that helps.
itojun
__
OpenSSL Project http://www.openssl.org
D
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> The compilation is currently running, but I have
Francesco.Gennai> already received an Informational and Fatal messages
Francesco.Gennai> (see the attached file).
Francesco.Gennai>
Francesco.Gennai> System data:
Francesco.Gennai> Alph
> From: Francesco Gennai <[EMAIL PROTECTED]>
> Francesco.Gennai> The compilation is currently running, but I have
> Francesco.Gennai> already received an Informational and Fatal messages
> Francesco.Gennai> (see the attached file).
> Francesco.Gennai>
> Francesco.Gennai> System data:
> Francesco.
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> > @MAKEVMS ALL NORSAREF NODEBUG DECC "" UCX
Oops, my mistake, take away the double quote:
@MAKEVMS ALL NORSAREF NODEBUG DECC UCX
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> %COPY-E-OPENIN, error opening
$4$DKB201:[OPENSSL.OPENSSL-0_9_6-BETA2.CRYPTO.ENGI
Francesco.Gennai> NE]ENGINE.H; as input
Francesco.Gennai> -RMS-E-DNF, directory not found
Francesco.Gennai> -SYSTEM-W-NOSUCHFILE, no such file
Francesco.G
> From: Francesco Gennai <[EMAIL PROTECTED]>
> Francesco.Gennai> %COPY-E-OPENIN, error opening
>$4$DKB201:[OPENSSL.OPENSSL-0_9_6-BETA2.CRYPTO.ENGI
> Francesco.Gennai> NE]ENGINE.H; as input
> Francesco.Gennai> -RMS-E-DNF, directory not found
> Francesco.Gennai> -SYSTEM-W-NOSUCHFILE, no such file
> From: Francesco Gennai <[EMAIL PROTECTED]>
> Francesco.Gennai> %COPY-E-OPENIN, error opening
>$4$DKB201:[OPENSSL.OPENSSL-0_9_6-BETA2.CRYPTO.ENGI
> Francesco.Gennai> NE]ENGINE.H; as input
> Francesco.Gennai> -RMS-E-DNF, directory not found
> Francesco.Gennai> -SYSTEM-W-NOSUCHFILE, no such file
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> I'm sorry but I don't think to have an environment for such test
Francesco.Gennai> (if I have understood the engine pourpose).
Francesco.Gennai> I have no crypto-card.
You don't have to. The engine dist has extra code that supports
ex
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> If you means just to donwload and build the "engine"
Francesco.Gennai> kit, then yes I can do it !
That's what I meant.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26
On Sun, 17 Sep 2000, Richard Levitte wrote:
>
> OpenSSL version 0.9.6 Beta 2
>
>
> OpenSSL - The Open Source toolkit for SSL/TLS
> http://www.openssl.org/
>
> OpenSSL is currently in a release cycle. The second beta is now released.
[snip]
>
It would b
From: Francesco Gennai <[EMAIL PROTECTED]>
Francesco.Gennai> My first problem is the change in the output of X509 command.
Francesco.Gennai>
Francesco.Gennai> I had the following call to the x509 command that worked fine
Francesco.Gennai> with openssl-0.9.5a
Francesco.Gennai>
Francesco.Gennai>
From: Tim Rice <[EMAIL PROTECTED]>
tim> It would be much eaiser to test and provide portability patches if
tim> openssl built outside of the source tree.
You can, if you play a little bit with soft links:
mkdir ../ossl-obj; cd ossl-obj
find ../openssl-0.9.6-beta2 -type f -print | \
while
On Mon, 18 Sep 2000, Richard Levitte - VMS Whacker wrote:
> From: Tim Rice <[EMAIL PROTECTED]>
>
> tim> It would be much eaiser to test and provide portability patches if
> tim> openssl built outside of the source tree.
>
> You can, if you play a little bit with soft links:
>
> mkdir ../ossl
Hi,
I am attempting to compile opensll (0.9.5a) by means of MetroWerk's
Codewarrior (CW) compiler.
The reason for this being that my company needs all software to run on both
Macintosh and Windoze, so everything is compiled with CW to reduce porting
overhead. (to my knowledge CW seems to be the o
44 matches
Mail list logo
