'%3e%3cpath%20d='M12%2012H84V84H12V12Z'%20fill='%23263238'/%3e%3c/g%3e%3c/svg%3e)
dhi.io/ktls-utils
ktls-utils
Handshake service for kernel TLS consumers
pushed 20 hours ago
linux/amd64, linux/arm64
34.67 MB
for linux/amd64
128
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About ktls-utils
ktls-utils provides a TLS handshake user agent (tlshd) that services TLS handshake requests on behalf of kernel TLS consumers. In-kernel TLS consumers need a mechanism to perform TLS handshakes on connected sockets to negotiate TLS session parameters that can then be programmed into the kernel's TLS record protocol engine.
This package materializes kernel socket endpoints in user space to perform TLS handshakes using the GnuTLS library. After each handshake completes, tlshd plants negotiated session parameters back into the kernel via standard kTLS socket options, enabling the kernel to handle the TLS record protocol for subsequent communication.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with zero-known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
ktls-utils is a trademark of Oracle Cooporation. All rights in the mark are reserved to Oracle Cooporation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.