Skip to content

Releases: signalapp/libsignal

v0.74.1

10 Jun 21:14
fd34ab3

Choose a tag to compare

-   backups: Add integrityCheck to LocatorInfo

v0.74.0

04 Jun 21:57
61827e1

Choose a tag to compare

- Integrate post-quantum ratchet in opt-in mode.

v0.73.3

03 Jun 23:37
7cce36e

Choose a tag to compare

- keytrans: Properly bridge and document errors

- keytrans: Add production configuration

- Internal improvements

- MSRV bumped to 1.83.0

v0.73.2

29 May 23:00
f8bcdb0

Choose a tag to compare

- Android: Fix bug which can cause CompletableFuture to be stripped by
  ProGuard/R8.

- keytrans: Bridge to ffi

v0.73.1

20 May 22:47
ad59d90

Choose a tag to compare

- Backups: the now-deprecated remote content locator fields are ignored and the new FilePointer.locator_info field must
  be set.

v0.73.0

20 May 20:46
1f92b82

Choose a tag to compare

- Support for starting sessions with pre-quantum X3DH has been removed from Swift, Java, and TypeScript. PQXDH will be required going forward.

- Bridge registration service client to Swift.

- Net/Java: Some CompletableFutures are now cancellable!

v0.72.1

15 May 01:01

Choose a tag to compare

- Fixes a regression introduced in v0.68.1 where incoming PreKey
  messages would fail to decrypt if the local device had archived the
  corresponding session. (This fix was also backported as v0.71.1.)

- Bridge registration service client to Swift.

v0.71.1

15 May 00:55

Choose a tag to compare

- Fixes a regression introduced in v0.68.1 where incoming PreKey
  messages would fail to decrypt if the local device had archived the
  corresponding session.

v0.72.0

14 May 15:26
ef5356b

Choose a tag to compare

- Swift: `sealedSenderEncrypt(message:for:from:sessionStore:identityStore:context:)` and `sealedSenderDecrypt(message:from:trustRoot:timestamp:sessionStore:identityStore:preKeyStore:signedPreKeyStore:context:)` have been removed. The former was a simple wrapper around `sealedSenderEncrypt(_:for:identityStore:context:)` for 1:1 messages that didn't expose all the features of UnidentifiedSenderMessageContent, and the latter was never updated to support PQXDH messages. The Signal iOS app does not use either function. If you were using `sealedSenderDecrypt`, switch to `UnidentifiedSenderMessageContent.init(message:identityStore:context:)`, and make sure to validate the resulting sender certificate and check for a self-send yourself before attempting to decrypt the inner message.

- The iOS minimum deployment target has been bumped to iOS 15.

- Unnecessary prefixes have been removed from file paths in log output.

- CDSI: fix handling of rate-limit-exceeded error to correctly parse the server-requested delay.

- Update incremental mac reading to support streaming videos.

v0.71.0

01 May 21:37
eac4cf5

Choose a tag to compare

- A pre-key message sender's identity is stored after the message is decrypted.

- Java, Node, Swift: changed IdentityKeyStore.saveIdentity to return an enum.

- Java: Expose account registration via the registration service client.

- Node: RegistrationService.registerAccount takes account password as a string.

- net

  - Connections to Signal services (and to Cloudflare's DNS-over-HTTPS server) will now require TLS v1.3, which they would already have been using.

  - Futures returned by ChatConnection.send() will now return more specific errors on failure.

- New SVR2 enclaves for staging and production.

- keytrans

  - Bridge to Node.

  - Support multiple auditors.