<div dir="ltr"><div dir="ltr"><div>Hi Dennis</div><br><div class="gmail_quote"><div class="gmail_attr">Yes, 10-main.conf is modified for both the versions. </div><div class="gmail_attr">Following are changes. </div><div class="gmail_attr"><br></div><div class="gmail_attr"><div class="gmail_attr"><<< file 1: /view/rdl117_linuxx86_64/vobs_tools/src/openssl-1.1.1b/Configurations/10-main.conf@@/main/1</div><div class="gmail_attr">>>> file 2: 10-main.conf</div><div class="gmail_attr">********************************</div><div class="gmail_attr">-----[16 changed to 16]-----</div><div class="gmail_attr">< ASFLAGS => "/nologo /Zi",</div><div class="gmail_attr">---</div><div class="gmail_attr">> ASFLAGS => "/nologo",</div><div class="gmail_attr">-----[44 changed to 44]-----</div><div class="gmail_attr">< ASFLAGS => "/nologo /Zi",</div><div class="gmail_attr">---</div><div class="gmail_attr">> ASFLAGS => "/nologo",</div><div class="gmail_attr">-----[211 changed to 211]-----</div><div class="gmail_attr">< ex_libs => add("-lsocket -lnsl -ldl"),</div><div class="gmail_attr">---</div><div class="gmail_attr">> ex_libs => add("-lsocket -lnsl -ldl -lm -lrt"),</div><div class="gmail_attr">-----[1226 changed to 1226]-----</div><div class="gmail_attr">< lib_cflags => add("/Zi /Fdossl_static.pdb"),</div><div class="gmail_attr">---</div><div class="gmail_attr">> lib_cflags => add("/Fdossl_static.pdb"),</div><div class="gmail_attr">-----[1228-1229 changed to 1228-1229]-----</div><div class="gmail_attr">< dso_cflags => "/Zi /Fddso.pdb",</div><div class="gmail_attr">< bin_cflags => "/Zi /Fdapp.pdb",</div><div class="gmail_attr">---</div><div class="gmail_attr">> dso_cflags => "/Fddso.pdb",</div><div class="gmail_attr">> bin_cflags => "/Fdapp.pdb",</div><div><br></div><div>The error is coming for OPENSSL_sk_new_null which is changed in 1.1.1b compared to 1.1.1 with <a href="https://github.com/openssl/openssl/pull/7721">https://github.com/openssl/openssl/pull/7721</a>. </div><div>Can this be related ?</div><div><br></div><div>Thanks and Regards,</div><div>Ram Krushna</div></div><div class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 4:07 PM <<a href="mailto:openssl-users-request@openssl.org">openssl-users-request@openssl.org</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send openssl-users mailing list submissions to<br>
<a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mta.openssl.org/mailman/listinfo/openssl-users" rel="noreferrer" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openssl-users-request@openssl.org" target="_blank">openssl-users-request@openssl.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openssl-users-owner@openssl.org" target="_blank">openssl-users-owner@openssl.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of openssl-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Internal IP Exposed (Kyle Hamilton)<br>
2. Re: Reg solaris support for openssl 1.1.1b (ramakrushna mishra)<br>
3. Re: Reg solaris support for openssl 1.1.1b (Dennis Clarke)<br>
4. Re: Building OpenSSL 1.1.1b for WinCE700 (???? (Souju TANAKA))<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 25 Mar 2019 22:09:31 -0500<br>
From: Kyle Hamilton <<a href="mailto:aerowolf@gmail.com" target="_blank">aerowolf@gmail.com</a>><br>
To: Abdul Qoyyuum <<a href="mailto:aqoyyuum@cardaccess.com.au" target="_blank">aqoyyuum@cardaccess.com.au</a>><br>
Cc: openssl-users <<a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a>><br>
Subject: Re: Internal IP Exposed<br>
Message-ID:<br>
<CAPMEXDY1UVrXFrfFJbFq=<a href="mailto:34Rhm-wdVz2YOnR2Ds%2B3L9Uzz9prw@mail.gmail.com" target="_blank">34Rhm-wdVz2YOnR2Ds+3L9Uzz9prw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
That's a configuration issue with the servers, not an issue with the<br>
openssl command itself.<br>
<br>
There's no information on what the back-end HTTP server software is<br>
being used. If it were Apache, there would be a ServerName directive<br>
that could change the server's idea of what name it should refer to<br>
itself as. I don't have information on other server software<br>
configuration.<br>
<br>
-Kyle H<br>
<br>
On Sun, Mar 24, 2019 at 7:34 PM Abdul Qoyyuum<br>
<<a href="mailto:aqoyyuum@cardaccess.com.au" target="_blank">aqoyyuum@cardaccess.com.au</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> New to the mailing list and a complete newbie to openssl and the likes. There's a ticket by a client that I'm new at and he claims that there's a security problem with the openssl command to his servers.<br>
><br>
> Internal IP exposed after running a openssl (version 1.1.0j) connect command:<br>
><br>
> openssl s_client -connect 103.XX.XXX.XX:10443 -quiet<br>
><br>
> Where 103.XX.XXX.XX is a Public IP. And after it shows the certificates, typed the following:<br>
><br>
> GET /images HTTP/1.0<br>
><br>
> And hit enter twice, the following gets displayed:<br>
><br>
> HTTP/1.0 301 Moved Permanently<br>
> Date: Mon, 25 Mar 2019 00:10:13 GMT<br>
> Server: xxxxxxxx-xxxxx<br>
> Location: <a href="https://10.240.123.1:10443/images/" rel="noreferrer" target="_blank">https://10.240.123.1:10443/images/</a><br>
> Connection: close<br>
> Content-Type: text/html; charset=utf-8<br>
> X-Frame-Options: SAMEORIGIN<br>
> Content-Security-Policy: frame-ancestors 'self'<br>
> X-XSS-Protection: 1; mode=block<br>
> X-Content-Type-Options: nosniff<br>
> Strict-Transport-Security: max-age=28800<br>
><br>
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><br>
> <HTML><HEAD><br>
> <TITLE>301 Moved Permanently</TITLE><br>
> </HEAD><BODY><br>
> <H1>Moved Permanently</H1><br>
> The document has moved <A HREF="<a href="https://10.240.123.1:10443/images/" rel="noreferrer" target="_blank">https://10.240.123.1:10443/images/</a>">here</A>.<P><br>
> </BODY></HTML><br>
> read:errno=0<br>
><br>
> The 10.240.123.1 is an internal IP and it is exposed by this little method. Although not shown when using curl -kv -O command.<br>
><br>
> Is there a way to cover up the "Location" or at least the internal IP from being exposed? Thanks.<br>
><br>
> Sorry if this isn't clear or if this is the wrong place to ask this.<br>
><br>
> --<br>
> Abdul Qoyyuum Bin Haji Abdul Kadir<br>
> HP No: +673 720 8043<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 26 Mar 2019 10:08:12 +0530<br>
From: ramakrushna mishra <<a href="mailto:rama.krushna7@gmail.com" target="_blank">rama.krushna7@gmail.com</a>><br>
To: <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
Subject: Re: Reg solaris support for openssl 1.1.1b<br>
Message-ID:<br>
<CAHgr=<a href="mailto:k%2BNbGaW735roC%2BaQBFW4B7VxCYi7o6VsqDqn6_7Xy4yRQ@mail.gmail.com" target="_blank">k+NbGaW735roC+aQBFW4B7VxCYi7o6VsqDqn6_7Xy4yRQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
><br>
> Hi All,<br>
><br>
<br>
Thanks for your responses.<br>
I am able to build openssl 1.1.1 on my solaris and able to run "openssl<br>
version".<br>
I followed the same procedure for openssl 1.1.1b and when I run "openssl<br>
version" seeing the mentioned error. i.e<br>
"ld.so.1: openssl: fatal: relocation error: file openssl: symbol<br>
OPENSSL_sk_new_null: referenced symbol not found<br>
Killed<br>
".<br>
<br>
So, How come it works with openssl 1.1.1 and not with 1.1.1b.<br>
I am using the same machine and same procedure to configure and install it.<br>
So, Is there anything different that need to be done for 1.1.1b version ?<br>
<br>
Thanks and Regards,<br>
Ram Krushna<br>
<br>
<br>
><br>
> On Sat, Mar 16, 2019 at 6:20 AM <<a href="mailto:openssl-users-request@openssl.org" target="_blank">openssl-users-request@openssl.org</a>> wrote:<br>
><br>
>> Send openssl-users mailing list submissions to<br>
>> <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
>><br>
>> To subscribe or unsubscribe via the World Wide Web, visit<br>
>> <a href="https://mta.openssl.org/mailman/listinfo/openssl-users" rel="noreferrer" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-users</a><br>
>> or, via email, send a message with subject or body 'help' to<br>
>> <a href="mailto:openssl-users-request@openssl.org" target="_blank">openssl-users-request@openssl.org</a><br>
>><br>
>> You can reach the person managing the list at<br>
>> <a href="mailto:openssl-users-owner@openssl.org" target="_blank">openssl-users-owner@openssl.org</a><br>
>><br>
>> When replying, please edit your Subject line so it is more specific<br>
>> than "Re: Contents of openssl-users digest..."<br>
>><br>
>><br>
>> Today's Topics:<br>
>><br>
>> 1. Re: Reg solaris support for openssl 1.1.1b (Jakob Bohm)<br>
>> 5. Re: Reg solaris support for openssl 1.1.1b (Dennis Clarke)<br>
>><br>
>><br>
>> ----------------------------------------------------------------------<br>
>><br>
>> Message: 1<br>
>> Date: Fri, 15 Mar 2019 18:19:53 +0100<br>
>> From: Jakob Bohm <<a href="mailto:jb-openssl@wisemo.com" target="_blank">jb-openssl@wisemo.com</a>><br>
>> To: <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
>> Subject: Re: Reg solaris support for openssl 1.1.1b<br>
>> Message-ID: <<a href="mailto:649ef06e-0f64-65bb-cb43-cfde681fd117@wisemo.com" target="_blank">649ef06e-0f64-65bb-cb43-cfde681fd117@wisemo.com</a>><br>
>> Content-Type: text/plain; charset=utf-8; format=flowed<br>
>><br>
>> On 15/03/2019 14:33, Dennis Clarke wrote:<br>
>> > On 3/15/19 5:38 AM, Matthias St. Pierre wrote:<br>
>> >> My guess is that your binary is loading the system's shared libraries.<br>
>> >> To find out whether this is the case, try<br>
>> >><br>
>> >> ??? ldd bin/openssl<br>
>> >><br>
>> >> If my assumption is correct, you might have to set the LD_LIBRARY_PATH<br>
>> >> explicitely.<br>
>> > Actually LD_LIBRARY_PATH is evil.<br>
>> ><br>
>> > The correct way to do this is to compile with a RUNPATH set in the<br>
>> > output ELF files.<br>
>> LD_LIBRARY_PATH overriding the compiled in RUNPATH is appropriate when<br>
>> testing<br>
>> a newly compiled binary before installing the libraries to their final<br>
>> locations, perhaps<br>
>> on the same, perhaps on another machine.<br>
>><br>
>> P.S.<br>
>> I don't known if the Solaris loader lets LD_LIBRARY_PATH override<br>
>> RUNPATH as<br>
>> presumed by the above answer.<br>
>><br>
>> Enjoy<br>
>><br>
>> Jakob<br>
>> --<br>
>> Jakob Bohm, CIO, Partner, WiseMo A/S. <a href="https://www.wisemo.com" rel="noreferrer" target="_blank">https://www.wisemo.com</a><br>
>> Transformervej 29, 2860 S?borg, Denmark. Direct +45 31 13 16 10<br>
>> This public discussion message is non-binding and may contain errors.<br>
>> WiseMo - Remote Service Management for PCs, Phones and Embedded<br>
>><br>
>><br>
>><br>
>> ------------------------------<br>
>> Message: 5<br>
>> Date: Fri, 15 Mar 2019 20:49:30 -0400<br>
>> From: Dennis Clarke <<a href="mailto:dclarke@blastwave.org" target="_blank">dclarke@blastwave.org</a>><br>
>> To: <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
>> Subject: Re: Reg solaris support for openssl 1.1.1b<br>
>> Message-ID: <<a href="mailto:4b08232c-f734-987c-814c-5acef59f42ab@blastwave.org" target="_blank">4b08232c-f734-987c-814c-5acef59f42ab@blastwave.org</a>><br>
>> Content-Type: text/plain; charset=utf-8<br>
>><br>
>> On 3/15/19 1:19 PM, Jakob Bohm via openssl-users wrote:<br>
>> > On 15/03/2019 14:33, Dennis Clarke wrote:<br>
>> >> On 3/15/19 5:38 AM, Matthias St. Pierre wrote:<br>
>> >>> My guess is that your binary is loading the system's shared libraries.<br>
>> >>> To find out whether this is the case, try<br>
>> >>><br>
>> >>> ???? ldd bin/openssl<br>
>> >>><br>
>> >>> If my assumption is correct, you might have to set the LD_LIBRARY_PATH<br>
>> >>> explicitely.<br>
>> >> Actually LD_LIBRARY_PATH is evil.<br>
>> >><br>
>> >> The correct way to do this is to compile with a RUNPATH set in the<br>
>> >> output ELF files.<br>
>> > LD_LIBRARY_PATH overriding the compiled in RUNPATH is appropriate when<br>
>> > testing<br>
>> > a newly compiled binary before installing the libraries to their final<br>
>> > locations, perhaps<br>
>> > on the same, perhaps on another machine.<br>
>> ><br>
>> > P.S.<br>
>> > I don't known if the Solaris loader lets LD_LIBRARY_PATH override<br>
>> > RUNPATH as<br>
>> > presumed by the above answer.<br>
>><br>
>> Yes it certainly does. Otherwise testing a new custom lib would be a<br>
>> royal pain as opposed to just a pain. Also most people still, after<br>
>> twenty years, know what LD_LIBRARY_PATH env var is for and it is a waste<br>
>> of breath trying to explain it after decades of watching folks skewer<br>
>> themselves over and over and over ....<br>
>><br>
>> dc<br>
>><br>
>><br>
>><br>
>> ------------------------------<br>
>><br>
>> Subject: Digest Footer<br>
>><br>
>> _______________________________________________<br>
>> openssl-users mailing list<br>
>> <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
>> <a href="https://mta.openssl.org/mailman/listinfo/openssl-users" rel="noreferrer" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-users</a><br>
>><br>
>><br>
>> ------------------------------<br>
>><br>
>> End of openssl-users Digest, Vol 52, Issue 19<br>
>> *********************************************<br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mta.openssl.org/pipermail/openssl-users/attachments/20190326/09253e6e/attachment-0001.html" rel="noreferrer" target="_blank">http://mta.openssl.org/pipermail/openssl-users/attachments/20190326/09253e6e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 26 Mar 2019 02:55:38 -0400<br>
From: Dennis Clarke <<a href="mailto:dclarke@blastwave.org" target="_blank">dclarke@blastwave.org</a>><br>
To: <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
Subject: Re: Reg solaris support for openssl 1.1.1b<br>
Message-ID: <<a href="mailto:4c02f69c-512b-d5c8-67a2-eebe6e3f3197@blastwave.org" target="_blank">4c02f69c-512b-d5c8-67a2-eebe6e3f3197@blastwave.org</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On 3/26/19 12:38 AM, ramakrushna mishra wrote:<br>
> Hi All,<br>
> <br>
> <br>
> Thanks for your responses.?<br>
> I am able to build openssl 1.1.1 on my solaris and able to run "openssl<br>
> version".<br>
> I followed the same procedure for openssl 1.1.1b and when I run "openssl<br>
> version"? seeing the mentioned error. i.e?<br>
> "ld.so.1: openssl: fatal: relocation error: file openssl: symbol<br>
> OPENSSL_sk_new_null: referenced symbol not found<br>
<br>
Did you modify Configurations/10-main.conf ?<br>
<br>
<br>
<br>
-- <br>
Dennis Clarke<br>
RISC-V/SPARC/PPC/ARM/CISC<br>
UNIX and Linux spoken<br>
GreyBeard and suspenders optional<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 27 Mar 2019 19:33:44 +0900<br>
From: ???? (Souju TANAKA) <<a href="mailto:sojulibra@gmail.com" target="_blank">sojulibra@gmail.com</a>><br>
To: <a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
Subject: Re: Building OpenSSL 1.1.1b for WinCE700<br>
Message-ID:<br>
<<a href="mailto:CAPvkBATRzBmqYAmHfiJs9wbgCt_s7zk_jViTU1sia35-pfL4aQ@mail.gmail.com" target="_blank">CAPvkBATRzBmqYAmHfiJs9wbgCt_s7zk_jViTU1sia35-pfL4aQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello,<br>
<br>
It works with our custommized cURL code.<br>
I wrote a detailed build instruction for CE.<br>
<a href="https://qiita.com/souju/items/94117c024862f57459c3" rel="noreferrer" target="_blank">https://qiita.com/souju/items/94117c024862f57459c3</a><br>
<br>
> It would be good if you created a github PR for this so the changes can be<br>
> considered for inclusion.<br>
<br>
Thank you. I post the PR.<br>
<a href="https://github.com/openssl/openssl/pull/8596" rel="noreferrer" target="_blank">https://github.com/openssl/openssl/pull/8596</a><br>
<br>
Regards,<br>
Souju TANAKA<br>
<br>
<br>
2019?3?19?(?) 18:39 Matt Caswell <<a href="mailto:matt@openssl.org" target="_blank">matt@openssl.org</a>>:<br>
<br>
><br>
><br>
> On 19/03/2019 07:08, ???? wrote:<br>
> > Hello,<br>
> ><br>
> > I have successfully build OpenSSL 1.1.1b (only libraries, no app) for<br>
> > WINCE700-ARMV4I, though I don't do any tests. Here is what I did. I hope<br>
> > original sources will be changed so as there is no need to change.<br>
><br>
> It would be good if you created a github PR for this so the changes can be<br>
> considered for inclusion.<br>
><br>
> Matt<br>
><br>
><br>
> ><br>
> > 1. Modify wcecompat.<br>
> ><br>
> > Add an alias, "_access" for access() in wcecompat io.h as below.<br>
> > --<br>
> > #define access _wceaccess<br>
> > #define _access _wceaccess<br>
> > --<br>
> ><br>
> > 2. Set Environmental variables<br>
> ><br>
> > set OSVERSION=WCE700<br>
> > set PLATFORM=VC-CE<br>
> > set TARGETCPU=ARMV4I<br>
> > set WCECOMPAT=C:\Users\dev\tanaka\wcecompat<br>
> > set LIB=C:\Program Files (x86)\Microsoft Visual Studio<br>
> > 9.0\VC\ATLMFC\LIB;C:\Program Files (x86)\Windows CE<br>
> > Tools\SDKs\YOUR_SDK_NAME\Lib\ARMV4I;C:\Program Files\Microsoft<br>
> > SDKs\Windows\v6.0A\Lib;C:\Program Files (x86)\Microsoft Visual Studio<br>
> > 9.0\VC\ce\lib\ARMV4I;C:\Program Files (x86)\Microsoft Visual Studio<br>
> 9.0\VC\lib<br>
> > set INCLUDE=C:\Program Files (x86)\Windows CE<br>
> > Tools\SDKs\YOUR_SDK_NAME\Include\ARMV4I;C:\Program Files (x86)\Microsoft<br>
> Visual<br>
> > Studio 9.0\VC\atlmfc\include;C:\Program Files (x86)\Microsoft Visual<br>
> Studio<br>
> > 9.0\VC\INCLUDE;C:\Program Files\Microsoft SDKs\Windows\v6.0A\include;<br>
> > set Path=C:\WINCE700\sdk\bin\i386\arm;C:\Program Files (x86)\Microsoft<br>
> Visual<br>
> > Studio 9.0\Common7\Tools;C:\Program Files (x86)\Microsoft Visual Studio<br>
> > 9.0\VC\VCPackages;C:\Program Files\Microsoft<br>
> ><br>
> SDKs\Windows\v6.0A\bin;C:\cygwin64\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program<br>
> > Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE;C:\Program Files<br>
> > (x86)\Microsoft Visual Studio 9.0\VC\BIN;%Path%<br>
> > set LIBPATH=C:\Program Files (x86)\Microsoft Visual Studio<br>
> > 9.0\VC\ATLMFC\LIB;"C:\Program Files (x86)\Windows CE<br>
> > Tools\SDKs\YOUR_SDK_NAME\Lib\ARMV4I";C:\Program Files (x86)\Microsoft<br>
> Visual<br>
> > Studio 9.0\VC\lib;C:\Program Files (x86)\Microsoft Visual Studio<br>
> > 9.0\VC\ce\lib\ARMV4I;<br>
> ><br>
> > 3. Configure<br>
> ><br>
> > (for ARM)(Configurations/windows-makefile.tmpl) Delete a line of<br>
> "setargv.obj".<br>
> > setargv.obj in C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\lib<br>
> is for<br>
> > x86 and cannot be linked with ARM objs.<br>
> ><br>
> > C:\Strawberry\perl\bin\perl Configure no-idea no-mdc2 no-rc5 no-asm<br>
> no-ssl3<br>
> > no-stdio no-async no-engine VC-CE<br>
> ><br>
> > Using full path to specify Strawberry perl. I recommend Strawberry perl<br>
> here to<br>
> > avoid error messages, I used 5.24.4.1-32bit.<br>
> ><br>
> > I added 3 options of "no-stdio" and "no-engine", "no-async". Because..<br>
> > * no-stdio: GetStdHandle() and STD_INPUT_HANDLE cannot be used in<br>
> WinCE. (used<br>
> > in apps\apps.c)<br>
> > * no-engine: Lack of CreatePipe() in WinCE (used in engines\e_dasync.c)<br>
> > * no-async: Lack of ConvertFiberToThread() in WinCE (used in<br>
> > crypto\async\arch\async_win.c)<br>
> > By "no-stdio" option, we build only libraries. No command line<br>
> application are<br>
> > generated.<br>
> ><br>
> > 4. Modify "makefile"<br>
> ><br>
> > * Add -D_MSC_VER=1300 in "CFLAGS="<br>
> > * In "CNF_CPPFLAGS=", change -I"\$(WCECOMPAT)/include" to<br>
> -I$(WCECOMPAT)/include<br>
> > * Change CNF_EX_LIBS=3 to CNF_EX_LIBS=ws2.lib crypt32.lib kernel32.lib<br>
> > $(WCECOMPAT)\lib\wcecompat.lib $(WCECOMPAT)\lib\wcecompatex.lib<br>
> corelibc.lib<br>
> > coredll.lib<br>
> ><br>
> > 5. Modify C Source<br>
> ><br>
> > Comment out a line of "# define stat _stat" in<br>
> > crypto\conf\conf_def.c<br>
> > crypto\rand\randfile.c<br>
> > crypto\store\loader_file.c<br>
> > Comment out a line of "# define fstat _fstat" in<br>
> crypto\rand\randfile.c.<br>
> ><br>
> > (crypt/init.c 167l and 777l) For lack of GetModuleHandleEx() in CE,<br>
> Change "#<br>
> > ifdef DSO_WIN32" to "# if defined(DSO_WIN32) && !defined(_WIN32_WCE)"<br>
> > -----------------<br>
> > # ifdef DSO_WIN32<br>
> > {<br>
> > HMODULE handle = NULL;<br>
> > BOOL ret;<br>
> ><br>
> > /* We don't use the DSO route for WIN32 because there is a<br>
> better way */<br>
> > ret = GetModuleHandleEx(GET_MODULE_HANDLE_EX_FLAG_FROM_ADDRESS<br>
> > -----------------<br>
> ><br>
> > (crypto\rand\randfile.c 257l) For lack of GetEnvironmentVariableW() in<br>
> CE,<br>
> > Change "#if defined(_WIN32) && defined(CP_UTF8)" to "#if defined(_WIN32)<br>
> &&<br>
> > defined(CP_UTF8) && !defined(_WIN32_WCE)"<br>
> ><br>
> > (for ARM)(include\internal\refcount.h)<br>
> > * Add "#include <winbase.h>" for InterlockedExchangeAdd().<br>
> > * (106l) In function CRYPTO_UP_REF() and CRYPTO_DOWN_REF(), change 2<br>
> > "_InterlockedExchangeAdd()" to be "InterlockedExchangeAdd()". There is no<br>
> > _InterlockedExchangeAdd() for non x86 in C:\Program Files (x86)\Windows<br>
> CE<br>
> > Tools\SDKs\YOUR_SDK_NAME\Include\Armv4i\winbase.h.<br>
> ><br>
> > (crypt/threads_win.c 27l) For lack of<br>
> InitializeCriticalSectionAndSpinCount() in<br>
> > CE, change<br>
> > ------------------<br>
> > /* 0x400 is the spin count value suggested in the documentation */<br>
> > if (!InitializeCriticalSectionAndSpinCount(lock, 0x400)) {<br>
> > OPENSSL_free(lock);<br>
> > return NULL;<br>
> > }<br>
> > ------------------<br>
> > to<br>
> > ------------------<br>
> > #ifndef _WIN32_WCE<br>
> > /* 0x400 is the spin count value suggested in the documentation */<br>
> > if (!InitializeCriticalSectionAndSpinCount(lock, 0x400)) {<br>
> > OPENSSL_free(lock);<br>
> > return NULL;<br>
> > }<br>
> > #else<br>
> > InitializeCriticalSection(lock);<br>
> > #endif<br>
> > ------------------<br>
> ><br>
> > 6. Build<br>
> ><br>
> > nmake<br>
> ><br>
> > Then we will get the following artifacts.<br>
> > libcrypto.lib<br>
> > libcrypto-1_1.dll<br>
> > libcrypto-1_1.pdb<br>
> > libssl.lib<br>
> > libssl-1_1.dll<br>
> > libssl-1_1.pdb<br>
> ><br>
> > Regards,<br>
> > Soju TANAKA<br>
> ><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mta.openssl.org/pipermail/openssl-users/attachments/20190327/9585737c/attachment.html" rel="noreferrer" target="_blank">http://mta.openssl.org/pipermail/openssl-users/attachments/20190327/9585737c/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
openssl-users mailing list<br>
<a href="mailto:openssl-users@openssl.org" target="_blank">openssl-users@openssl.org</a><br>
<a href="https://mta.openssl.org/mailman/listinfo/openssl-users" rel="noreferrer" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of openssl-users Digest, Vol 52, Issue 41<br>
*********************************************<br>
</blockquote></div></div></div>