MD5 not matching File
-
Haaaaaaaaaaaaahahahahaha. Please, uninstall your browser "improvements". There's been a thread about this not even a month ago.
-
pretty sure even if you download via https still works.. But yeah with dok on this, those links are not https - so your running something that is switching it.
I show for example those links as http://files.atx.pfsense.org/mirror/updates/pfSense-Full-Update-2.2.4-RELEASE-i386.tgz
If you have tried to go there before with https then browser can remember that, etc.
You should not be getting pointed to https in those links, they are all http.
-
https://www.reddit.com/r/PFSENSE/comments/3notso/pfsenseorg_seems_down_docs_forums_any_alternates/
https://twitter.com/pfsense
-
So I just got this to happen with firefox 41, it likes to use https if you have on https for that site before. So I was getting links to https even though they don't work because I had been playing around with https on the previous threads about this.
i just cleared firefox cache, website prefs, etc.. And now it goes to http for all those mirrors like it suppose too.
-
https://www.reddit.com/r/PFSENSE/comments/3notso/pfsenseorg_seems_down_docs_forums_any_alternates/
https://twitter.com/pfsense
Hmmm, so all those 3 DNS servers are behind a single switch? Sounds like that needs some redesign.
-
Ok heres one for all you beautifully smart people I do not have "https everywhere" as an addon in Firefox Chrome or IE.
The only reference to it was in Eset NOD32 my AV but the selection was greyed out so I temp disabled Nod32 and still no DL
Since its effecting all 3 browsers Im thinking it must be Windows or perhaps a Arris router setting that forces Https. ???? If possible ???
BUT I just tried DL from Firefox in NEW PRIVATE WINDOW and VIOLA !!!!!! It worked ! Hurray
now to see if hashes match….......
-
Aaah, the famous ESET MITM thing… @TIm:
The only reference to it was in Eset NOD32
https://forum.pfsense.org/index.php?topic=93188.0
This "feature" is exactly as helpful in every AV out there.
-
OK I looked for an add-on for force HTTPS everywhere and found nothing.
There is a setting in Eset Nod32 for HTTP scanning but that's all greyed out so I didnt try to mess with it.
Disabled Nod32 and still didn't work.
Firefox, Chrome and IE would not go HTTP alone.
What finally did just work is 'New private window"
SO I just DL the first file and here are the hashes
pfSense-memstick-2.2.4-RELEASE-i386(1).img.gz f45cd3be36e5c44704352caa9172b723
MD5 12e914c5fe740ee55c8ebfa958fe16c2
Back to the beginning…... no matching hash
-
Yeah, dude. Reinstall that superscrewed box. (And skip ESET.)
-
Yeah, dude. Reinstall that superscrewed box. (And skip ESET.)
I can actually appreciate difficult issues like this because they are learning opportunities. I thank all of you for taking the time to help me out BUT when you just basically say F' it just reinstall
I'd at least like an explanation as to why you think that would be the best course. To me that sounds like 1st level tech support. Are there certain circumstances that can effect the hash process
to cause mismatch ?
-
Your internet is messing up your downloads. Call your ISP.
-
I thank all of you for taking the time to help me out BUT when you just basically say F' it just reinstall
A lot of us maintain these firewalls in corporate settings, and you often don't have the luxury of drilling down to the _n_th level to find out the source of a problem. Oftentimes it's pragmatism that drives everything, and Get 'Er Done is more important than Who? How? Why?
