<p dir="ltr">FjbbnbmbnmàKgjkjuio π_\\°^_<¶_<\\=\<_=<<=[[^°°_=<\<<_\^°√•©\\_===<=]]]>_^^=</p>
<div class="gmail_quote">On Jan 3, 2018 6:00 AM, <<a href="mailto:erlang-questions-request@erlang.org">erlang-questions-request@erlang.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send erlang-questions mailing list submissions to<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:erlang-questions-request@erlang.org">erlang-questions-request@<wbr>erlang.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:erlang-questions-owner@erlang.org">erlang-questions-owner@erlang.<wbr>org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of erlang-questions digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Windows Patch Packages? (Kenneth Lundin)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Wed, 3 Jan 2018 10:48:23 +0100<br>
From: Kenneth Lundin <<a href="mailto:kenneth.lundin@gmail.com">kenneth.lundin@gmail.com</a>><br>
To: "<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> Questions"<br>
<<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] Windows Patch Packages?<br>
Message-ID:<br>
<<a href="mailto:CAOzgw9298UukjP7uLRLKzGPu6ZCQgtDWVoW8xcatb6xniYijcA@mail.gmail.com">CAOzgw9298UukjP7uLRLKzGPu6ZCQ<wbr>gtDWVoW8xcatb6xniYijcA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
By mistake my answer was only sent to Peter Tirell, should have been sent<br>
to the list.<br>
<br>
Here it is<br>
<br>
<br>
The pre built Windows installers on <a href="http://erlang.org" rel="noreferrer" target="_blank">erlang.org</a> are only provided for the<br>
planned releases and patch packages, they are not provided for "emergency"<br>
patches<br>
between or after the planned releases. 18.3 is the latest pre built<br>
Windows installer for the OTP 18 release track.<br>
<br>
In order to apply 18.3.4.7 you have to build from source.<br>
<br>
Another possibility if it is tricky to build on Windows, is that you build<br>
from source on Linux and then copy the only application changed by the<br>
patch to your Windows system under ERl_ROOT/lib or somewhere else if you<br>
point it out with erl -pa <Path><br>
<br>
Since OTP 20.2 is just a patch it only lists in its README what has been<br>
fixed since the last patch , which was 20.1.7 containing a fix for<br>
OTP-14748. You can look i the release notes for the ssl application in OTP<br>
20.2 and find that OTP-14748 is mentioned there.<br>
<br>
So there is a Windows build, namely 20.2 which includes the patch you are<br>
looking for.<br>
<br>
/Regards Kenneth, Erlang/OTP Ericsson<br>
<br>
On Wed, Dec 20, 2017 at 3:55 PM, Peter Tirrell <<a href="mailto:ptirrell@gmail.com">ptirrell@gmail.com</a>> wrote:<br>
<br>
> Hello all,<br>
><br>
> I saw an existing recent thread about general patch packages but didn't<br>
> necessarily want to hijack that thread. I currently am using OTP 18.2.1 on<br>
> Windows but became aware of security advisory CVE-2017-1000385 (<br>
> <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-1000385#VulnChangeHistoryDiv" rel="noreferrer" target="_blank">https://nvd.nist.gov/vuln/<wbr>detail/CVE-2017-1000385#<wbr>VulnChangeHistoryDiv</a>)<br>
><br>
> It looks like I can get OTP 18.3.4.7+ and have the advisory addressed, but<br>
> I'm unclear on how to do so. The downloads page simply lists an 18.3<br>
> download and doesn't list the fixed OTP bug number in the readme. The<br>
> earlier thread I saw seemed to imply that Windows builds on the downloads<br>
> page aren't updated.<br>
><br>
> So my question is - how do I apply the latest Windows patched builds? Are<br>
> there patched Windows release builds available somewhere? If I download a<br>
> version from the downloads page, will that be the latest available major<br>
> point version, including any patches for that point version?<br>
><br>
> Or if there's a patch package put out, do I need to either compile that<br>
> version from source, or wait until there is another major point version<br>
> released that comes *after* that patch package was created? For example,<br>
> I'm looking for a fix for bug "OTP-14748". The only Windows build that<br>
> appears to be dated since that was fixed is 20.2, yet the readme for that<br>
> does not include a reference to 14748 either.<br>
><br>
> Thanks for any info!<br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180103/faa07055/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180103/faa07055/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
<br>
<br>
End of erlang-questions Digest, Vol 354, Issue 11<br>
******************************<wbr>*******************<br>
</blockquote></div>