Repository navigation
esrun@0.46.0
Security
-
Mutual TLS (DECISIONS D201).
serveandlistentakerequestCert,
caandcrlto require client certificates, always verified — there is
norejectUnauthorized. The handler'sinfo.peerCertificateand an
accepted socket'sopened.peerCertificatecarry the verified certificate
(subject,subjectaltname,fingerprint256,raw,validFrom,
validTo). Clients present one withcert/keyonruntime:net
connect,sslCert/sslKeyon the PostgreSQL and MySQL drivers,
cert/keyortlsCertificateKeyFileon MongoDB (withMONGODB-X509
authentication), and Bun'stls: { ca, cert, key }onfetch, which gets a
connection pool of its own. -
Certificate rotation (D200):
server.setSecureContext({ cert, key })on
a TLSserveserver orlistenlistener replaces its credentials for new
connections without dropping open ones, and refuses a key that does not
belong to the certificate. -
Revocation (D202):
--tls-crl=<file>checks every TLS client's servers
against operator-supplied CRLs, andcrldoes the same for client
certificates. A CRL past itsnextUpdaterefuses what it covers; nothing is
fetched over the network. -
TLS prefers the hybrid post-quantum key exchange X25519MLKEM768 in every
client and server (DECISIONS D199). The build had turned rustls's
preference off, so handshakes used plain X25519 first. -
esrun upgradeverifies what it installs (DECISIONS D198). It replaced
the running binary with the downloaded archive without checking it, though
the CLI reference said it did. It now refuses a release that publishes no
checksums.txt, or whose archive's SHA-256 does not match it, and leaves the
installed binary untouched. The new binary is written beside the old one and
renamed into place, so an interrupted upgrade never leaves half a binary.
Drafts and pre-releases are no longer offered, and there is no progress bar. -
fetchruns on the runtime's own HTTP client (D198): hyper's framing
and hyper-util's connection pool, with redirects, content codings and
deadlines written to their specifications. Following a redirect now drops
the body'sContent-*headers when the method becomesGET, rejects rather
than resending a streamed body, and dropsCookie2andWWW-Authenticate
along withAuthorization,CookieandProxy-Authorizationon a hop to
another origin. A decoded body arrives at most 64 KiB at a time.
TCP_NODELAYis on. reqwest,self_updateandrustls-platform-verifier
are gone, takingsecurity-framework,core-foundationand the system
proxy readers with them: 25 to 26 fewer crates on each platform. -
Every TLS client verifies against one trust store (DECISIONS D197).
fetchand the--otelexporter checked the operating system's store
whileruntime:net, the database drivers andWebSocketchecked the
bundled Mozilla roots, so a CA one API trusted another refused, and
SSL_CERT_FILEchanged whomfetchalone trusted. All of them now use the
bundled Mozilla roots, or exactly what the new--tls-calists. A private
CA installed only in the operating system is no longer trusted byfetch:
name it with--tls-ca=bundled --tls-ca=<file>. -
--tls-ca=<file|bundled>(repeatable) sets the process trust store. A file
that cannot be read, holds no certificate, holds a private key or any other
non-certificate block, or has a certificate outside its validity period stops
startup, naming the file but never quoting it. No environment variable
changes trust; esrun warns whenNODE_EXTRA_CA_CERTS,NODE_USE_SYSTEM_CA,
DENO_CERTorDENO_TLS_CA_STOREis set. -
fetchand the--otelexporter no longer readHTTP_PROXY,
HTTPS_PROXY,ALL_PROXYor the operating system's proxy settings. The
HTTP client enabled them by default, so an inherited environment variable
could route every outbound request through a host the deployment never
named. Requests now go to the host in the URL. -
The bundled TLS root certificates (
webpki-roots1.0.11) no longer trust
"emSign Root CA - C1" or "emSign ECC Root CA - C3". Mozilla removed them
after the October 2026 compromise of eight eMudhra intermediate CA keys;
"emSign ECC Root CA - G3", the root that signed those intermediates, was
already dropped in 1.0.10. Applies to every TLS client.
Fixed
install.shsupports the fish shell: asked to add ES Runtime toPATH, it
writes~/.config/fish/conf.d/es-runtime.fish(honouring
XDG_CONFIG_HOME) withfish_add_path, instead of appending a POSIX
exportline to~/.bashrcthat fish never reads. The manual instruction
is printed in fish syntax too.
Changed
-
The site footer centers a visibly external Foundation policies link without
changing the AFW badge's position. -
The footer states that the site uses no trackers or analytics.
-
Footer text colors meet WCAG AA contrast against the dark footer background.
-
The AFW footer badge icon uses black strokes.
-
Update the website AFW packages; adapt benchmark components to the current
compiler's single final view return requirement. -
The site's benchmark data is re-measured with esrun 0.45.0 (esdev 0.24.0,
node 26.13.0, bun 1.4.4, deno 2.9.7, llrt 0.9.0-beta, PostgreSQL 18.6) — the
previous full run published 0.43.0 against node 24 and PostgreSQL 16 — and
now includes thejsonc_largeandjson5_largerows.
website/src/versions.jsis regenerated to match. Eleven esrun rows are more
than 10% faster;crypto_asym(ECDSA P-256 sign + verify) is 55% slower,
the cost of the move to the 0.14 NIST curves for RUSTSEC-2026-0387. -
Benchmark charts expose row and column relationships to assistive technology;
animated benchmarks can be paused from the keyboard, and selector controls
announce their pressed state. -
The durable-worker diagram keeps commit and restart markers visible without
motion and improves the storage-link contrast.