Electron apps can't use the Channel Session Protocol due to AES-KW being disabled in BoringSSL

[gnarea]

Electron doesn't support AES-KW because BoringSSL doesn't enable it. This causes courier sync to break in the desktop gateway, and will make it impossible to write Awala-compatible apps powered by Electron.

If we can't get this fixed in Electron or BoringSSL, we'll need to implement one of the following workarounds -- sorted from least to most awful:

1. Patch webcrypto to use a pure JS implementation of AES-KW: Can't use AES-WRAP in Electron apps PeculiarVentures/webcrypto#40
2. Create a new package to extend webcrypto to use a pure JS implementation of AES-KW.
3. Create a fork of Electron where BoringSSL is patched to enable the cipher. We'd have to maintain it indefinitely.
4. Ditch Electron in the desktop gateway and officially accept that Awala-compatible apps can't be powered by Electron.
5. Disable the channel session protocol when AES-KW isn't available.

[github-actions]

🎉 This issue has been resolved in version 1.55.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