causes problems under Windows if the certificate changes

[ClusterWood]

... causes problems under Windows if the certificate changes. Solution:

Delete '...\AppData\Roaming\sieve'

Install sieve-0.5.2. Add server again, certificate warnings can be skipped here. Login: “Force PLAIN”; when everything is running again, install version sieve 0.6.1. Runs somewhat more stable than 0.5.2, but cannot handle certificate changes.

Good luck

[thsmi]

This does not sound like a bug to me.

But as you completely ignored the issue template, did not provide much useful information and what you write does not really compute it is crystal ball time. From your writing it sounds to me, as if you are using self singed certificates and then pin the certificates fingerprint. Correct?

If so the program has to reject the connection, if you change the server's certificate does not match the pinned fingerprints. Everything else would be inherently unsafe. Because this is exactly what will happens in a man in the middle attack. Where someone impersonates your server.

In case you know you changed your cert's fingerprint for some reason and thus broke the chain of trust override., then open the app and go the the corresponding account's settings, open the "sever settings" and add your cert's fingerprint to the "Fingerprint" section.

Alternatively you can also remove the fingerprint and then it will ask you upon the next connect to verify the fingerprint and will add the fingerprint to the server's settings. But never blindly trust a cert without checking the fingerprint.

Anyhow the real fix would be rolling out your root ca to your clients pcs, so that you do not need to pin the certificate at all. Pinning certificates is a hack and not a solution for a productive environment. You should not use it unless your really really know what you are doing. In general the easiest is got to a trustworthy notary which has a CA root is already included in you system's ca store and request from them a certificate, which is normally way cheaper than manually rolling out a custom root CA.