ISOMAN

Artifact

metal-arm64.iso

Talos Linux · 1.13.6 arm64 metal standard · iso · 212 MB

Checksums

sha512
df82a05a8df6dd2e29a6d82bf00d97b3f3fe9ce920502498f48117939c6237e27e03f61237160c2fd2c8c5a8bd148f5f23e4bb8bd2836a7bfba0e2c1f767a587
Checksum source
sha1
7905c8cb3e18077f0f79a3b23b41d1afc71a0027
Checksum source
md5
8d770466c706dcba0853131666e62312
Checksum source
sha512
80fa834ea1af128d73afe70da90a5400810425b84bdd07585aa71385628270faca64ed3b266badb9580b2c65902fe001abae5c3a56290a15a5ff047f67e8485d
Checksum source
sha512
ce950927617f2bf0e40e45679371c4c922653baba03ea16afacb2fed9b3405a03728d1a19df782707201853b47acaa73dd3e53a80d9bd9e73fc38a4a04c4147b
Checksum source
sha512
cb7da296fccfacadc00962a98fe9c5f08d6c0fcae5e0386f04b1be5ac6bdc37e3b8430e043c8c1f03225e9426e57729272d1b2b1d5367889bad13fd154361bd1
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.6/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.