As demonstrated by anttiviljami on Github browser-autofill-phishing allows for Chrome to leak additional…
Following on from my post the other day about how the current beta version of Chrome has the ability to mark websites as Not Secure. Google has now confirmed this will be implemented in Chrome 56 release…
Chrome 55 (latest beta build available via Chrome Canary) has the ability to specifically flag a HTTP website as non secure.
If your site has a login form make sure you are using HTTPS as the major browsers are starting to warn users about lack of encryption.
If your website loads a form using type=”password” the browsers assume this means you have some…
From Chrome 46 websites that have HTTPS errors will no longer display any padlock in the browser window.
At Servertastic we make the ability to purchase an SSL Certificate as simple as we possibly can. But as an installer you have many things you need to consider to ensure your site uses the best encryption available to secure the HTTPS site.
Symantec applauds Adam Langley’s resolve to increase consumer safety on the web, however, his proposal to remove OCSP and CRLs in a future release of the Chrome browser is misguided and could potentially have dangerous…