Re: [openssl-users] Fwd: Itanium problem
I'm impressed you were able to do a FIPS build for Windows x64. I didn't think this was possible. ;-) This looks like the hash that FINGERPRINT_premain() spits out when the signature hasn't been embedded into the binary. You may want to confirm the signature is embedded during the build process. On 04/16/2015 04:31 PM, Rongliang Lei wrote: I used Fips module 2.0.9 and OpenSSL 1.0.1M. It built fine in windows for x64,win32 and Itanium. However, it only runs fine for x64 and Win32. For Itanium system, my executable exits immediately right after it runs, and it generated with follow sequence d375fa8a9fd9d8f90fede1f1a9e548132d63230f. I tried dynamic load the libeay32.dll or ssleay32.dll. It has same problem. Any idea about this issue? ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Fwd: Itanium problem
Do you mean it is impossible to do a FIPS build for Windows ia64(Itanium System)? On Fri, Apr 17, 2015 at 8:59 AM, John Foley fol...@cisco.com wrote: I'm impressed you were able to do a FIPS build for Windows x64. I didn't think this was possible. ;-) This looks like the hash that FINGERPRINT_premain() spits out when the signature hasn't been embedded into the binary. You may want to confirm the signature is embedded during the build process. On 04/16/2015 04:31 PM, Rongliang Lei wrote: I used Fips module 2.0.9 and OpenSSL 1.0.1M. It built fine in windows for x64,win32 and Itanium. However, it only runs fine for x64 and Win32. For Itanium system, my executable exits immediately right after it runs, and it generated with follow sequence d375fa8a9fd9d8f90fede1f1a9e548132d63230f. I tried dynamic load the libeay32.dll or ssleay32.dll. It has same problem. Any idea about this issue? ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Fwd: Itanium problem
Normal WIN64 works fine so far On Fri, Apr 17, 2015 at 11:13 AM, Dr. Stephen Henson st...@openssl.org wrote: On Fri, Apr 17, 2015, John Foley wrote: I'm impressed you were able to do a FIPS build for Windows x64. I didn't think this was possible. ;-) WIN64 uses PIC and there aren't any relocation issues so in some ways it's less trouble than WIN32. This looks like the hash that FINGERPRINT_premain() spits out when the signature hasn't been embedded into the binary. You may want to confirm the signature is embedded during the build process. Yes that's the cause. Itanium wasn't a platform that was specifically included during the validation so the build system might not handle it properly and the result most likely wouldn't be validated anyway. Do normal WIN64 binaries work? Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Fwd: Itanium problem
On Thu, Apr 16, 2015 at 4:31 PM, Rongliang Lei rongliang.lei...@gmail.com wrote: I used Fips module 2.0.9 and OpenSSL 1.0.1M. It built fine in windows for x64,win32 and Itanium. However, it only runs fine for x64 and Win32. For Itanium system, my executable exits immediately right after it runs, and it generated with follow sequence d375fa8a9fd9d8f90fede1f1a9e548132d63230f. I tried dynamic load the libeay32.dll or ssleay32.dll. It has same problem. Any idea about this issue? I seem to recall the hash like d375fa8a9fd9d8f90fede1f1a9e548132d63230f will be returned with an exit code of 42 (magic). When something encounters it (was it fipsld?), it writes the signature to the file. You can see remnants of it at the wiki page on fipsld++:https://wiki.openssl.org/index.php/Fipsld_and_C%2B%2B#fipsld_Modifications . You're free to modify the fipsld script within reason. Its not sequestered. Jeff ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Fwd: Itanium problem
On Fri, Apr 17, 2015, John Foley wrote: I'm impressed you were able to do a FIPS build for Windows x64. I didn't think this was possible. ;-) WIN64 uses PIC and there aren't any relocation issues so in some ways it's less trouble than WIN32. This looks like the hash that FINGERPRINT_premain() spits out when the signature hasn't been embedded into the binary. You may want to confirm the signature is embedded during the build process. Yes that's the cause. Itanium wasn't a platform that was specifically included during the validation so the build system might not handle it properly and the result most likely wouldn't be validated anyway. Do normal WIN64 binaries work? Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Fwd: Itanium problem
On 17/04/2015 17:25, Rongliang Lei wrote: Normal WIN64 works fine so far On Fri, Apr 17, 2015 at 11:13 AM, Dr. Stephen Henson st...@openssl.org mailto:st...@openssl.org wrote: On Fri, Apr 17, 2015, John Foley wrote: I'm impressed you were able to do a FIPS build for Windows x64. I didn't think this was possible. ;-) WIN64 uses PIC and there aren't any relocation issues so in some ways it's less trouble than WIN32. This looks like the hash that FINGERPRINT_premain() spits out when the signature hasn't been embedded into the binary. You may want to confirm the signature is embedded during the build process. Yes that's the cause. Itanium wasn't a platform that was specifically included during the validation so the build system might not handle it properly and the result most likely wouldn't be validated anyway. Do normal WIN64 binaries work? Normal Win64? You mean Win64 for HP/Digital Alpha AXP, aka Windows 2000 Release Candidate? Or Win64 for Itanium, aka Windows XP 64 bit edition, Gold and Service pack 1? Or the latest one (possibly not yet released) Win64 for Arm ARCHitecture v8? You surely cannot mean that amd64 port, introduced in Windows 2003 (NT 5.02)? Just joking :-) Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] Fwd: Itanium problem
I used Fips module 2.0.9 and OpenSSL 1.0.1M. It built fine in windows for x64,win32 and Itanium. However, it only runs fine for x64 and Win32. For Itanium system, my executable exits immediately right after it runs, and it generated with follow sequence d375fa8a9fd9d8f90fede1f1a9e548132d63230f. I tried dynamic load the libeay32.dll or ssleay32.dll. It has same problem. Any idea about this issue? ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
