Skip to content

wisp 0.0.8

Latest

Choose a tag to compare

@vcealicu vcealicu released this 13 Nov 21:19
· 18 commits to main since this release

LocalGhost wisp 0.0.8

Cut on 13 November 2026. The eighth cut of wisp; the name is the release line, the number the
cut. Everything in 0.0.1's notes still holds, and the pages for 0.0.2,
0.0.3, 0.0.4, 0.0.5, 0.0.6 and
0.0.7 say what each cut changed.

A box on 0.0.7 that takes 0.0.8 gains two columns and a table at its first unlock (the schema
converges by itself) and, in the first pass ten minutes later, folds every month that ended six
weeks ago or more: MEMORIES shows a month where it showed that month's days, and the days are
one tap down. The links between memories are drawn in the same pass, and the first chat of each
day chooses the front page. Over the days that follow, a "?" appears beside any memory the box
read again and could not find in the record it came from. Clips get their running time when
ghost.framed starts. redeploy.sh installs the box's firewall table, which existed only as
typed commands before; sudo ./tools/server_setup_root.sh, run once more, narrows the sudo
rule and turns security updates on; sudo ./tools/privacy_check.sh should then show both model
servers refusing a request that comes without their key. A box with backups switched on should
run ghost-cli ghost.framed backup full=true once: no photo original was in a backup before
this cut. A phone on 0.0.7 keeps its pairing, and moves its web search key into the phone's
encrypted store the first time it is read. The relay's own changes are in the web repository
(deploy/mail): root-once.sh once more for the new certificate hook, then install.sh.

Built with Go 1.27.4, where 0.0.4 to 0.0.7 were built with 1.27.1. The three releases between
carry security fixes to crypto/tls, crypto/x509, net/http, net/textproto and os, which
are the packages the box's door and its mail are made of; 0.0.7 was cut two weeks after the
first of them. redeploy.sh brings a box's Go up to the release's from the mirror before it
builds, as it always has. The app builds with Gradle 9.9.

