Update webpage "News" from version "1.1.0-beta.1" to "1.2.0-beta.1"

This commit is contained in:
inference 2024-04-01 20:45:42 +00:00
parent 3c9f3f962a
commit ba75ef7104
Signed by: inference
SSH Key Fingerprint: SHA256:K/a677+eHm7chi3X4s77BIpLTE9Vge1tsv+jUL5gI+Y

View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<!-- Inferencium - Website - News -->
<!-- Version: 1.1.0-beta.1 -->
<!-- Version: 1.2.0-beta.1 -->
<!-- Copyright 2024 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -48,7 +48,9 @@
<h2><a href="#2024-04-01">2024-04-01</a></h2>
<article id="key-ssh-update-20240401">
<h3><a href="#key-ssh-update-20240401">SSH Key Update</a></h3>
<p>On 2024-03-29, a backdoor was discovered in the
<p>On 2024-03-29, a
<a href="https://www.openwall.com/lists/oss-security/2024/03/29/4">backdoor was publicly disclosed</a>
in the
<a href="https://git.tukaani.org/?p=xz.git">xz-utils</a>
software. Inferencium systems <strong><em>did</em></strong> have the affected versions of
this software installed, and the tools were used. The software has since been downgraded to
@ -74,7 +76,7 @@
attack due to musl not supporting the required <code>IFUNC</code> functionality.</p>
<p><strong>Despite the evidence, it is unknown exactly what this malicious code does and is
capable of in entirety. As a precautionary measure, I have generated a new SSH key and
classifed the previous key as compromised. You can find my new key on the
classified the previous key as compromised. You can find my new key on the
<a href="key.xhtml#ssh-current-2">Key webpage</a>.</strong></p>
<p>There is no evidence that my previous key was compromised, so this is entirely a
precautionary measure. All files and Git commits, tags, and releases signed with the