logo  Collatz Conjecture
log in

Powered by BOINC

User of the day

User profile Profile Beyond
I'm retired and DC is one of my hobbies along with marathon canoe racing and XC skiing. In the work world was a network manager and most recently a...

News

Power Outage
The power was out while I was gone for the weekend. Everything should be back to normal now though. 22 Aug 2016, 0:11:51 UTC · Comment


Firewall Failure
Internet access was lost last night due to the magic smoke being released from a capacitor in the firewall's power supply. The backup firewall will be used until I replace the primary firewall. 9 Aug 2016, 16:10:27 UTC · Comment


SSL Certificate Replaced
After finally getting the site cleared by Google's security scan, I was able to apply for and install a new SSL certificate. Thanks for your patience. 28 Oct 2015, 13:29:26 UTC · Comment


Google's Anti-Malware Detection Gives False Positives
For the last several months, Google has identified the Collatz apps as "having an unknown virus". I have asked Google for specifics since their scan states that Collatz has "Undetermined malware" and all virus scans I have done show no issues.

Because other sites relay on their security tools, I have not been able to update the expired SSL certificate. Since the BOINC client will not fall back to HTTP if there is an issue with the SSL Certificate (e.g. it is expired), I had to remove the certificate. That means that logins are no longer encrypted. Thanks, Google, you've accomplished the exact opposite of what you intended and all attempts to get you to rectify the situation have fallen on deaf ears.

Proof?
The applications that Google complains about are exactly the same as the ones created several years ago (before the suspected trojan even existed).

I can compile the application on a clean machined (fresh install of everything from DVDs direct from Microsoft) and the applications match the supposedly infected ones byte for byte.

The issue is that in order to scan the files quickly, Google uses a "thumbprint" of each virus and if the application happens to have any code that matches the small snippet in the thumbprint, Google deems it to be infected. Google __should__ check for the real virus instead of a thumbprint when it finds an initial match. That would avoid false positives. Instead, they assume they are correct and ban the site. Hmmmm... I thought we were supposed to be innocent until proven guilty, not just suspected of being guilty. But, I guess that's what happens when you become the 800 lb. gorilla.
22 Oct 2015, 14:22:30 UTC · Comment


Sieve in Production; Large and Solo deprecated
The collatz_sieve applications have been changed from beta to production status so all volunteers will now be getting them. I also increased the sieve workunit size by 4 times. I expect it will take BOINC a while to re-adjust it's runtime estimates as they are based on floating point calculations which aren't used in Collatz except to show the percent complete.

I deprecated the solo_collatz and large_collatz applications and disabled the associated work generators. Any that are in progress will still be validated, you just won't get any new solo or large WUs since you will receive sieve WUs instead.

If the sieve application fails immediately after it starts, you probably need to install the latest Microsoft Visual C++ runtime and, since BOINC will send your computer both 32 and 64 bit applications, you will need to install both the 32 and 64 but C++ runtime (see main page for a link or just Google it).
23 Sep 2015, 18:48:17 UTC · Comment


... more

News is available as an RSS feed   RSS





Copyright © 2016 Jon Sonntag; All rights reserved.