HTTPS web server and automatic certificates — your device as a safe front door
What it is
NanumOS can serve a web site over HTTPS by itself. httpsd takes encrypted connections (TLS 1.3 and 1.2), and acme gets free certificates from Let's Encrypt and renews them before they run out. No separate front program (reverse proxy) is needed.
Basics
How to use it
- Check:
u httpsd --checklists the certificates it would use, days left and names (never the keys).acme statusshows the last renewal result. - First start with no certificate:
httpsdmakes a self-signed one for this device's name andlocalhost(selfsigned.crt), so HTTPS answers at once; browsers warn until you add a real one (acme add) or trust this one. - Renewal:
acme addputs a scheduled job (23 4 * * * acme renew) in your crontab; every day it checks and gets a new certificate once 2/3 of the old one's life has passed. httpsd reads a changed certificate within 5 seconds (no restart).
How it works
When a visitor (a browser) connects, httpsd reads the first greeting (ClientHello) for the name (SNI) and the TLS version. Visitors that speak TLS 1.3 get our 1.3 engine, written from RFC 8446; visitors that speak only 1.2 get BearSSL's 1.2 engine. The certificate is chosen by name (exact name, then a *. wildcard, else the first file), and the ECDSA or RSA key by the signature methods the visitor accepts. Only current ciphers: TLS 1.3 AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305; TLS 1.2 the same three with ECDHE (old CBC, RSA key exchange and TLS 1.0/1.1 are refused). A returning visitor gets a short handshake (1.2 session ID, 1.3 ticket — never across names). One connection carries many requests in turn (keep-alive).
Technical details
- Code:
user/cmds/httpd.c(httpsd is the same source built with TLS),user/tls/tlsserv.c(certificate choice, session cache, 1.2),user/tls/tls13.c(TLS 1.3: x25519 and P-256 key exchange, HelloRetryRequest, PSK tickets, RSA-PSS),user/tls/acme.c,acmejson.c. Contractdocs/contracts/HTTPS.md. - Key bytes are never printed — not on the screen, in a log or in a state file. A new key is made at each renewal.
- The new parsers that read network bytes (ClientHello, records, tickets, ACME JSON, HTTP requests) are fuzz targets (
tests/fuzz/tls13,acme,httpd). - No HTTP/2 yet (the plan is in the contract). No OCSP stapling.
What this app takes and sends
| Takes | Only on acme add / acme renew: the certificate chain from acme-v02.api.letsencrypt.org (acme-staging-v02.api.letsencrypt.org with --staging). Nothing else. |
| Sends | To Let's Encrypt: the account's public key, the contact e-mail if you gave one, and the names for the certificate. Let's Encrypt sees this device's internet address and connects to door 80 of this device to check. Issued certificates are public (Certificate Transparency logs) — the names become public. Our servers see nothing. |
| For how long | Until acme remove NAME stops renewing and you delete the files. |
| How to turn it off | Without acme add nothing is sent. Removing the acme renew line (crontab -e) stops automatic renewal. |
| Without internet | acme says why in one line and stops. httpsd keeps serving the certificates it has. |
Frequently asked
Must port 80 be open?
For now, yes (the HTTP-01 check). Places that cannot open port 80, and wildcards like *.example.org, need the DNS-01 check: the place for it is built, but no plug-in for a DNS provider exists yet. acme then says exactly that.
How do I know a certificate is about to run out?
The Assistant's health check (os_check) has an "HTTPS 인증서" (HTTPS certificates) row: under 20 days is a warning, under 7 days a fault, and a failed renewal shows as a warning with its reason.
Why are TLS 1.0 and 1.1 refused?
They are old and not safe, and every current browser speaks 1.2 or 1.3.
Can my key leak?
Key files are readable by you only (600); a key others can read is not used. Key contents are never printed anywhere.
NanumOS 0.1.8349 · 2026-11-16