I literally spent 2 minutes searching github for “elixir lib lawyers obfuscation”. Then I realised “oh, actual human lawyers”.

There’s a simple, cross-platform, language-agnostic tool that’s perfect for this application: LAWYERS. If you’re worried about your clients stealing proprietary algorithms the way to guard against that is with contract language.

You can put up technical roadblocks, but ultimately you’re handing them the algorithms in a form that’s analyzable and reversible given sufficient time and money.

@mmmries is correct - The typical connection path is WSS with client-side and server-side SSL to establish that connection. On our production devices, we use the ATECCA508A/608A cryptographic chips for storing the device cert and key.

Firmwares are signed and the device has the public key to verify the file to prevent installing unknown firmware.

There is a decent amount to it so I’d recommend digging through the NervesHub documentation a bit for the gist if its of interest.

We’re also working towards root-filesystem encryption on our devices as a further step of protection when using Nerves (but this has a little bit to go)