Re: OpenSSL 0.9.8f Win32 Compile Error

2007-10-13 Thread Alex Pokotilo
n\vcvars32.bat" 3) copy build.bat to the release root directory 4) start "build.bat build". 5) when build failed go to ms directory and copy ntdll.mak to the release root directory 6) open ntdll.mak(in the root directory) go to 19th line and delete /Wx option. 7) start "build.bat

// "PURIFY" directive

2007-10-04 Thread Alex Pokotilo
Hi all, I had a wonder hour debugging ECDSA unit test I made to verify subset of EC library after porting to ARM. I excluded(using compilation directive) "time" in "RAND_seed" and "RAND_pool" itself. After that signatures created by ECDSA became same every session. So I can check resulting signatur

Re: EC_KEY_new_by_curve_name fails when I use NID_secp112r1, NID_secp112r2, NID_secp128r1, NID_secp128r2 etc

2007-10-01 Thread Alex Pokotilo
My mistake :( Everything works fine with Montgomery fields(nist optimized fields just skipped). Fail occured because field power was not enough to sign hash with 20 byte length. Sorry for thoughtless post :( Regards, Alex 2007/10/1, Alex Pokotilo <[EMAIL PROTECTED]>: > Fail occur

EC_KEY_new_by_curve_name fails when I use NID_secp112r1, NID_secp112r2, NID_secp128r1, NID_secp128r2 etc

2007-10-01 Thread Alex Pokotilo
Fail occurs because "EC_GROUP_set_curve_GFp" calls "ec_GFp_nist_group_set_curve" and since we are not working with 192, 224, 256, 384, 521 fields. Why the function is restricted to work with following fields ? Is it for security considerations ? Regards, Alex __