You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Answered all the questions in this template (Or provide a working crystal ball).
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
sieve dfeeac1 + local patches to debug via console logging in the Electron app
macOS 12.6.4
dovecot 2.3.20_1 in a FreeBSD 13.1 jail
The text was updated successfully, but these errors were encountered:
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.
- Add facilities for using custom CA, client certificate and private key
- Use SNI if using custom client certificate and private key
- Fix broken `ignoreCertErrors()`
- Change behaviour of "Forget Password" button ...
- The button becomes disabled after a click event rather than
disappearing
- The button clears both auth password and TLS private key passphrase
- Pressing 'Ctrl + Shift + I' or 'F12' combo launches dev tool
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
The text was updated successfully, but these errors were encountered: