News for hackers. Stuff that matters.
Re:Travis CI Security Advisory: Secured Environment Variables by andrewvc on Monday May 08, 2017 @05:35PM (#14295830)
While I love travis for what it is, this is a foreseeable result here.

At the very least they need to add a failsafe that checks all outgoing logs for any secure tokens and replaces them with '*' or something.

If you sign up to play a game of whack-a-mole you will lose eventually.

Re:Travis CI Security Advisory: Secured Environment Variables by wwwigham on Monday May 08, 2017 @05:42PM (#14295877)
That's actually exactly what the stated mitigation they've implemented is, if I've read it correctly. Though they're working on building it into their VM images in order to reduce the memory overhead of the filter.
Re:Travis CI Security Advisory: Secured Environment Variables by tehlike on Monday May 08, 2017 @06:21PM (#14296179)
What if the token was encrypted or altered in a way simple find replace wouldnt work?
Re:Travis CI Security Advisory: Secured Environment Variables by ReverseCold on Tuesday May 09, 2017 @11:05AM (#14300630)
Even just encoding it differently (base64, bin, hex, etc) would work against that.