pure/serve/tls.h, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-09-29T06:06:27ZPut the links and the crypto they use in link/, a part of their own2026-09-29T06:06:27Zeunhhunecpition205@gmail.com2026-09-29T06:06:27Zurn:sha1:a052b95c8135cdc5f9b91f8efc991cac80fbbe8b
libpure-link.a holds them; pure-serve and the M5 harness link it instead
of naming its source files.
Map OpenSSL only in a server that uses it2026-09-27T18:03:34Zeunhhunecpition205@gmail.com2026-09-27T18:03:34Zurn:sha1:8019260926dcebe4f4be99cb5f92f84fbc9cd6d3
Linking OpenSSL cost every pure-serve 2.3 MiB of resident memory, 0.66
MiB of it the process's own (relocated data), though most servers never
reach an https receiver or seal a send. The code that uses OpenSSL (TLS
to https receivers, sealing) is now built as pure-crypto.so beside
pure-serve and exports one table; pure-serve maps it the first time a
wire to an https URL opens or a key is read or a seal wired
(serve/crypto.c), and a missing library is reported at startup. What
needs no OpenSSL, a key's hex and the suite this CPU seals with, stays in
pure-serve.
An idle server: RSS 4,496 -> 2,320 kB, PSS 1,639 -> 881 kB, private
dirty 1,296 -> 864 kB. A static OpenSSL was measured too and is worse
(RSS 3.8 MiB, but 2.3 MiB private: all of its tables relocated). The
checks, https webhooks and sealed sends included, pass unchanged.