News for hackers. Stuff that matters.
Re:Travis CI Security Advisory: Secured Environment Variables by mintplant on Monday May 08, 2017 @08:33PM (#14296826)
> As this fix runs in Ruby, it results in larger memory overhead. To address this, we are working on an executable binary that will be installed as part of the build-image. Work on this is expected to be complete by the end of the week.

Run it through sed?

Re:Travis CI Security Advisory: Secured Environment Variables by jacques_chester on Monday May 08, 2017 @08:47PM (#14296879)
We hit this in Cloud Foundry Buildpacks, where all the builds and logs are completely public[0].

The team wrote and added Concourse-Filter[1]. You stream logs through it. It compares what's going past to current environment variables. Anytime something goes past that looks like one of the environment variables, it blanks it out.

You can set a whitelist for things you're not fussed about.

Disclosure: I have twice worked on Buildpacks on behalf of Pivotal.

[0] https://buildpacks.ci.cf-app.com/

[1] https://github.com/pivotal-cf-experimental/concourse-filter