Page MenuHomePhabricator

Use olm WASM with content hash on web in production
ClosedPublic

Authored by marcin on Nov 27 2023, 2:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 12, 3:43 PM
Unknown Object (File)
Sat, Nov 9, 7:10 PM
Unknown Object (File)
Sat, Nov 9, 2:57 PM
Unknown Object (File)
Wed, Oct 30, 1:21 PM
Unknown Object (File)
Oct 2 2024, 4:38 AM
Unknown Object (File)
Oct 2 2024, 4:38 AM
Unknown Object (File)
Oct 2 2024, 4:38 AM
Unknown Object (File)
Oct 2 2024, 4:38 AM
Subscribers

Details

Summary

This differential fixes an urgent Linear issue: https://linear.app/comm/issue/ENG-5895/web-notification-decryption-error. Production web builds will use
olmFilename variable with content hash provided by the keyserver. Development builds will use default olm.wasm filename.

Test Plan
  1. Clear all cache files for localhost:3000/comm. This step is necessary since production builds might have used olm WASM from cache populated by dev builds.
  2. Builds production web app.
  3. Ensure that notifications are encrypted (MariaDB console) and correctly decrypted on the keyserver.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable