ISOMAN

Artifact

metal-arm64.iso

Talos Linux · 1.12.12 arm64 metal standard · iso · 199 MB

Checksums

sha512
873231bea8f4caa1ac00dc7e194aac65fbff0d135806dd8c93942c54ccb13de24eea1be204ea96195c6cafebb5ec4a5a7bcfdaad13c7661148df160e57ec1d9f
Checksum source
sha1
0cef00d7cc785d0083e72d1771463c59b8d8d29f
Checksum source
md5
911a2523a86b215896682d5e41f4c3b0
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.12/metal-arm64.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.