Thank you Richard,

I'm am testing 
openssl-1.0.0-stable-SNAP-20100127.tar.gz       3.8 MB  27/01/2010
06:15:00

It builds correctly.

During tests I go the following errors:

1. SSLROOT is not defined correctly

in <.test>tests.com sslroot definition is replaced

$      sslroot = f$parse("sys$disk:[-.apps];",,,,"syntax_only") - "].;"+
".]"
$      define /translation_attributes = concealed sslroot 'sslroot'

I have been forced to do it on more old fashioned way in order to get
this work

$       ROOT = F$PARSE(__here,"[]A.;0",,,"SYNTAX_ONLY,NO_CONCEAL") -
"A.;0"
$       ROOT_DEV = F$PARSE(ROOT,,,"DEVICE","SYNTAX_ONLY")
$       ROOT_DIR = F$PARSE(ROOT,,,"DIRECTORY","SYNTAX_ONLY") -
                   - ".][000000" - "[000000." - "][" - "[" - "]" -
".TEST"
$       ROOT = ROOT_DEV + "[" + ROOT_DIR
$       DEFINE/NOLOG SSLROOT 'ROOT'.APPS.] /TRANS=CONC


2. could not pass through this point... I have seen that earlier as
well, but now it can not find the seed file at all in the current
directory. 


2071080376:error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG
not seeded:USRDSK:[ZA
Y.WORK.OPENSSL-100-STABLE-SNAP-20100127.CRYPTO.RAND]MD_RAND.C;1:519:You
need to read the OpenSSL FAQ, http://www.openssl.o
rg/support/faq.html
2071080376:error:04088003:rsa routines:RSA_setup_blinding:BN
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100127.CRYPTO.
RSA]RSA_LIB.C;1:426:
2071080376:error:04066044:rsa routines:RSA_EAY_PRIVATE_ENCRYPT:internal
error:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-201
00127.CRYPTO.RSA]RSA_EAY.C;1:403:
2071080376:error:0D0C3006:asn1 encoding routines:ASN1_item_sign:EVP
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100127.
CRYPTO.ASN1]A_SIGN.C;1:279:

Do you have any idea what to do?

In fact there still exists all issues that I have sent in Monday
2010-01-25 19:59 

3. Manually started JPAKETEST fails!!!

TITAN2_ZAY $ mc
USRDSK:<ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100125.IA64.EXE.TEST>JPAKETES
T.EXE
p =
F9E5B365665EA7A05A9C534502780FEE6F1AB5BD4F49947FD036DBD7E905269AF46EF28B
0FC07487EE4F5D20FB3C0AF8E700F3A2FA3414970CBED4
4FEDFF80CE78D800F184BB82435D137AADA2C6C16523247930A63B85661D1FC817A51ACD
96168E95898A1F83A79FFB529368AA7833ABD1B0C3AEDDB14D
2E1A2F71D99F763F
g = 2
q =
7CF2D9B2B32F53D02D4E29A2813C07F7378D5ADEA7A4CA3FE81B6DEBF482934D7A377945
87E03A43F727AE907D9E057C738079D17D1A0A4B865F6A
27F6FFC0673C6C0078C25DC121AE89BD56D16360B291923C98531DC2B30E8FE40BD28D66
CB0B474AC4C50FC1D3CFFDA949B4553C19D5E8D861D76ED8A6
970D17B8ECCFBB1F
A->B s1
B->A s1
A->B s2
B->A s2
Alice's key =
3722C81D780857B4AAE63D109950698938A846C11E616ED29419A986C6D813E35F6969F9
B2C70DD399437978DEAE71606425ADF08D7D
3459B0D8EB19B21D732A038A478B0BAF7A818E5266D75A1097D3F43384D6A9F2DD774AB6
7D282DF907DD2519F2A5185792DAE8C742BD4D4E91340DDBB0
8956856284831D9E3C475BF150
Bob's key   =
3722C81D780857B4AAE63D109950698938A846C11E616ED29419A986C6D813E35F6969F9
B2C70DD399437978DEAE71606425ADF08D7D
3459B0D8EB19B21D732A038A478B0BAF7A818E5266D75A1097D3F43384D6A9F2DD774AB6
7D282DF907DD2519F2A5185792DAE8C742BD4D4E91340DDBB0
8956856284831D9E3C475BF150
A->B s3a
B->A s3b
A->B s1
B->A s1
A->B s2
B->A s2
Alice's key =
A7F469FF38ED3BA3225E1B05A8B44F3643A9128E4E0D2E225744CD58DE55C5D02276E401
1B27A91AEEF3AE6B43D827CC61E6D2E933A5
E8C0601A0E25B434402F8AB9C04855F06794436D592FBE922ED027A37B285207C30F63A2
5115433DA1F8499CB8B5A09D945981489C18CED798944B873E
37DA5200793F2F5283A3BA2704
Bob's key   =
F2FFD37A8934C66480E43F126DC9EB79CBD4F82ACC0686434407A83AFCCC467FDDD50B5C
5DCE74CCE490027033E411701F80C62DE0F9
BFC1611DBD2F1249C3ACC13E724AFBFC10120F57DC304DD6EF7A972DBA33C5008776486A
CAF4A0EE5AB2958E8585A0A94BF7E77805DED664956532DBDC
BA4602C2AD1791C917F9CFDF19
A->B s3a
Bob fails to process Alice's step 3a
2071080376:error:3106706A:lib(49):JPAKE_STEP3A_process:hash of hash of
key mismatch:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SN
AP-20100125.CRYPTO.JPAKE]JPAKE.C;1:443:

4. igetest - exe does not exists at all. We're not building at all?

