HTTPS adoption has reached the tipping point

That’s it – I’m calling it – HTTPS adoption has now reached the moment of critical mass where it’s gathering enough momentum that it will very shortly become “the norm” rather than the exception it so frequently was in the past. In just the last few months, there’s been some really significant things happen that have caused me to make this call, here’s why I think we’re now at that tipping point.
We’ve already passed the halfway mark for requests served over HTTPS
This was one of the first signs that we’d finally hit that tipping point and it came a few months ago:

This is really significant – Mozilla is now seeing more secure traffic than it is non-secure traffic. Now that doesn’t mean that most sites are now HTTPS because that figure above has a huge portion of traffic served from a small number of big sites. Twitter, Facebook, Gmail etc.


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/LgqH-KPTvT8/

Original article

Time to Upgrade Your Python: TLS v1.2 Will Soon Be Mandatory

If you’re using an older Python without the most secure TLS implementation, this is the year to get serious about upgrading. Otherwise next June you may not be able to “pip install” packages from PyPI.PyPI’s maintainer Donald Stufft recently announced that python.org and related sites will begin disabling the old TLS versions 1.0 and 1.1. This change was imposed on us by our content delivery network, Fastly, in response to a change imposed on them by the Payment Card Industry Security Standards Council. In order to continue serving websites that take credit card payments, Fastly is required to disable the old, insecure versions of TLS. Since the PSF’s servers, including PyPI, use Fastly, the old versions of TLS will be disabled as well.Fastly wrote in October 2015,
There have been serious and systemic security issues with earlier versions of TLS and its predecessor, SSL, including POODLE, Heartbleed, and LOGJAM. These threatened


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/hQvMOHQx41g/time-to-upgrade-your-python-tls-v12.html

Original article

Data Loss at GitLab

GitLab, thanks for using PostgreSQL 9.6 and its replication and backup facilities.
We’re sorry that you lost your database:https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/
Thank you for posting this publicly to allow us to comment on this for your postmortem analysis.
I’m very happy that you monitor Replication Lag, that is good. Replication lag of 4GB is at times normal, so shouldn’t have caused major concern. I’ve recently fixed a bug in replication that caused replication to hang in some cases for up to a minute; we released a public fix to that and it will be included in the next maintenance release of PostgreSQL 9.6. It’s not certain that the bug was hit and, if it was, whether that was enough to cause the slow down noted. The openness of your response means we should do the same also, so I’m mentioning this issue here for that reason.
Restarting replication was probably unnecessary but if you shutdown the


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/ty8AsKhb4HI/

Original article

GitLab.com Melts Down After Wrong Directory Deleted, Backups Fail

An anonymous reader quotes a report from The Register: Source-code hub Gitlab.com is in meltdown after experiencing data loss as a result of what it has suddenly discovered are ineffectual backups. On Tuesday evening, Pacific Time, the startup issued the sobering series of tweets, starting with “We are performing emergency database maintenance, GitLab.com will be taken offline” and ending with “We accidentally deleted production data and might have to restore from backup. Google Doc with live notes [link].” Behind the scenes, a tired sysadmin, working late at night in the Netherlands, had accidentally deleted a directory on the wrong server during a frustrating database replication process: he wiped a folder containing 300GB of live production data that was due to be replicated. Just 4.5GB remained by the time he canceled the rm -rf command. The last potentially viable backup was taken six hours beforehand. That Google Doc mentioned in the


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/UJ8VUijm1lU/gitlabcom-melts-down-after-wrong-directory-deleted-backups-fail

Original article

How to capture and stream your gaming session on Linux

There may not be many hardcore gamers who use Linux, but there certainly are quite a lot Linux users who like to play a game now and then. If you are one of them and would like to show the world that Linux gaming isn’t a joke anymore, then you will find the following quick tutorial on how to capture and/or stream your gaming session interesting.


Original URL: https://www.howtoforge.com/tutorial/how-to-capture-and-stream-your-gaming-session-on-linux/

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: