SSL Errors

Anyone else seeing this?

Screen Shot 2020-09-05 at 09.32.22.png

Multiple feeds with the same error, it appears they all hosted on AWS.

Gertjan

Noop.
What is the URL used ?
http - see the error - or https download ?

This is a typical server side message. The admin of the feed should review its cert settings.
You can't do anything, just wait it out.

These:

https://raw.githubusercontent.com/heradhis/indonesianadblockrules/master/subscriptions/abpindo.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
http://theantisocialengineer.com/AntiSocial_Blacklist_Community_V1.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_malware.txt

From a shell just to confirm:

curl https://raw.githubusercontent.com/heradhis/indonesianadblockrules/master/subscriptions/abpindo.txt
curl: (60) SSL certificate problem: self signed certificate

Not too concerned, all self signed certs. Maybe they (whoever maintains those feeds) get it together or they don't. We'll see.

johnpoz

You got something else going on - or they have been fixed in the last few minutes. But none of those links show self signed, and they have been valid for awhile

example

via curl

You going through some proxy would be my guess. Trying to do mitm

Thank you John! I added some additional feeds last evening. I removed them and all is well. Not sure how that would have created a cert problem. Someone more knowledgable than I will immediately understand, I'm sure.

Today is going to be hectic once the kids are up, but I will go back and isolate the problem feed and report back.

johnpoz

I don't see how adding a feed would have anything to do with other feeds.. You sure you were not trying to access via a proxy?

Or were being redirected?

Maybe trying to route your traffic thru some ultra secure -- all about your privacy vpn/proxy.. That was doing mitm on you ;) You know - for your privacy ;) heheheh

Did you grab the info from the cert that was being listed as selfsigned? This can normally lead to a clue.. For example at work you can see that is a bluecoat created cert..

@johnpoz No, I'm sure. Added a few feeds:

https://blocklist.cyberthreatcoalition.org/vetted/domain.txt
https://urlhaus.abuse.ch/downloads/text/
https://zerodot1.gitlab.io/CoinBlockerLists/list.txt

No proxy, no vpn, no tin foil hats.

johnpoz

Those feeds are showing good for you right? That first one is on a cloudflare cert.. etc..

@johnpoz Yes, they did.

@johnpoz John, I have to go. Thanks again for your help. I'll check back later in the day.