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.

Sign up for GitHub

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

Jump to bottom

tls-no-verify option for feeds #3

Closed
Necoro opened this issue Apr 19, 2020 · 0 comments
Closed

tls-no-verify option for feeds #3

Necoro opened this issue Apr 19, 2020 · 0 comments
Assignees
@Necoro
Labels
compatibility Unwanted behavior change to feed2imap enhancement New feature or request
Milestone
First usable release

Comments

@Necoro
Copy link
Owner

Necoro commented Apr 19, 2020 •
edited

Some feeds can return invalid certificates when talked to via HTTPS (wrong servername, self signed, missing cert chain). feed2imap used to circumvent this by always setting tls no verify -- but now we want this to be done only on a per feed basis (plus the possible global option).

Until this is implemented, feeds with broken HTTPS are inaccessible
@Necoro Necoro added enhancement New feature or request compatibility Unwanted behavior change to feed2imap labels Apr 19, 2020
@Necoro Necoro self-assigned this Apr 19, 2020
@Necoro Necoro mentioned this issue Apr 26, 2020
Closed
12 tasks
@Necoro Necoro added this to the First usable release milestone Apr 26, 2020
@Necoro Necoro closed this as completed in c2b5808 Apr 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Necoro Necoro

Labels
compatibility Unwanted behavior change to feed2imap enhancement New feature or request
Projects
None yet
Milestone
First usable release
Development

No branches or pull requests
1 participant
@Necoro