Index: general/prog/rust.xml
===================================================================
--- general/prog/rust.xml	(revision da58f1aef1292b80998d93628ba991a787f57a2b)
+++ general/prog/rust.xml	(revision ca97a2a1e384fd84b87c2962c188241d87acd7a1)
@@ -7,6 +7,6 @@
   <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz">
   <!ENTITY rust-download-ftp  " ">
-  <!ENTITY rust-md5sum        "6d1728cf0a86b0c5f33d3870379997ed">
-  <!ENTITY rust-size          "172 MB">
+  <!ENTITY rust-md5sum        "275744c77bf07fd07abe0fd829e6dafb">
+  <!ENTITY rust-size          "176 MB">
   <!-- Gentle Reminder: buildsize is how much the user requires for the real
        install, i.e. the source with its DESTDIR *plus* the DESTDIR.  You
@@ -14,7 +14,7 @@
        to measure it, or du -sm to look at the size of the build tree before and
        after the tests. -->
-
-  <!ENTITY rust-buildsize     "8.8 GB (370 MB installed) including 309 MB of ~/.cargo files for the user building this. Add 6.2 GB including extra 273 MB of ~/.cargo files if running the tests">
-  <!ENTITY rust-time          "27 SBU (including download time; add 13 SBU for tests, both on a 4-core machine)">
+	
+  <!ENTITY rust-buildsize     "8.7 GB (417 MB installed) including 296 MB of ~/.cargo files for the user building this. Add 6.5 GB including extra 281 MB of ~/.cargo files if running the tests">
+  <!ENTITY rust-time          "25 SBU (including download time; add 13 SBU for tests, both on a 4-core machine)">
 ]>
 
@@ -84,5 +84,5 @@
         have reason to rebuild with a modified configuration (e.g. using the
         shipped LLVM after building with shared LLVM, perhaps to compile crates
-        for architectres which the BLFS LLVM build does not support)
+        for architectures which the BLFS LLVM build does not support)
         it is possible for the install to leave a broken
         <command>cargo</command> program. In such a situation, either remove
@@ -308,9 +308,10 @@
     </para>
 
+<!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used
 <screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \
        -e '/^curl-sys /s/0.4.48/0.4.50/' \
-       src/tools/cargo/Cargo.toml &amp;&amp;
-
-export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &amp;&amp;
+       src/tools/cargo/Cargo.toml &amp;&amp; -->
+
+<screen><userinput>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &amp;&amp;
 python3 ./x.py build --exclude src/tools/miri</userinput></screen>
 
@@ -333,11 +334,11 @@
 
     <para>
-      At a minimum, fifteen tests will fail: all the tests (twelve) in
-      the <quote>assembly</quote> suite, apparently because warnings are
-      tuened on,
-      run-make-fulldeps/long-linker-command-lines, run-make-fulldeps/print-cfg,
-      run-make-fulldeps/sysroot-crates-are-unstable.
-      If <command>gdb</command> is installed,  another failure
+      At a minimum, 49 tests will fail: all 48 of the tests in
+      the <quote>assembly</quote> suite which are not skipped (various lints
+      cause the warnings in these tests to be treated as errors), and
+      run-make-fulldeps/long-linker-command-lines.
+<!--  If <command>gdb</command> is installed,  another failure
       (debuginfo/function-names.rs) can be expected.
+      # seems ok with 11.2 ken -->
     </para>
 
@@ -345,5 +346,5 @@
       As with all large testsuites, other tests might fail on some machines -
       if the number of additional failures is in the single digits,
-      check the log for 'FAILED' and review lines above that, particularly the
+      check the log for 'failures:' and review lines above that, particularly the
       'stderr:' lines. Any mention of
       SIGSEGV or signal 11 in a failing test is a cause for concern.
@@ -449,5 +450,5 @@
     </para>
 
-    <para>
+<!--<para>
       <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates
       normally downloaded for this release do not correctly initialise
@@ -455,5 +456,5 @@
       <application>openssl-3.0.0</application>. Upstream has fixed that for a
       future release, this sed causes the fixed versions to be used.
-    </para>
+    </para>-->
 
     <para>
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision da58f1aef1292b80998d93628ba991a787f57a2b)
+++ introduction/welcome/changelog.xml	(revision ca97a2a1e384fd84b87c2962c188241d87acd7a1)
@@ -43,4 +43,14 @@
     -->
     <listitem>
+      <para>January 24th, 2022</para>
+      <itemizedlist>
+        <listitem>
+          <para>[ken] - Update to rustc-1.58.1 (Security Update). Fixes
+          <ulink url="&blfs-ticket-root;16003">#16003</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>January 23rd, 2022</para>
       <itemizedlist>
Index: packages.ent
===================================================================
--- packages.ent	(revision da58f1aef1292b80998d93628ba991a787f57a2b)
+++ packages.ent	(revision ca97a2a1e384fd84b87c2962c188241d87acd7a1)
@@ -377,5 +377,5 @@
 <!ENTITY ruby-version                 "&ruby-minor-version;.&ruby-patch-version;">
 <!ENTITY ruby-gemdir                  "/usr/lib/ruby/gems/&ruby-minor-version;.0">
-<!ENTITY rust-version                 "1.56.1">
+<!ENTITY rust-version                 "1.58.1">
 <!ENTITY scons-version                "4.2.0">
 <!ENTITY slang-version                "2.3.2">
