thsmi / sieve

Sieve Script Editor
GNU Affero General Public License v3.0
729 stars 56 forks source link

Can't seem to get a self-signed cert fingerprint to be recognized #892

Closed ohmantics closed 6 months ago

ohmantics commented 1 year ago

Prerequisites

What happened?

Using the Electron app, built locally, I pasted the SHA256 fingerprint of my self-signed server cert into the proper field in the Settings. (Not entirely clear how the fingerprint should be formatted. Does it have colons between bytes or not, etc.?)

I always get a verification error during STARTTLS.

Based on logging I did, options.ignoreCertErrors isn't being set anywhere, so we always raise an exception and bail out of the connection before upgrading completes.

What did you expect to happen?

I expected to be able to use the fingerprint feature to get around a self-signed cert not verifying.

Which Version

pavhofman commented 9 months ago

I am getting the same issue with the latest released version 0.6.1, on linux, self-signed certificate on the server, SHA1 fingerprint. The app does not get past the button CONTINUE on certificate warning screen, keeps repeating the screen.