Skip to main content

LANMess

End-to-end encrypted messenger with a terminal UI. Discovers peers on the local LAN, or add them by IP and port to use any network you can route to.

Install

pip install lanmess

Run

lanmess

First launch

  1. Display name.
  2. Group code (min 12 chars, shared with your peers).
  3. PIN (min 12 chars, mixed character classes). Unlocks your local database.

You type the group code once. From now on you unlock with your PIN.

Adding contacts

Two ways:

  • By code (A or the add-code input): the peer must be on the same broadcast domain. LANMess discovers them via a UDP beacon, then performs the signed add handshake.
  • By IP (I or /addip): you provide the peer's IP, port, and current add code. No discovery is used. Works on any routable network, including overlay networks and VPNs.

To find your own addresses, use Show my address in the menu (Session section) or /address. Every IPv4 on the machine is listed with the TCP port peers should connect to.

UI overview

  • Sidebar: contacts with unread badges (3), verified markers *, and state tags [active], [chat req], [BLOCKED].
  • Chat pane: conversation, [UNVERIFIED] warning if applicable, status line, message input.
  • M opens a sectioned menu (Chat / History / Session / System).
  • Ctrl+Z opens a modal with your current add code and countdown.
  • ? opens help. Ctrl+L locks. Ctrl+Q quits.
  • I opens the add-by-IP dialog.

Security model (v1.1.8)

  • Per-session X25519 handshake with fresh ephemerals both sides.
  • Symmetric hash ratchet per message (forward secrecy within a session).
  • Ed25519 signatures on every control frame and every message.
  • Length-padded messages (256-byte blocks).
  • Safety numbers for out-of-band verification (V or /verify).
  • Data at rest sealed by a random per-device master wrapped with Argon2id(PIN).
  • HMAC-chained audit log for sensitive events.
  • Frame size caps, connection semaphore, per-IP rate limits.

Migrating

From v1.1.3 through v1.1.6: enter your PIN. Everything re-encrypts under a fresh random master if needed and the audit log is created. Nothing lost.

From v1.1.2: enter your old group code once plus a new PIN.

See THREAT_MODEL.md for what is and isn't defended.

Metadata

Release files for lanmess 1.1.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lanmess 1.1.8
File Size Uploaded Provenance Actions
lanmess-1.1.8.tar.gz 41.9 kB With provenance Details for lanmess-1.1.8.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lanmess 1.1.8
File Interpreter ABI Platform Actions
lanmess-1.1.8-py3-none-any.whl Python 3 none any Details for lanmess-1.1.8-py3-none-any.whl

Total release size: 75.2 kB

Release files / lanmess-1.1.8.tar.gz

Download URL lanmess-1.1.8.tar.gz
Size 41.9 kB
Tags Source
SHA-256 checksum
How to use checksums
2426c1a079a25ee5b756a2b144d058e74101263deb1a6a1b5b5db269b4de1b6d
BLAKE2b-256 checksum
How to use checksums
52da29f0a948e10129f28c0d2d45df10915bf2bafcb75b6a9d3ee4329b336a6e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

Release files / lanmess-1.1.8-py3-none-any.whl

Download URL lanmess-1.1.8-py3-none-any.whl
Size 33.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d38e43c912bdb21a96908fcbcae1f4764c1bf5df8ccc9559f3e8ec6073c3fee
BLAKE2b-256 checksum
How to use checksums
16dfe3b213ca32beb3bacf74cc626df0e27bd3aa926662dd13351c23fa32bbc7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

Security for lanmess 1.1.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for lanmess-1.1.8.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page