Releases: signalapp/libsignal
Releases · signalapp/libsignal
v0.84.0
v0.83.0
- backups: Support polls in backup validator - spqr: Remove client-provided options to turn on/off SPQR, defaulting to on everywhere.
v0.82.1
- keytrans: Unify errors with other typed APIs - Locally-closed WebSocket connections now explicitly send close code 1000 instead of an empty close frame - node: Buffer is explicitly imported from node:buffer
v0.82.0
- Node: migrate libsignal-client to the ECMAScript module format (from CommonJS). - Node: interfaces now use property notation for method requirements, which TypeScript can check more strictly. - net: Direct connections to the Signal servers will be tried as a fallback if connecting through an HTTP or SOCKS proxy fails or takes too long.
v0.81.1
- Enable negotiating permessage-deflate support for chat websocket connections, if configured. - Net: remove Noise connection shadowing for staging Chat websocket connections.
v0.81.0
- KyberPreKeyStore.markKyberPreKeyAsUsed now takes three arguments, to allow tracking how the pre-key is used: the Kyber pre-key ID, the signed EC pre-key ID, and the session base key. - We now always defer to an HTTP/HTTPS proxy for DNS resolution.
v0.80.3
- Internal changes and logging updates only
v0.80.2
- backups: Add logging to BackupAuthCredentialRequestContext_ReceiveResponse internals
v0.80.1
- Sealed sender SenderCertificates can now use a `bytes` representation for the sender, and may avoid embedding their signing ServerCertificate in favor of referencing a "known" certificate baked into libsignal. See sealed_sender.proto and the `KNOWN_SERVER_CERTIFICATES` list in the source for more details.
v0.80.0
- backups: relax restriction that backups with backup_tier == free cannot have backupsSubscriberData - Migrate crates to Rust 2024 edition. - Desktop: add a distinct error type for incremental mac verification failures.