Post-Mortem and Security Advisory: Data Exposure After travis-ci.com Outage
> The shell the tests ran in unknowingly had a DATABASE_URL environment variable set as our production database. It was an old terminal window in a tmux session that had been used for inspecting production data many days before. The developer returned to this window and executed the test suite with the DATABASE_URL still set.<p>I was expecting something like this. I remember, I configured my terminal windows to change their background when I'm on production systems [2], after around I read about gitlab database incident [1].<p>1 : <a href="https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/" rel="nofollow">https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...</a><p>2 : <a href="http://www.drinchev.com/blog/ssh-and-terminal-background/" rel="nofollow">http://www.drinchev.com/blog/ssh-and-terminal-background/</a>