doc/release_notes/index.md
3.0.3 ( 2025-06-13 )=====================================================================
io.github.input_leap.input-leap to resolve to Github repository correctly.3.0.2 ( 2024-10-12 )Please open a Github issue you're still using these versions and can't upgrade. Depending on popular demand removal of old OS support may be reverted.
3.0.1 ( 2024-10-10 )3.0.0 ( 2024-10-04 )Added Wayland support. Note that XWayland won't work properly and warning is printed.
Create an uninstall target for Makefiles
This allows for developers (or users who are testing) to remove Input Leap from
their system, based on $PREFIX.
Added a new clipboard sharing size limiter to prevent transferring clipboards past a default value in bytes.
Allow Qt version to be selected via CMake
CMake now uses a sane default of Qt 5, but allows for a CMake option of
QT_DEFAULT_MAJOR_VERSION, for overriding of the Qt library used during build.
For example, setting QT_DEFAULT_MAJOR_VERSION to 6 uses Qt 6, and setting to
5 uses Qt 5. Older versions are not supported.
Added new converters for X11 to support copy pasting png/tiff/jpg/webp formats.
Added support for building against Qt 6 in addition to Qt 5.
debian folder which previously clashed
with data provided by the Debian packaging.input-leap.conf.example-advanced to accurately include the advanced configuration described in/intended by the comment within it.2.4.0 ( 2021-11-01 )Barrier now supports client identity verification (fixes CVE-2021-42072, CVE-2021-42073).
Previously a malicious client could connect to Barrier server without any authentication and send application-level messages. This made the attack surface of Barrier significantly larger. Additionally, in case the malicious client got possession of a valid screen name by brute forcing or other means it could modify the clipboard contents of the server.
To support seamless upgrades from older versions of Barrier this is currently disabled by default. The feature can be enabled in the settings dialog. If enabled, older clients of Barrier will be rejected.
Barrier now uses SHA256 fingerprints for establishing security of encrypted SSL connections. After upgrading client to new version the existing server fingerprint will need to be approved again. Client and server will show both SHA1 and SHA256 server fingerprints to allow interoperability with older versions of Barrier.
All of the above security issues have been reported by Matthias Gerstner who was really helpful resolving them.
--drop-target option that improves drag and drop support on Windows when Barrier is
being run as a portable app.--enable-crypto command line option has been made the default to reduce chances of
accidental security mishaps when configuring Barrier from command line.
A new --disable-crypto command line option has been added to explicitly disable encryption.--profile-dir option that allows to select custom profile directory.2.3.4 ( 2021-11-01 )Barrier will now correctly close connections when the app-level handshake fails (fixes CVE-2021-42075).
Previously repeated failing connections would leak file descriptors leading to Barrier being unable to receive new connections from clients.
Barrier will now enforce a maximum length of input messages (fixes CVE-2021-42076).
Previously it was possible for a malicious client or server to send excessive length messages leading to denial of service by resource exhaustion.
Fixed a bug which caused Barrier to crash when disconnecting a TCP session just after sending Hello message (fixes CVE-2021-42074). This bug allowed an unauthenticated attacker to crash Barrier with only network access.
All of the above security issues have been reported by Matthias Gerstner who was really helpful resolving them.