Version 0.13.0

v0.13.0 focuses on HaveClip’s original purpose - clipboard synchronization - and security. All other unrelated features were removed, including:

The idea is that the user should be able to run a different feature-rich clipboard manager alongside HaveClip, which takes care only of the synchronization from now on.

The encryption mechanism was made more accessible by internally generating self-signed certificates (except for Sailfish version). The certificates now give peers identity.

v0.13.0 also introduces a new pairing mechanism. In order to ensure that the clipboard is sent and received to/from trusted devices, the peers remember each other’s identity. The peer’s identity is established during the pairing process (called verification), in which the user must enter the security code shown on one device to the other, thus verifying their identities.

The clipboard synchronization is now successful only if both communicating peers have valid identities. No data is leaked if the identity is not correct.

The unencrypted mode still works, but is strongly discouraged, as anyone can set/read your clipboard.

Another useful feature is limiting the size of the clipboard which the device will accept or send. This might save some unwanted traffic and resources when something big gets into the clipboard.

Similar to that, it is possible to filter what MIME types will be sent or received. This is used on Jolla in default configuration, which will now send and accept only text/*. Nothing else will get there.

v0.13.0 also supports on-demand clipboard synchronization. Clipboard sending can be disabled in settings and you can sync the clipboard only when you want to, not always.