Merge commit '73c6f44e6b' into trunk

This commit is contained in:
Bruce Dubbs 2021-05-17 19:47:47 -05:00
commit c8115f33d6
3 changed files with 38 additions and 15 deletions

View File

@ -48,6 +48,10 @@
<para>[ken] - Patch exiv2-0.27.3 (security fix). Fixes <para>[ken] - Patch exiv2-0.27.3 (security fix). Fixes
<ulink url="&blfs-ticket-root;15052">#15052</ulink>.</para> <ulink url="&blfs-ticket-root;15052">#15052</ulink>.</para>
</listitem> </listitem>
<listitem>
<para>[bdubbs] - Update to nss-3.65. Fixes
<ulink url="&blfs-ticket-root;15044">#15044</ulink>.</para>
</listitem>
<listitem> <listitem>
<para>[bdubbs] - Update to libidn-1.37. Fixes <para>[bdubbs] - Update to libidn-1.37. Fixes
<ulink url="&blfs-ticket-root;15048">#15048</ulink>.</para> <ulink url="&blfs-ticket-root;15048">#15048</ulink>.</para>

View File

@ -25,7 +25,7 @@
<!ENTITY nftables-version "0.9.3"> <!ENTITY nftables-version "0.9.3">
<!ENTITY nettle-version "3.7.2"> <!ENTITY nettle-version "3.7.2">
<!ENTITY nss-minor-version "64"> <!ENTITY nss-minor-version "65">
<!ENTITY nss-micro-version "0"> <!ENTITY nss-micro-version "0">
<!--<!ENTITY nss-version "3.&nss-minor-version;.&nss-micro-version;">--> <!--<!ENTITY nss-version "3.&nss-minor-version;.&nss-micro-version;">-->
<!ENTITY nss-version "3.&nss-minor-version;"> <!ENTITY nss-version "3.&nss-minor-version;">

View File

@ -14,10 +14,10 @@
<!ENTITY nss-download-http "https://&nss-url;/NSS_3_&nss-minor-version;_RTM/src/nss-&nss-version;.tar.gz"> <!ENTITY nss-download-http "https://&nss-url;/NSS_3_&nss-minor-version;_RTM/src/nss-&nss-version;.tar.gz">
<!ENTITY nss-download-ftp " "> <!ENTITY nss-download-ftp " ">
<!ENTITY nss-md5sum "2b042b68ec53e99f8f91f37c0c842ee3"> <!ENTITY nss-md5sum "0f162efc4e587b0a37f05d5d438cfc0c">
<!ENTITY nss-size "79 MB"> <!ENTITY nss-size "79 MB">
<!ENTITY nss-buildsize "306 MB (add 99 MB for tests)"> <!ENTITY nss-buildsize "304 MB (add 99 MB for tests)">
<!ENTITY nss-time "2.9 SBU (with parallelism=4, add 20 SBU for tests)"> <!ENTITY nss-time "2.9 SBU (with parallelism=4, add 35 SBU for tests)">
]> ]>
<sect1 id="nss" xreflabel="NSS-&nss-version;"> <sect1 id="nss" xreflabel="NSS-&nss-version;">
@ -150,21 +150,40 @@ make BUILD_OPT=1 \
HOST=localhost DOMSUF=localdomain ./all.sh &amp;&amp; HOST=localhost DOMSUF=localdomain ./all.sh &amp;&amp;
cd ../</userinput></screen> cd ../</userinput></screen>
<!-- Some information about the tests: <note>
- HOST=localhost and DOMSUF=localdomain require the changes done to <para>Some information about the tests:</para>
/etc/hosts in r11892 (LFS). Without these variables, a FQDN is <itemizedlist spacing="compact">
required to specified, and this generic way should work for <listitem>
<para>
HOST=localhost and DOMSUF=localdomain are required
Without these variables, a FQDN is
required to specified and this generic way should work for
everyone. everyone.
- With NSS-3.53, there were 53,866 tests. The tests take an </para>
extremely long time to run. </listitem>
- Another interesting discovery has to do with interrupting the tests. <listitem>
It was discovered that, when interrupting the tests, the test suite <para>
The tests take an extremely long time to run. If desired there is
information the all.sh script about running subsets of the
total test suite.
</para>
</listitem>
<listitem>
<para>
When interrupting the tests, the test suite
fails to spin down test servers that are run. This leads to an fails to spin down test servers that are run. This leads to an
infinite loop in the tests where the test suite tries to kill a server infinite loop in the tests where the test suite tries to kill a server
that doesn't exist anymore because it pulls the wrong PID. that doesn't exist anymore because it pulls the wrong PID.
- Test suite results (in HTML format!) can be found at </para>
../../test_results/security/localhost.1/ </listitem>
--> <listitem>
<para>
Test suite results (in HTML format!) can be found at
../../test_results/security/localhost.1/results.html
</para>
</listitem>
</itemizedlist>
</note>
<para> <para>
Now, as the <systemitem class="username">root</systemitem> user: Now, as the <systemitem class="username">root</systemitem> user: