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

fix: do not save "Automatic" into configured_imap_certificate_checks #5891

Merged
merged 1 commit into from
Aug 17, 2024

Conversation

link2xt
Copy link
Collaborator

@link2xt link2xt commented Aug 17, 2024

configured_imap_certificate_checks=0 means
accept invalid certificates unless provider database says otherwise or SOCKS5 is enabled.
It should not be saved into the database anymore.

This bug was introduced in
#5854 (commit 6b4532a)
and affects released core 1.142.4, 1.142.5 and 1.142.6.

Fix reverts faulty fix from
#5886 (commit a268946)
which changed the way configured_imap_certificate_checks=0 is interpreted and introduced problems
for existing setups with configured_imap_certificate_checks=0: #5889.

Existing test from previous fix is not reverted
and still applies.
Regression test is added to check that
configured_imap_certificate_checks
is not "0" for new accounts.

Fixes #5889

configured_imap_certificate_checks=0 means
accept invalid certificates unless provider database
says otherwise or SOCKS5 is enabled.
It should not be saved into the database anymore.

This bug was introduced in
<#5854>
(commit 6b4532a)
and affects released core 1.142.4, 1.142.5 and 1.142.6.

Fix reverts faulty fix from
<#5886>
(commit a268946)
which changed the way configured_imap_certificate_checks=0
is interpreted and introduced problems
for existing setups with configured_imap_certificate_checks=0:
<#5889>.

Existing test from previous fix is not reverted
and still applies.
Regression test is added to check that
configured_imap_certificate_checks
is not "0" for new accounts.
@link2xt
Copy link
Collaborator Author

link2xt commented Aug 17, 2024

Also added regression test in python.

@link2xt link2xt merged commit af4d54a into main Aug 17, 2024
37 checks passed
@link2xt link2xt deleted the link2xt/save-strict-tls branch August 17, 2024 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TLS failures with 1.142.6 core
2 participants