-
DinoX v2.3.1
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 1m11sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 51m53sBuild / Build AppImage (push) Successful in 1h55m57sBuild / Build Flatpak (push) Successful in 47m38sreleased this
2026-10-05 03:15:45 +02:00 | 348 commits to master since this releaseDinoX v2.3.1
Modern XMPP client with extended features.
What's New
Highlights
- Updated desktop call engine: Google/libwebrtc M152 brings refreshed Linux and Windows runtimes, hardware-assisted video where available, independent software fallbacks, and fixes to direct-call and private-room MUJI negotiation.
- Safer profile maintenance: Backups, restores, password changes, history resets, and profile deletion now coordinate database snapshots, exclusive profile ownership, and recoverable maintenance transactions.
- Clearer contact permissions: Contact dialogs and conversation details show the actual presence subscription state, offer explicit request and grant actions, and report failures without inventing mutual permissions.
Added
- Desktop hardware video codecs: H.264 can use VA-API/NVENC encoding and VA-API/NVDEC decoding on supported Linux systems, and Media Foundation on supported Windows systems. Encoding and decoding choose hardware independently and fall back to software when initialization or processing fails. Linux VP8 reception can use VA-API when the driver exposes the required decoding profile; VP8 encoding remains on the CPU. VP8 stays the initial preference, with VP9 and H.264 selected from shared peer capabilities.
- Visible OMEMO key-access failures: Direct messages waiting for a contact's encryption keys now report denied server access. Subscription requests, grants, and contact actions stay bound to the selected account, with live permission state and retryable failures. The affected controls and error messages include updated German translations.
Changed
- Private-room group calls: MUJI preparation follows reflected room presence, correlates preparation generations, and freezes conference content names, payload IDs, packetization times, codec dependencies, and feedback before READY presence and native media commitment. Explicit BUNDLE mapping is negotiated with peers that support it. New locally created conference capabilities omit optional RRTR; existing READY maps and adopted calls retain their negotiated parameters.
- Direct-call negotiation: Jingle answers and ICE candidates retain the original offer's content order and identities. Description-level and payload-level RTCP feedback, wildcard feedback, and reporting intervals survive SDP conversion, while an answer can omit optional feedback. Direct 1:1 RRTR remains optional.
- Consistent encrypted backups: Backup snapshots wait for admitted message processing to finish and include the related plugin databases. Archive progress follows the messages actually admitted to that snapshot, reducing mismatches between stored messages and restored history state.
- Recoverable offline profile operations: Restore, password changes, history reset, and profile deletion are applied before normal databases and plugins start, under an exclusive profile lock. Interrupted operations retain owned staging and rollback state; maintenance preserves the attachment encryption key and is serialized with account removal and shutdown.
- Release packaging: Linux and Windows packages use pinned M152 runtimes and optimized release defaults. Runtime checks cover codec dependencies, worker lookup, provenance, and package contents. Debian packaging avoids a second application compilation, Flatpak source copies exclude local build outputs, and AppImage verification has a budget for the complete package checks.
- Regression coverage: Expanded tests cover multi-account OMEMO state, profile locking and crash recovery, SQLCipher backup and password changes, MUJI preparation and native mappings, scoped RTCP feedback, contact permissions, Unicode rendering and backups, and Windows fixture cleanup and binding types.
Fixed
- Failed profile password checks on Windows: Offline maintenance closes the database handle when opening or validating an encrypted database fails, allowing Windows to release the file for cleanup and retry.
- Legacy OMEMO startup and recovery: New device registration checks the account's published device list and bundle identity before publication. Bundle discovery no longer creates encryption sessions prematurely; sessions are prepared when sending messages or encrypted Jingle transfers. A bounded trusted-device key transport can recover a missing prekey, while archived receive state and session persistence remain transactional.
- Incoming and queued OMEMO messages: Direct chats can display authenticated decrypted messages even when the outgoing mode is plaintext. Device-list changes revalidate queued sends through normal encryption, and failed direct-message key queries produce a retryable local error. Account isolation, trust choices, and the selected encryption mode are preserved; OMEMO 2 remains disabled in production.
- Groupchat archive collisions and replies: Messages with conflicting personal-archive IDs no longer suppress distinct room messages. Groupchat references and replies use the room-authorized stanza identity, and ambiguous targets are rejected.
- Call setup and teardown: Early remote ICE candidates are buffered until the session can accept them. Closed native sessions are destroyed outside callback locks, failed MUJI peer sessions are retired, and removed participant widgets are cleared. Native MUJI answers reject RTX payloads whose primary codec is absent.
- Unicode text and optional previews: Link parsing, formatting, quotes, and highlighting operate on the original UTF-8 text instead of offsets from a lowercased copy. Optional data-URI thumbnails preserve their metadata, and unsupported previews retain normal file and download controls.
- Windows backup paths and runtime caches: A bundled native archive helper handles backup and restore filenames containing spaces or non-ASCII characters. Certificate bundles and GStreamer registries use the runtime cache directory, keeping startup cache work away from the profile before its lock and restore checks.
- Tor bridge startup: Bundled Lyrebird and obfs4 transports launch correctly from directories containing spaces or Unicode characters. Tor receives a supported executable argument and the corresponding working directory on Linux and Windows.
- GTK focus and XMPP stream ownership: Text-widget focus is cleared at the appropriate lifecycle boundary, and stream modules track attachment ownership so a reused module cannot leave handlers bound to the wrong stream.
- XMPP error handling: Diagnostic text no longer masks the actual stanza error condition, regardless of XML child order. Native OMEMO failures retain their underlying Signal error details for diagnosis.
Security
- Packaged Tor update: Update Tor from 0.4.9.8 to 0.4.9.12. Linux and Flatpak source pins, Windows package verification, and runtime inventories use the verified artifacts; the Windows package and its upstream signature are mirrored in Forgejo
vendor-deps. - Encrypted profile protection: An existing OMEMO database with a missing key fails explicitly rather than receiving a replacement key. Account-related message state stays on its actual pipeline object, and payload-less legacy key transports cannot expose an unauthenticated outer message body.
- Data-preserving cache cleanup: Cache clearing keeps durable account data and active media intact. Profile deletion retains its pending request across shutdown, and restore and maintenance reject unsafe ownership and filesystem paths.
- Automatic API certificates: Certificate renewal and removal recheck the current API mode and custom certificate settings when activated, preventing stale controls from changing manually configured certificates.
- Private-room call invitations: Direct MUJI invitations for an already joined room require a current participant with the matching disclosed full JID and an active private-room lifecycle. Reconnects and occupant changes invalidate stale acceptance work.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.1_amd64.deb.sha256 sudo apt install ./dinox_2.3.1_amd64.debAppImage
sha256sum -c DinoX-2.3.1-x86_64.AppImage.sha256 chmod +x DinoX-2.3.1-x86_64.AppImage ./DinoX-2.3.1-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.1-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.1-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.1.tar.gz.sha256 tar xf dinox-2.3.1.tar.gz cd dinox-2.3.1 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/build/release-deps/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
23 downloads
-
Source code (TAR.GZ)
9 downloads