mirror of
https://github.com/slurdge/goeland.git
synced 2026-11-11 21:02:30 +00:00
[GH-ISSUE #98] Option to accept self-signed SSL certificate or expired SSL certificate (in HTTPS) #23
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: slurdge/goeland#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @djm1 on GitHub (Dec 12, 2022).
Original GitHub issue: https://github.com/slurdge/goeland/issues/98
Hello,
would it be possible (or is it already possible?) to add an option to configuration file to accept self-signed SSL certificates (certificate signed by unknown authority) and expired SSL certificates in HTTPS connections?
I'm aware about the security risk, but sometimes it is difficult to get the SSL certificate corrected / updated.
Thank you
@slurdge commented on GitHub (Dec 12, 2022):
Yes, you can use
email.allow-insecurein config, as such:@djm1 commented on GitHub (Dec 12, 2022):
Hello,Thank you for your quick reply.If I'm not mistaken, provided option is covering only SMTP server's SSL certificate. Would it be possible to create similar option for object "source"? - in example specific HTTPS side do not have trusted or have expired HTTPS certificate.Thank you--S pozdravomMiroslav @.***
-------- Original message --------From: slurdge @.> Date: 12/12/22 15:21 (GMT+01:00) To: slurdge/goeland @.> Cc: djm1 @.>, Author @.> Subject: Re: [slurdge/goeland] Option to accept self-signed SSL certificate or
expired SSL certificate (in HTTPS) (Issue #98)
Yes, you can use email.allow-insecure in config, as such:
[email]
allow-insecure = true
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@slurdge commented on GitHub (Dec 12, 2022):
Sorry I misunderstood. I'll have to look at the library used to retrieve feeds
@djm1 commented on GitHub (Dec 13, 2022):
Thank you, I will wait for your review and feedback :-)--S pozdravomMiroslav @.***
-------- Original message --------From: slurdge @.> Date: 12/12/22 22:47 (GMT+01:00) To: slurdge/goeland @.> Cc: djm1 @.>, Author @.> Subject: Re: [slurdge/goeland] Option to accept self-signed SSL certificate or
expired SSL certificate (in HTTPS) (Issue #98)
Sorry I misunderstood. I'll have to look at the library used to retrieve feeds
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@djm1 commented on GitHub (Jan 10, 2023):
Hello,
did you have a time to look on this topic, please?
Thank you
On Tue, Dec 13, 2022 at 12:10 PM Miroslav Vrabel @.***> wrote:
--
S pozdravom
Miroslav Vrabel
@.***
@slurdge commented on GitHub (Jan 10, 2023):
Hello @djm1 , yes, I did look into it.
I also have a beginning of a solution however I don't like it much, that's why I am thinking a bit more about it. Sorry
@djm1 commented on GitHub (Jan 10, 2023):
Hello,
no problem, thank you for the update. The situation from my side is that
not all website owners are refreshing the SSL certificates, or not all
website owners are using the SSL certificates signed by trusted authority.
I think it is not possible to cover all website owners to get the SSL
certificates configured properly so I'm searching for alternative solution
Thank you
On Tue, Jan 10, 2023 at 3:10 PM slurdge @.***> wrote:
--
S pozdravom
Miroslav Vrabel
@.***
@slurdge commented on GitHub (Jan 18, 2023):
This will be available in the next release, with an option for each source.
@slurdge commented on GitHub (Jan 18, 2023):
Please check 0.13.0
@djm1 commented on GitHub (Jan 18, 2023):
Great, thank you for adding this feature. I will test it in new release.
On Wed, Jan 18, 2023 at 3:25 PM slurdge @.***> wrote:
--
S pozdravom
Miroslav Vrabel
@.***