5. I have suggested earlier and sent a patch for using the second
(currently empty, unused) parameter for configuring 32 or 64 bit pointer
size. 
I still think that it would be useful to have.

$!
$! Check To See If P2 Is Blank.
$!
$ IF (P2.EQS."32")
$ THEN
$    POINTER_SIZE = "32"
$ ELSE
$   IF (P3.EQS."64")
$   THEN
$     POINTER_SIZE = "64"
$   ELSE
$!
$!    Tell The User Entered An Invalid Option..
$!
$     WRITE SYS$OUTPUT ""
$     WRITE SYS$OUTPUT "The Option ",P2," Is Invalid.  The Valid Options
Are:"
$     WRITE SYS$OUTPUT ""
$     WRITE SYS$OUTPUT "    32  :  Compile with 32 bit pointer size"
$     WRITE SYS$OUTPUT "    64  :  Compile with 64 bit pointer size"
$     WRITE SYS$OUTPUT ""
$!
$!    Time To EXIT.
$!
$     GOTO TIDY
$!
$!  End The Valid Argument Check.
$!
$   ENDIF
$ ENDIF
$! End The P2 Check. 

... and further down add this to compiler flags:
$! Write The [.CRYPTO.<ARCH>]BUILDINF.H File.
$!
$ WRITE H_FILE "#define CFLAGS ""/pointer_size=''POINTER_SIZE'/float=g""
/* compiler flags */"


Can anybody send a comment regarding those issues?
Thank you in advance.

Regards,
Z

 

-----Original Message-----
From: Richard Levitte [mailto:rich...@levitte.org] 
Sent: den 27 januari 2010 02:20
To: openssl-dev@openssl.org; s...@antinode.info
Subject: Re: OpenSSL 1.0.0 beta5 release v. VMS

OK, I've gone through and tested the script...  it works for me, I
hope it works for you.

Cheers,
Richard

In message <20100125.112009.189705375.rich...@levitte.org> on Mon, 25
Jan 2010 11:20:09 +0100 (CET), Richard Levitte <rich...@levitte.org>
said:

richard> I just had a look at testtsa.com, and yeah, the corresponding
shell
richard> script has evolved since testtsa.com was last updated.  Working
on it
richard> right now.
richard> 
richard> Cheers,
richard> Richard
richard> 
richard> In message <10012423165954_20205...@antinode.info> on Sun, 24
Jan 2010 23:16:59 -0600 (CST), "Steven M. Schweda" <s...@antinode.info>
said:
richard> 
richard> sms> From: Richard Levitte <rich...@levitte.org>
richard> sms> 
richard> sms> > Might be a fault in test/testtsa.com...  I'll see if I
can find
richard> sms> > something there...
richard> sms> 
richard> sms>    I got some improvement by trying harder to preserve
case in some
richard> sms> places:
richard> sms> 
richard> sms> -$      call create_tsa_cert 1 tsa_cert
richard> sms> +$      call create_tsa_cert 1 "tsa_cert"
richard> sms> 
richard> sms> -$      call create_tsa_cert 2 non_tsa_cert
richard> sms> +$      call create_tsa_cert 2 "non_tsa_cert"
richard> sms> 
richard> sms> Knowing nothing, I'd guess that the missing "TSA_CERT" was
actually
richard> sms> supposed to be "tsa_cert".  I normally run with Parse
Style: Extended,
richard> sms> and that may make me more vulnerable to these things.  Or,
it could just
richard> sms> be lame DCL.  (Finally, there's a good reason to use:
richard> sms>       X = "aBc"
richard> sms> instead of:
richard> sms>       X := aBc
richard> sms> among other things.)
richard> sms> 
richard> sms> And correcting some file names:
richard> sms> 
richard> sms> -$              open/write file
VMStsa-response1.create_tsa_cert
richard> sms> +$              open/write file
VMStsa-response_1.create_tsa_cert
richard> sms> 
richard> sms> -$              define/user sys$input
VMStsa-response.create_tsa_cert
richard> sms> +$              define/user sys$input
VMStsa-response_1.create_tsa_cert
richard> sms> 
richard> sms> -$              open/write file
VMStsa-response2.create_tsa_cert
richard> sms> +$              open/write file
VMStsa-response_2.create_tsa_cert
richard> sms> 
richard> sms> -$              define/user sys$input
VMStsa-response.create_tsa_cert
richard> sms> +$              define/user sys$input
VMStsa-response_2.create_tsa_cert
richard> sms> 
richard> sms> Creating a file named one thing and then using a file
named some other
richard> sms> thing looked suspicious to me.
richard> sms> 
richard> sms>    The next problem I saw in that test:
richard> sms> 
richard> sms> unable to load certificates: ./tsaca.pem
richard> sms> 
richard> sms> seems to be an inability to find a file specified in the
".cnf" file:
richard> sms> 
richard> sms> certs           = $dir/tsaca.pem
richard> sms> 
richard> sms> The shell script seems to say things like "-out tsaca.pem
-keyout
richard> sms> tsacakey.pem", while the DCL never mentions "tsaca.pem".
Either more
richard> sms> code theft or else less would seem to be in order here.
richard> sms> 
richard> sms>
------------------------------------------------------------------------
richard> sms> 
richard> sms>    Steven M. Schweda               s...@antinode-info
richard> sms>    382 South Warwick Street        (+1) 651-699-9818
richard> sms>    Saint Paul  MN  55105-2547
richard> sms>
______________________________________________________________________
richard> sms> OpenSSL Project
http://www.openssl.org
richard> sms> Development Mailing List
openssl-dev@openssl.org
richard> sms> Automated List Manager
majord...@openssl.org

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         rich...@levitte.org
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org

 
 
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to