ISOMAN

Artifact

metal-amd64.iso

Talos Linux · 1.13.8 amd64 metal standard · iso · 336 MB

Checksums

sha512
51991c10cac326a45d7bf6a42c27374bc69ee3a3457058dcfb5282e4b08add673324ca964639c1180e52f0d447ae8cd6732b456dc5cd3d7dffce157723ea034b
Checksum source
sha1
d164b6a6c4bdc5a3b8fc4ee7aa464cc47ef5853c
Checksum source
md5
4135b556dd032b32b26b419df52db92d
Checksum source
sha512
918b41e8a25987737d8f76465c579616ed0cc16eafefb3a9cc88fe4acbd9893e0ce77c1dc5ec4ee449facba20b6ae4e51a6d6e5393e5630bf21e5cefc46d4bbb
Checksum source
sha512
f867b58684ff2bbc44306fae446eee5f9e81de694d13bbbf9207154b3e7b7866478c88bd9c8e6487f4b9e8999b5a34c344911e4e3ba1a7db7deea4732642fd89
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.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.