Accept your server’s certificate
Gerfaut opensThis server signs its own certificate when you select Save backend and the server answers. Until you accept the certificate, syncs with that server fail. A .onion server skips this step.
When the server does not answer, Gerfaut saves the backend with
Saved. The server did not answer, so its certificate is unchecked. Gerfaut never asks about that certificate later. If the server signs its own, select Save backend again once it answers.1
Print the fingerprint on your server
On the machine that runs the server, run the command the dialog shows, with the path of the certificate file:
2
Compare it with the one Gerfaut shows
The two SHA-256 fingerprints must match, character for character.
3
Select Accept and save
Gerfaut records the fingerprint for that host and saves the backend.
- Android
- Desktop
Gerfaut shows the fingerprint and the command that prints it on your server, and saves nothing before Accept and save.
Decide when a certificate changes
When the host presents another certificate, syncs fail withthe server's certificate changed. Select Save backend in Settings > Network to open This server's certificate changed, with the fingerprints Accepted before and Presented now.
1
Check the new fingerprint with whoever runs the server
Select Cancel if you cannot. Gerfaut then saves nothing and trusts nothing.
2
Select Trust the new certificate
Then confirm.
- Android
- Desktop
Select Trust it anyway.
Forget a certificate
Once you forget a certificate, syncs with its server fail until you select Save backend again and accept the certificate.
1
Select Forget on the line of the server
In Settings > Network, the
Trusted certificates card lists each server whose certificate you accepted.2
Confirm
- Android
- Desktop
Select Forget certificate under the line.
Certificate forgotten and removes the line.