bob3160
4841
I prefer this link: https://www.avast.com/en-us/privacy-policy . It’s up to date.
The one you posted gives a chopped up excerpt from a year old forum post. 
BeSecure
4842
polonus
4843
Is the cure worse than the initial problem?
CloudfFlare now offers a solution to the so-called mixed content problem: http://forums.theregister.co.uk/forum/1/2016/09/20/cloudflare_offers_encryption_up_the_wazoo/
Re-writing every link as HTTPS Everywhere where they could, and where they cannot the green padlock is misleading.
They hope soon all of the internet has turned HTTPS Everywhere.
For the record the El Reg is also on American CloudFlare,
and they also dealt an additional little smear to tor-developers, in their article.
By the way CloudFlare implemented their own certificate incorrectly:
Would you trust them with half-baked e2e encryption?
From the crypto-report:
Certificate is not installed correctly
cloudflare.com
This is not a Symantec certificate.
Please contact the Certificate Authority for further verification.
You have 2 errors
RSA wrong certificate installed.
The domain name does not match the certificate common name or SAN.
ECC wrong certificate installed.
The domain name does not match the certificate common name or SAN.
Info
BEAST
This server is vulnerable to a BEAST attack. More information.
Chain installation:
2 certificates found: RSA and ECC.
To view each certificate chain, click a tab below.
RSA
ECC
Certificate information
This server uses an Extended Validation (EV) certificate. Information about the site owner has been fully validated by COMODO CA Limited to help secure personal and financial information.
Common name:
SAN:
cloudflare.com, www.cloudflare.com
Valid from:
2015-Dec-01 00:00:00 GMT
Valid to:
2016-Nov-30 23:59:59 GMT
Certificate status:
Valid
Revocation check method:
OCSP
Organization:
CloudFlare, Inc.
Organizational unit:
COMODO EV Multi-Domain SSL
City/locality:
San Francisco
State/province:
California
Country:
US
Certificate Transparency:
Embedded in certificate
Serial number:
e3bb289893780deab01913b0a1400d77
Algorithm type:
SHA256withRSA
Key size:
2048
polonus
BeSecure
4844
polonus
4845
mchain
4846
Brian Krebs reports Google is now protecting him:
https://krebsonsecurity.com/2016/09/the-democratization-of-censorship/
Today, I am happy to report that the site is back up — this time under Project Shield, a free program run by Google to help protect journalists from online censorship. And make no mistake, DDoS attacks — particularly those the size of the assault that hit my site this week — are uniquely effective weapons for stomping on free speech, for reasons I’ll explore in this post.
polonus
4847
BeSecure
4848
BeSecure
4849
Asyn
4850
BeSecure
4851
Pondus
4852
Pondus
4853
mchain
4854
BeSecure
4855
polonus
4857
Pondus
4858
Asyn
4859
Target Czech-speaking countries, lock screen and pc and encrypts files and adds the extension .k0stya C partition, the D partition is clean!
Kostya Ransomware adds the extension .k0stya!Demonstration of attack video review.
https://youtu.be/Sti6F_VqC7Q
Is Avast! ready to deal with this ransomware?!!! :-\