ISOMAN

Artifact

metal-amd64.iso

Talos Linux · 1.12.8 amd64 metal standard · iso · 317 MB

Checksums

sha512
43dd147322c56950da4910ea646418b3f963ff0fe9863a3e5f42be14832274d50f105141f9ac2b2f4a5d83ac11ea7a9fc85db99c8f8f8b982aa6582c35ad46e7
Checksum source
sha1
769c4e6a11b7d655daed56a2b3f3e6c8cd901bd7
Checksum source
md5
f8d650d71109ad57487d71b2268ed6ef
Checksum source
sha512
a5c96dbb12fa0fd5b12b87e703b04553e6f68a715520572ca71b00956b5e407d94d46efdafc9ceb2bb3788a453dbc18064c1647d29dd575a85dcebb4ecdcdf14
Checksum source
sha512
8e4847769329a1e91963457ce237f8f27818d1c3b1724368e51fb2f1985bf70a516cdb72b5857c7deb55d61aba3f1ad054ad04965962fecece3879a258754120
Checksum source

Quality

Confidence
1.00
Missing checksum
no
Missing architecture
no
Stale downloads
0
Audited

Download Sources

ProtocolTypeStatusURL
httpsofficial-mirror · download_pageok 200https://sourceforge.net/projects/talos-linux.mirror/files/v1.12.8/metal-amd64.iso/download

Related CVEs

  1. CVE-2022-36103

    HIGH · Talos Linux is a Linux distribution built for Kubernetes deployments. Talos worker nodes use a join token to get accepted into the Talos cluster. Due to improper validation of the request while signing a worker node CSR (certificate signing request) Talos control plane node might issue Talos API certificate which allows full access to Talos API on a control plane node. Accessing Talos API with full level access on a control plane node might reveal sensitive information which allows full level access to the cluster (Kubernetes and Talos PKI, etc.). Talos API join token is stored in the machine configuration on the worker node. When configured correctly, Kubernetes workloads don't have access to the machine configuration, but due to a misconfiguration workload might access the machine configuration and reveal the join token. This problem has been fixed in Talos 1.2.2. Enabling the Pod Security Standards mitigates the vulnerability by denying hostPath mounts and host networking by default in the baseline policy. Clusters that don't run untrusted workloads are not affected. Clusters with correct Pod Security configurations which don't allow hostPath mounts, and secure access to cloud metadata server (or machine configuration is not supplied via cloud metadata server) are not affected.