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).
Was: torlando-tech/microReticulum @ feat/t-deck @ ca355e5 (a torlando
fork with unrelated git history per pyxis_microReticulum_alignment_analysis).
Now: attermann/microReticulum @ tag 0.3.0 @ f8d91d1 (canonical upstream).
This commit is configuration-only — just the submodule pointer + URL.
Pyxis will not build yet because vanilla upstream doesn't ship the
fork's added subtrees (src/LXMF, src/BLE, src/Hardware/TDeck, src/UI,
src/Instrumentation, PSRAMAllocator/BytesPool/ObjectPool/FileStream/
FileSystem, Cryptography/{BZ2,Ratchet}, Utilities/Print,
SegmentAccumulator). Subsequent commits in this branch vendor those
into pyxis itself or carve them out into standalone libraries per
the alignment plan.
Split T-Deck firmware from microReticulum examples/lxmf_tdeck/ into its
own repo. microReticulum is consumed as a git submodule dependency pinned
to feat/t-deck. All include paths updated from relative symlinks to bare
includes resolved via library build flags.
Both tdeck (NimBLE) and tdeck-bluedroid environments compile successfully.
Licensed under AGPLv3.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
torlando-tech