Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import missing host.ignoreCertErrors #778

Open
3 tasks done
EntropyWorks opened this issue Jul 15, 2022 · 8 comments
Open
3 tasks done

Import missing host.ignoreCertErrors #778

EntropyWorks opened this issue Jul 15, 2022 · 8 comments
Labels
App Issue affects the standalone application bug

Comments

@EntropyWorks
Copy link

Prerequisites

  • Tried the most recent nightly build
  • Checked if your issue is already reported.
  • Answered all the questions in this template (Or provide a working crystal ball).

What happened?

I'm using the nightly build for MacOS. I had exported the config from a working nightly build on another MacOS machine. When importing the config into the new laptop it appears to connect but just sits there connecting.

  1. Working Sieve.app export configuation
  2. New laptop download new version of Sieve.app from nightly build.
  3. Import old config
  4. Fails to work
  5. Delete config
  6. Manually enter settings from the exported json file.
  7. Make sure to have Fingerprint set
  8. Fails to connect
  9. Open up Developer Tools
  10. Application -> Storage -> Local Storage -> file://
  11. @krmi707c-8yx53fzo6j.host.ignoreCertErrors = UNABLE_TO_VERIFY_LEAF_SIGNATURE
  12. That seems to have fixed it!!!

What did you expect to happen?

I expected the import to work and prompt me for a password. Adding KEY=@krmi707c-8yx53fzo6j.host.ignoreCertErrors VALUE=UNABLE_TO_VERIFY_LEAF_SIGNATURE by hand fixed things.

Screenshots

Screen Shot 2022-07-14 at 7 22 47 PM

Screen Shot 2022-07-14 at 7 16 30 PM

Which Version

  • Standalone app
  • MacOS nightly build
  • Postfix Dovecot
@thsmi thsmi added the App Issue affects the standalone application label Jul 22, 2022
@stale
Copy link

stale bot commented Aug 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 12, 2022
@thsmi thsmi removed the stale label Aug 12, 2022
@stale
Copy link

stale bot commented Aug 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 31, 2022
@stale stale bot closed this as completed Sep 8, 2022
@thsmi thsmi reopened this Sep 10, 2022
@thsmi thsmi removed the stale label Sep 10, 2022
@k5123
Copy link

k5123 commented Sep 21, 2022

Confirmed reproduced on Windows. Can only get past the error message by adding UNABLE_TO_VERIFY_LEAF_SIGNATURE in the debugger > Application > Storage > file:// > ???.host.ignoreCertErrors. Application doesn't set this when the warning dialog is OK'd. Value stays at "undefined".

@stale
Copy link

stale bot commented Oct 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 8, 2022
@k5123
Copy link

k5123 commented Oct 11, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This bot is way too anxious.

@stale stale bot removed the stale label Oct 11, 2022
@stale
Copy link

stale bot commented Oct 28, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 28, 2022
@k5123
Copy link

k5123 commented Nov 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Or the issue isn't getting the attention it would need...?

@stale stale bot removed the stale label Nov 2, 2022
@thsmi thsmi added the bug label Nov 13, 2022
@anatoli26
Copy link

Same here. Spent hours on trying to modify LevelDB externally. Then found this issue and the "solution".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Issue affects the standalone application bug
Projects
None yet
Development

No branches or pull requests

4 participants