What changed since 0.0.7

  • Mail reads as paragraphs. The first message through the relay (24 October, Gmail to the box,
    the first round trip) reached the phone as three-word tails: Gmail breaks plain text at 76
    columns and does not say so. The box now honours format=flowed where a sender declares it
    (RFC 3676, DelSp too) and, where none is declared, joins the lines a wrapper broke, by the
    wrapper's own rule read backwards (a line was broken before a word only if the word did not
    fit the widest line), leaving lists, indented text, blank lines, quotes at another depth and
    the signature separator alone; runs of blank lines stop at two. Messages already on the box
    keep the text they were stored with; the sealed original is untouched either way.
  • The app's buttons keep their label on one line. Three in a row (ARCHIVE, UNREAD, DELETE under a
    message) used to break the word; the label shrinks a step instead and the button's side
    padding is a third of the Material default.
  • Mail reaches the phone seconds after it is delivered, not minutes. Three waits were stacked:
    the relay looked at its queue every half minute, the box asked the relay every two minutes, and
    SENT reloaded only when opened. The relay now delivers the moment a box posts, the box asks
    again at 4, 10, 25 and 60 seconds after a send, and SENT reloads every four seconds while a
    row still says "waiting at the relay".
  • The relay sends from its IPv4 address. Its first message to Gmail went from the box's IPv6,
    which the SPF record does not name, and failed SPF; the relay now dials receivers over IPv4
    first and IPv6 only for a host with no IPv4 address.
  • An OpenPGP implementation of the box's own, internal/pgp, for end-to-end encrypted mail
    (the next cut wires it into MAIL): version 4 keys, Ed25519 and Curve25519 for the box, RSA
    and the NIST curves accepted from others, AES-256 in the integrity-protected packet, SHA-256
    signatures, the three compressions on read, armor. Built on the standard library's primitives
    alone, 1,900 lines, tested against GnuPG 2.4 both ways (its keys and ours, each compression,
    signing subkeys, a NIST key, an expired key). Nothing in MAIL changes yet.
  • ghost-ctl doctor: the box's own check-up, one screen of PASS/WARN/FAIL with the fix on the
    next line. Every port open to the network and the process and user holding it, with anything
    of the box's on a public address other than 80, 443 and the relay's 25 a FAIL (secd's plain
    port, the vault's databases, a node's RPC, the model server, code-server); the firewall
    tables; nginx and the edge's two shapes agreeing with /etc/ghost/edge; certificate expiry,
    the box's and Let's Encrypt's; ssh keys-only and no root; unattended security updates and a
    pending reboot; every mail DNS record the box needs looked up, and the relay's PTR and
    greeting; the box's name answering on 443. It changes nothing (tools/README.md 8e).
  • The firewall table is part of the tree. tools/nft/localghost.nft keeps secd's plain
    loopback port to root and nginx (the audit's forged-header hole, closed in the kernel);
    tools/firewall.sh installs it under /etc/nftables.d with /etc/nftables.conf including
    the directory, so it survives a reboot, and server_setup_root.sh and redeploy.sh run it.
    The relay's own table (port 25 limited per source, nothing on IPv6) is installed the same way
    by its root-once.sh in the web repo. Both are tables of their own; the machine's other rules
    are not touched. Until now these rules existed only as commands typed on one box.
  • server_setup_root.sh installs nftables and unattended-upgrades and turns security updates
    on; redeploy.sh no longer re-renders the ghost-secd nginx site on a box with the stream
    passthrough (that put a second listen 443 beside the stream's); ghost-setup makes the
    daemons' user by the name given (--user), not a ghost user it never used.
  • GALLERY refreshed. A video is told from a photo at a glance: its cell wears a green frame with
    ▶ and the running time at the foot (the box now reads a clip's duration from its header and
    fills older rows in at start), and a "[ ▶ videos ]" switch shows the clips alone. The frame's
    card is new: the picture at its own shape rather than a square, "> VIDEO · 1:42" or "> PHOTO"
    as the heading, the name, when and how big, where, what the box saw, and the tags as chips in
    their groups (people, place, event, activity …), each with its ✕ and a line to add one. A
    result opened from the search now shows its tags, place and description too; it used to say
    "none yet" for tags it had plainly matched on. The screen stays on and the phone does not lock
    while a clip plays or a slideshow runs.
  • The box reads its memories again. A memory distilled from a chat or a note was written once and
    then believed, so a misreading lived on in every later answer. Now, once a day on the GPU, a few
    per pass, synthd fetches the record a memory was made from and asks the model whether the record
    says this; YES stamps it, NO or PARTLY puts it in doubt with the record's own words beside it
    (kept only when its names and numbers are in the record). A doubted memory stays, marked "?" in
    MEMORIES with what was found on its page, out of the chat's grounding and out of a person's
    written body, until you edit, delete or leave it. Facts about people are checked one by one.
    Your own edits are never read again; nothing is deleted. ghost-cli ghost.synthd read-again.
  • A second security audit (10 November), and what it changed. The first audit's fixes held;
    this one went through what had been built since and what had been left for later. Three
    areas were not covered that day (the mail relay, local privilege boundaries on the box, the
    media parsers); they were gone through on 12 November, further down this page.
    • Unlock. The PIN is always tried through the attempt limiter, and a second phone arriving
      during a running unlock waits for its own turn instead of being handed the first one's; a
      wrong PIN counts against the phone that typed it and ends that phone's session, not the
      owner's; behind nginx, the certificate in the header is verified against the box's device
      CA, where any non-empty header used to pass.
    • Root's writes onto the vault. ghost.secd runs as root and puts the phone's uploads into
      folders the daemons' user owns. It did so by path, so a daemon that had been taken over
      could point root's writes, and the ownership root hands over, at any directory on the
      machine. Every such write (photos, notes, voice, health, news batches, mail, refreshed
      binaries, model weights) now walks down from the volume's root without following a link
      and owns files through their descriptors.
    • Where the box connects. The box's own fetches (feeds, linked articles, coin sites, the
      weather centres) are https only, to public addresses only, checked again at the
      connection, five redirects at most, and the Met Office key never follows a redirect to
      another host. A link in a feed can no longer make the box ask its own loopback or the
      router. A page that is not UTF-8 no longer takes ghost.synthd down, and a fault in reading
      anything from outside costs one pass, not the daemon. A feed is kept to its first 300
      entries.
    • Mail. What MAIL shows as the sender is the address the checks were run on, by one reading
      of the header; an address that is not a plain one (a quoted name with spaces, built so
      that a cut shows someone else's address) is shown as "an unreadable sender" and scored.
      Names and subjects are one line with hidden direction marks removed and named. "Looks
      genuine" is said only when the From domain was proven; otherwise "no signs of spam, sender
      not proven". A signature over part of a body does not count, two strangers under an
      unlisted com.xx no longer align with each other, a slow SPF lookup no longer starves the
      DMARC one. A very long hard-wrapped message is read in its length, not its square (1.4 MB
      took almost five minutes), and a short last line is no longer pulled into the paragraph
      before it. Web pages and SVGs as attachments are not kept.
    • Backups. The nightly backup now holds the photo and video originals. It had been sealing
      framed/ (the Timeline folders) when the archive is frames/archive: no original was ever
      in a backup. Incrementals go by when a file landed, not the photo's own date; every backup
      ends with a manifest of what the box held; ghost.restore unseal file out.tar writes
      nothing unless the whole file authenticated. A box with backups already switched on should
      run ghost-cli ghost.framed backup full=true once.
    • Deletes. Deleting a chat takes its copy out of the journal (it used to stay, and memories
      were made from it afterwards); the day's story drops the model's text when words it was
      written from are taken back, and a day with nothing left is not told; forgetting a day's
      fixes removes its path and route files; a memory you deleted is not written again when the
      note about you is re-read. Memory titles and record quotes no longer go to the INFO log.
    • The read-again pass (not yet released when audited). It no longer doubts a fact that has
      no record to be read against (every fact from a check-in was doubted without asking the
      model), reads a check-in's facts against the check-in, and a YES stands only when the
      memory's names and numbers are in the record.
    • The app. "Use on-phone models only" on the lock gate drops the box session (it opened the
      whole app on the stored two-day session with no fingerprint and no PIN); "re-scan the box
      QR" asks for the phone's unlock first; a picker or the camera left open more than two
      minutes, or the screen going dark, means the gate; text shared from another app is shown
      and asked about before it becomes a note; LOCK drops the phone's session even when the box
      did not answer, and says the box is still open; a finished clip and a slideshow no longer
      hold the screen on for ever. A photo attached to a chat is decoded and fitted on the box
      like any other before the model sees it.
    • OpenPGP (internal/pgp, still not wired into MAIL). A genuine signed message with other
      data attached no longer comes back as that data with the signer's name; revocations count
      wherever they stand (GnuPG writes them first); the newest subkey binding decides; critical
      subpackets the box does not know make a signature unusable; keys and messages are bounded
      (RSA to 8192 bits, signatures per key, packets, decompressed size); a key is judged again
      at the time it is used.
  • The chat looks things up more readily. In auto mode the phone used to ask the box for a
    search plan only when the question held a word from one list (today, price, latest …), so
    "who built hagia sophia" was answered from what the model remembered. Now the box's model is
    asked about every question that is not small talk and not plainly about your own life; it
    is told to search when unsure, to cover two readings of an unclear question, and to name the
    subject, and it always gives three searches so a thin first round has one left to try. The
    plan no longer waits behind a photo being described (it used to time out there and the phone
    gave up on the web). The box's Wikipedia is tried by the question's own words when they are
    typed without capitals, and by what the plan says the question needs when a follow-up names
    nothing; on the phone, the plan's subject fetches Wikipedia's summary beside the search
    results. Every search is shown in the answer's trail before it leaves, and is held to a rule
    on the box and again on the phone: nothing in the first person, no address, no long number,
    and none of your people's names unless you typed the name yourself.
  • The known gap "mail from a home connection refused by the large receivers until the sending IP
    has a reverse name" is softened to the spam folder: Gmail took the box's first message on the
    first try and filed it in Spam.
  • "Feels like" counts the sun. The box's own forecast gave the shade figure at all hours: 3°
    and "feels -2" at noon under a clear sky. With the sun up and the cloud letting it through,
    what a person standing in it absorbs is added (Steadman's term, from the sun's height and the
    cloud cover): the same hour reads about 5°. At night and under full cloud nothing changes.
  • The areas the second audit did not reach, and the app end to end (12 November):
    • The phone. A paired phone no longer takes another box's QR on sight: it stops, names both
      boxes, and pairs only on ENROL. Enrolling again starts clean (the old session's token and
      caches went to the new box before). WIPE THIS PHONE now also takes the session token,
      voice notes not yet sent, the last news, prices and weather, the map's last view and the
      search key. Links in feeds, coin pages and search results open only when they are web
      addresses. A web page built to be slow can no longer hold a core for minutes. Other apps
      cannot draw over the app, and the PIN screen is blank in a screen share. The app's network
      policy is named and allows no cleartext anywhere. The crash report shown before the gate
      says where, not what was being read. A release's notes from the mirror are held to their
      shape before they are shown. A camera-roll picture dated in the future no longer stops
      the photo sync until that date.
    • The mail relay (the web repository). One message can no longer carry a second inside it
      (the data ends on CRLF, dot, CRLF and nothing else), in either direction. A receiver
      cannot fill the relay's memory, stall everyone's outgoing mail, or write the text of the
      report the relay sends a box. Mail is delivered to public addresses only. The scripts
      that run as root no longer write by name into folders root does not own.
    • On the box. The model servers ask for a key: before, any account on the machine could
      ask the model and watch what it was working on. The update tools, which run as root on
      the unlocked volume, no longer follow a link there (two of their lines would have given a
      taken-over daemon root). ffmpeg and dwebp get the same size limits as the box's own
      decoders, a deadline, and a bounded reply; a WebP's size is read before it is decoded; a
      clip built as millions of empty boxes is put down at once; a photo dated in the year 9999
      is filed by the phone's date.
  • Memories are kept the way the posts say they should be ("How memory gets made"), four steps
    closer. docs/MEMORY.md is the whole model, with what is built and what is not.
    • Anchors. On a memory's page, [ ◆ mark as an anchor ] marks it as one of the few your
      life hangs on. Only you can: the box counts what goes together, it does not decide what
      mattered, and no pass sets, lifts, deletes or folds away an anchor. Anchors come first in
      MEMORIES, have a chip of their own, and lead what every chat starts from.
    • The company a memory keeps. A memory's page lists what the box holds with it and why:
      the people it names, the place it was at, the day it was written on, the trip or the
      month it is part of. Each is a tap away. The links are drawn from the memories with no
      model, so each is something the box can point at. A deleted memory leaves every
      neighbourhood at once.
    • Months. A month that ended six weeks ago becomes one memory, counted from its days (how
      many, the photos, the places, the trips, the walking, the notes), with its days and
      outings under it the way a trip holds its days. Nothing is deleted: the days are one tap
      down and what they were told from is where it was. Recent weeks stay day by day.
    • The front page. Every chat used to start from the first 1,200 characters of the note
      about you, whatever the note went on to say. It starts now from a page chosen once a day:
      the note's opening, your anchors, and the few memories that weigh the most (the ones in
      company, lately made or lately looked at). The memories on it say so.
    • A question brings better memories. Of two that match equally the heavier goes first, not
      the newer, and the best match brings a neighbour the question did not name: ask about a
      person and the trip they were on can come with them.
    • Fixed: a question that matched nothing in the archive showed three "memories" under the
      answer with invented dates ("photo caption placeholder"). They were test scaffolding from
      the first weeks and are gone. Nothing found is nothing shown.
    • Fixed: a day told again (a late caption, a late sync) lost its place under its trip until
      the next folding and showed on its own in the feed.
    • Fixed: an outing under an old trip could open as "this memory is not on the box any
      more". The page looked for its memory in the feed, which stops at six hundred rows with
      the parts last; it asks the box for the memory by name now.

Known gaps at 0.0.8

  • Carried from 0.0.7: the box CA key on the OS disk by choice; releases signed by the site key
    alone; the APK not byte-reproducible; the Mist and the decoy volume not built; mail from a home
    connection filed in Spam by the large receivers until the sending IP has a reverse name; the box's
    forecast with no verification yet (nothing scores yesterday's forecast against what happened,
    so the blend's weights are set by hand); the mirror's daemon specified and not built.
  • From the first audit's leads, still open: the calendar and contacts device label comes from
    the upload, not the certificate. (The share handler, the picker guard and the unseen web
    queries are closed in this cut.)
  • From the 12 November pass, left as they are: the update tools still download by name into
    the unlocked volume as root (a daemon that had been taken over could aim an update's bytes
    at another file: destruction, not control; the lasting fix is to do that work as the
    volume's owner, and it needs the box to test); the relay's outgoing mail has no MTA-STS or
    DANE (a receiver's certificate that does not verify is still delivered to, encrypted); the
    daemons' health ports tell any local account their counts; a voice note waits on the phone
    as plain audio until the box has it.
  • The memory model, against the posts (docs/MEMORY.md has the list): memories are matched
    by word, not by meaning, so two things alike in meaning that share no word are not linked
    and not found together; there is no queue of questions with yes, no and don't ask again;
    ghost.cued's context priming has nothing to prime against, so what comes unasked is a day a
    year ago and something nearby; there are no years above the months; a memory's kind cannot
    be changed from the phone. A person's memory keeps what you said of them as facts and the
    model writes them up, which is more than the "pointer" the overhears post describes.
  • From the second audit, open by choice or waiting on a decision: the box still reads linked articles and coin
    sites itself while SETTINGS says only the phone fetches on Wi-Fi; other people's text that
    reaches a chat answer can be distilled into a memory; a shared text that starts "Daily
    check-in " is filed as that day's check-in (it is now shown and asked about first);
    deleting a day's memory on MEMORIES does not stop the DAY page telling it; a backup proves
    secrecy and wholeness, not who wrote it; incrementals do not replay deletions; mail has no
    disk ceiling; the short install check cannot verify the bundle it downloads, the mirror
    script accepts an expired or revoked site-key signature, and the site key signs everything
    from the web host's keyring.