2018
GitHub - UnaPibaGeek/ctfr: Abusing Certificate Transparency logs for getting HTTPS websites subdomains.
Abusing Certificate Transparency logs for getting HTTPS websites subdomains.
2017
2016
Certbot
Automatically enable HTTPS on your website with EFF's Certbot, deploying Let's Encrypt certificates.
2015
New Chrome security policy: powerful features will be removed on insecure origins
by 1 otherGoogle recently announced a security policy change that will impact future versions of the Chrome browser. Chrome is already warning that support to powerful features on insecure origins (HTTP) is deprecated, and according to recent announcements the removal will take place soon.
The impact of Google’s new Chrome security policy on WebRTC | TokBox Blog
After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.
Deprecating Powerful Features on Insecure Origins - The Chromium Projects
(via)
As with gradually marking HTTP as non-secure, we expect to gradually migrate these features to secure-only, based on thresholds of usage, starting with lowest usage and moving towards higher. We also expect to gradually indicate in the UX that the features are deprecated for non-secure origins.
Dans Chrome, un site HTTP sera marqué non sécurisé
Comme vous le savez, Google pousse tout le monde à passer son site en HTTPS. La dernière trouvaille est que Chrome affiche un avertissement pour les sites en HTTP, indiquant qu'ils ne sont pas sécurisés...
2011
2007
SecuObs - Installation sécurisée d'Apache Openssl, Php4, Mysql, Mod_ssl, Mod_rewrite, Mod_perl , Mod_security
Installation sécurisée d'Apache Openssl, Php4, Mysql, Mod_ssl, Mod_rewrite, Mod_perl , Mod_security
1
(9 marks)
