Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/blackthornyugen/tiny-key-s-server
Container SecurityWeb Proxies & InterceptionSecurity VirtualizationNetwork SecurityCryptographyDevSecOps
GitHubblackthornyugen/tiny-key-s-server

tiny-key-s-server

OpenSSL s_server testing tool for tiny EC private keys for CVE-2026-111943 research.

View RepositoryWebsite
14 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    634
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    417
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    383
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    328
  • 6

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    288

Explore all tools

Browse our collection of tools

View all tools →
Share

tiny-key-s-server

A lightweight, automated containerized testing tool powered by Alpine Linux and OpenSSL s_server for testing with small integers as Elliptic Curve private keys.

It generates a two-tier Elliptic Curve (EC) certificate chain (CA + Server), signs the server certificate with custom SAN extensions (IPs and domain names), captures and echoes all executed OpenSSL commands, and serves a live HTML report explaining how the certificate and key were created while running in -WWW or -www mode.


Features

  • Dynamic EC Key & Chain Generation: Generates a CA key & certificate, a server key & CSR, signs the server certificate using the CA with Subject Alternative Names (SANs), and bundles them into fullchain.pem.
  • Cross-Signed & Multi-Path Chains: Because EC keys $a$ (server) and $b$ (intermediate CA) are fully deterministic, intermediate key $b$ can be pre-signed or cross-signed by external roots ($b \rightarrow c_1$, $b \rightarrow c_2$). The server dynamically bundles certificates and serves either the default chain, a specific cross-signed path (CHAIN_MODE=c1), or all available paths combined (CHAIN_MODE=all).
  • Exact Scalar s Bytes Input: Directly accepts an EC private key scalar $s$ as a hex string (e.g., 0xdeadbeef1337 or deadbeef...) or small integer (e.g., 42), embedding the exact hex scalar into the generated EC private key so that openssl ec -text displays your exact bytes under priv:.
  • Configurable via Environment Variables:
    • Scalars: S_BYTES, SERVER_S_BYTES, CA_S_BYTES.
    • Curves: CA_CURVE, SERVER_CURVE, or fallback CURVE (e.g., prime256v1, secp384r1, secp521r1).
    • Subjects: CA_SUBJECT and SERVER_SUBJECT.
    • SANs: DOMAINS and IPS (comma or space separated).
    • Modes: WWW_MODE (WWW, www, HTTP).
    • Ports: PORT (default 4433).
  • Mounted Volume Support: Automatically detects if pre-existing certificate chains (e.g., fullchain.pem, tls.crt) and private keys are mounted to /certs, serving those instead.
  • Interactive HTML Audit Page: Echoes all commands executed with exit codes, parameters, and decoded certificate details (openssl x509 -text -noout and openssl ec -text -noout). In -WWW mode, visiting https://<host>:<port>/index.html renders this full report with one-click PEM file downloads.
  • Helm Chart & ArgoCD Integration: Production-ready Helm chart (chart/) and ArgoCD Application (argocd/) matching Gitea CI/CD pipelines.

Quick Start

1. Run with Custom Scalar s Bytes (Hex)

docker run -p 4433:4433 \
  -e S_BYTES="0xdeadbeef1337" \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

When running openssl ec -in server.key.pem -text -noout, the private key scalar displays:

priv:
    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:00:00:00:00:00:00:00:00:00:00:de:ad:be:ef:
    13:37

2. Run with Integer Scalar s

docker run -p 4433:4433 \
  -e S_BYTES="42" \
  -e DOMAINS="localhost,test.internal" \
  -e IPS="127.0.0.1,192.168.1.100" \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

3. Run with Independent CA and Server Scalars

docker run -p 4433:4433 \
  -e SERVER_S_BYTES="0xdeadbeef" \
  -e CA_S_BYTES="0x1337c0de" \
  -e CA_CURVE="prime256v1" \
  -e SERVER_CURVE="prime256v1" \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

4. Run with Mounted Volume Override

If you have pre-generated certificates (such as Let's Encrypt or Vault certs):

docker run -p 4433:4433 \
  -v /path/to/my/certs:/certs:ro \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

When fullchain.pem (or tls.crt) and privkey.pem (or tls.key / server.key) are present in /certs, the container inspects and serves them directly without generating new certificates.

5. Multi-Path and Cross-Signed Chains ($a \rightarrow b \rightarrow c_1 / c_2$)

Because keys $a$ (server, scalar $s$) and $b$ (CA, scalar $s+1$ or CA_S_BYTES) are deterministic, intermediate key $b$ can be pre-signed by external root CAs ($c_1, c_2, \dots$) ahead of time, or roots can be mounted to be signed automatically on startup.

Providing Chains via Volume Mount

Place cross-signed chain PEMs in /certs/chains/:

  • /certs/chains/c1.pem (contains $b$ signed by $c_1$, and optionally $c_1$)
  • /certs/chains/c2.pem (contains $b$ signed by $c_2$, and optionally $c_2$)
# Serve specific cross-signed path (a -> b_c1 -> c1)
docker run -p 4433:4433 \
  -e S_BYTES="0x01" \
  -e CA_S_BYTES="0x02" \
  -e CHAIN_MODE="c1" \
  -v /path/to/chains:/certs/chains:ro \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

# Serve all paths concatenated in fullchain.pem (a -> b_c1 + b_c2)
docker run -p 4433:4433 \
  -e S_BYTES="0x01" \
  -e CA_S_BYTES="0x02" \
  -e CHAIN_MODE="all" \
  -v /path/to/chains:/certs/chains:ro \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

Providing Chains via Environment Variables

For CI/CD or lightweight execution without volume mounts:

docker run -p 4433:4433 \
  -e S_BYTES="0x01" \
  -e CHAIN_MODE="all" \
  -e EXTRA_CHAIN_PEM="$(cat extra_chain.pem)" \
  ghcr.io/blackthornyugen/tiny-key-s-server:latest

Automatic Root Signing

Mount external root CA certificates and private keys to /certs/roots/:

  • /certs/roots/c1.crt and /certs/roots/c1.key

On boot, the container automatically generates an intermediate certificate for key $b$ signed by root $c_1$, and makes it available under CHAIN_MODE="c1" or CHAIN_MODE="all".


Connecting & Testing

Web Browser / cURL

In -WWW mode, fetch the HTML report:

# Insecure (skip CA verification)
curl -k https://localhost:4433/index.html

# Download the generated CA certificate
curl -k -O https://localhost:4433/ca.crt.pem

# Secure request using the downloaded CA
curl --cacert ca.crt.pem https://localhost:4433/index.html

OpenSSL s_client

Connect and inspect the certificate chain in the terminal:

openssl s_client -connect localhost:4433 -showcerts

Environment Variables

Download Tool