ISOMAN

Artifact

metal-amd64.iso

Talos Linux · 1.13.9 amd64 metal standard · iso · 334 MB

Checksums

sha512
f867b58684ff2bbc44306fae446eee5f9e81de694d13bbbf9207154b3e7b7866478c88bd9c8e6487f4b9e8999b5a34c344911e4e3ba1a7db7deea4732642fd89
Checksum source
sha1
31c9feb5d45de188f0a3f8605667deaedcd5cdfa
Checksum source
md5
effdecaed376fb05e29ef675024cb986
Checksum source
sha512
e4f9bcd99f6a2be972371601d264536aae0c568f446c78d543e3cb2ed4d4f39fe7260735b6ab5a5f45d2da222c094f97fb344eda6f61d35596cffca4dea602d9
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.13.9/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.