mirror of
https://github.com/torlando-tech/pyxis.git
synced 2026-10-22 05:52:25 +00:00
torlando-tech
40e561f444
Was: attermann/microReticulum @ tag 0.3.0 (vanilla)
Now: torlando-tech/microReticulum @ pyxis-fixes-on-0.3.0 @ 97e72a3
= vanilla 0.3.0 + 3 focused upstream-PR-ready commits
The branch carries our spec-conformance fixes that vanilla upstream
0.3.0 is missing:
bb177e4 Fix PKCS7 padding to be spec-conformant (RFC 5652 §6.3)
918f743 Fix HMAC convenience digest() helper hashing the message twice
97e72a3 Apply RFC 7748 §5 scalar clamping in X25519PrivateKey constructor
Each is one self-contained commit with a unit test that catches the
bug — designed so they can be cherry-picked or PR'd to attermann
upstream individually after we've finished e2e testing pyxis on top.
The conformance bridge baseline against vanilla 0.3.0 was 50/85;
expectation post-this-pin is to recover to 52/85 (the X25519 clamping
unblocks both x25519_generate and identity_from_private_key).
Pyxis
An LXMF and LXST client firmware for T-Deck, built on a highly modified fork of microReticulum
Very much WIP, don't expect stability :)
Features
Reticulum transport over:
- RNode-compatible LoRa
- AutoInterface (local wifi)
- TCP Client
- BLE Interface (barely working if at all)
Other features:
- GPS-synced time
- One really annoying beep when you get a new message (user toggle)
- View the announce stream
- Choose a propagation node (and sync with it) (fixed in v0.2.1)
- Set auto announce timer
- Light up keyboard (user toggle)
Will crash in about 5 minutes of normal use (sorry)I had 5d uptime on v0.2.0 with BLE disabled- Make LXST voice calls (codec2 only, quality sounds horrible coming out the other end in Columba, needs work)
Why "Pyxis"
Pyxis, latin for "compass," is a constellation in the southern sky depicting a mariner's compass. Small but essential, the compass ensures every message finds its destination - even when the path is uncertain.