Note: As of HaveClip v0.14.0, certificate generator is a part of HaveClip and works out-of-the-box.
HaveClip for Sailfish v0.13 and below cannot generate the needed certificate on its own. The private key and certificate must be generated elsewhere and copied to Jolla.
There are several ways to generate a self-signed certificate, these two are described here:
- Using HaveClip
- With OpenSSL CLI
Generating certificate with HaveClip
Generate certificate (in Settings -> Security), locate the files and copy them to Jolla.
Be careful not to overwrite your own certificate though, as you would have to pair all your devices again.
You could first change the paths, generate certificate and change the path back again. Then copy the newly generated certificate to Jolla.
Generating certificate with OpenSSL
This command will generate a self-signed certificate valid for 10 years.
$ openssl req -x509 -newkey rsa:2048 -keyout haveclip.key -out haveclip.crt -days 3650 -nodes
Copy the private key and certificate to Jolla
Once you have the private key and certificate, you have to copy them to Jolla. You can do this over SSH if you have developer mode, via USB cable or some application for this purpose.
By default, the key and certificate on Jolla are stored in /home/nemo/.local/share/harbour-haveclip/harbour-haveclip/.
You can of course change this if you have trouble finding it (Settings -> Security).
If you don’t change the file names or paths, you should have haveclip.crt and haveclip.key
in /home/nemo/.local/share/harbour-haveclip/harbour-haveclip/.
Restart HaveClip and check that the certificate is loaded. If so, you can proceed with device pairing.