I just got my eligius payout, like clockwork. On pretty much the same schedule as every other payout. Despite the fact that the pool has been having so many problems, and that wizkid has had to work himself absolutely ragged to keep it running.  

Last thing he or this thread needs is you trolling and being a general retard (which you absolutely must be to be calling such a long running pool with such a solid track record of not losing shares a 'scam'). Just GTFO, go do something beneficial for the human race. Like walking into the freeway and getting hit by a truck before you can breed.

256-bit encryption should not be a reason for it to be considered invalid.

Odd that you're seeing a "parts that are not secure" message on multibit.org - I don't see that. I believe that is Chrome's equivalent of the 'mixed content' warning, which means that some elements of the page were served up over HTTP rather than HTTPS, which as far as I can tell shouldn't be happening on multibit.org and isn't here. Malware may actually be a possibility, perhaps something is injecting ads or something served over HTTP into the page for you?

Try the following, maybe:

• CTRL-SHIFT-I to open the Chrome inspector window (while on multibit.org)
• Go to the Network tab
• Right click the column headers (Name, Method, Status, etc) and enable 'Scheme' as a column
• Force a page refresh with CTRL-F5 with the inspector window still open.
• Now check for anything in the list of resources fetched which has a Scheme of 'http' instead of 'https'.

If there's anything http there, that would explain Chrome's complaint, and might be indicative of something being injected (since I see nothing being linked via HTTP on multibit.org here). Perhaps malware, a proxy, a chrome extension, or even your ISP?

It's green for me in Chrome as well.

If it's red, your browser thinks it is illegitimate, of course. Could be that someone your browser's trusted keys are borked? multibit.org's cert is signed by Startcom, maybe somehow Startcom CA cert has been ripped out of your Chrome's stash of trusted keys? No idea how, mind you, but it would explain it...

Is it possible that your machine's clock is totally wrong, set in the future? The SSL cert for multibit.org expires in Dec 2015, so if your machine thought it was past that date, that would be another explanation... you'd likely be having problems with more than Chrome though.

If you click on the lock icon beside the https, and look under the Connection tab there, it should give some further info about why it doesn't trust the cert.