meshsat 0.9.1: Messaging, and the SMS default number

meshsat 0.9.1: Messaging, and the SMS default number

• Setup > Messaging, as MeshSat Android's three cards:

  • Encryption: the SMS link's AES-256-GCM key, which you can generate, save, show, copy, paste and save to a file. Encryption on or off, and automatic decryption of incoming texts, which keeps a text from an ordinary phone as it came. A key that cannot encrypt is refused before it is used.
  • Message compression: SMS and Iridium SBD, off or MSVQ-SC, with its stages. MSVQ-SC is offered only where the Bridge has its encoder, and this phone has none, which the page says.
  • Quick messages: the 30 brevity codes, as on Android. A code received from another MeshSat now reads as its words.

• Setup > SMS: "Where a text goes with no recipient", the number a routing rule's text goes to when it names none. Left empty, such a text is not sent.

• The Bridge underneath (MeshSat Bridge afe026af):

  • A link set to encrypt no longer sends a message in plain text when its key cannot encrypt. The message gives up with the reason (MESHSAT-1411).
  • A link's encryption and compression can now be set without touching the rest of the link, keys are checked when saved, and a gateway's stored secrets survive a save (MESHSAT-1412).

• Tested: 201 unit tests. On the bench phone, against the installed package, 81 cases green: 67 against a scripted Bridge, 8 against a second, real Bridge, 6 live. Among them:

  • every Messaging switch and button, checked as the exact change it makes to the Bridge's SMS link;
  • against the real Bridge: a key that cannot encrypt refused, a link's chains set without changing the rest of it, and an SMS gateway with no default number.

  The phone has no SIM, so no text has been encrypted or decrypted live.

Install on a Mobian phone: wget https://github.com/meshsat/meshsat-linux/releases/download/v0.9.1/meshsat_0.9.1_arm64.deb && sudo apt install ./meshsat_0.9.1_arm64.deb (docs/INSTALL.md).