500 karma · joined March 26, 2014
Any time you want to show me a 100% future-proof algorithm for sensitive-info detection that works across any/all code on github, I'd be happy to toss my hat in and say, "I was wrong", until then, people will never ever beat 0days they don't know exist (0day being more than just a SW exploit). Just do.not.commit.sensitive.info.to.github. Period. That is the only sure way to not mess it up. Software only executes what is in the code, regardless of how nonsensical it is (aka, your code will not save you from messing up, something something something, PEBKAC)
I'm not arguing it's "impossible to play this game" It's 100% possible to play it when and how you'd like. I'm discussing the rate of "did I win (read: not get pwnd)?" It's cat and mouse of automation for vulnerable/sensitive info ... but all of that is rendered moot if you ... wait for it ... don't commit it to Github which would mean it wouldn't get to Github's API which means it wouldn't appear in 3rd party services sucking the firehose from Github cloud-y silicon teet.
And expanding on this ... committing your passwords and sensitive info to your code-repo is so misguided it's actually funny. What happens if you have an employee and they go off the deep end? Whoops, gotta rotate all those passwords/credentials/un-fuck every branch/resync dev's machines/etc. Keeping that sensitive info in a private, self-hosted, well-maintained internal repo (with strong ACLs, especially wrt server/hosting environments) will go significantly further for your team's security than submitting a feature request to a company to stop you from making arbitrary mistakes every so often.
No matter how clever you get with your pattern matching, you're going to have to always play catch-up with Web Framework N+1's format / weird-ass package manager. The dual approach is the only sensible approach because it expands your coverage. The important thing to this is to internalize the knowledge learned from 3rd parties and integrate that into your native process / tools, but not everyone will do that.
It'd be grand if we could say, "yeah, they should take care of my security for me because I'm paying them" but reality is a bitch. It doesn't matter what they were 'supposed' to do if there was an infosec leak or attack, you can't ctrl-z that (set of) event(s) and that info is out there, so it must be fixed (re-roll credentials, regen keys/certs, etc) and accounted for next time. There really is no 'getting ahead' but 'being less behind' will at least help mitigate getting eaten from the herd ;-)
There will never be a 100%-fool-proof "Did you mean to commit this sensitive unicode string?" but getting in front of that with a, "ok, I've checked my code, ran my tests, pruned the sensitive data, is there anything I'm missing?" will go a long way both in present and future times.
There's an issue with your example. Google looks for the substr 'attach', but does it know that a file with a string 20 chars from the newline 50 lines deep with two single quotes is actually your root password? There's a world of difference between keying off of a word/phrase and understanding the context of a larger document+metadata. Trusting computers to do the latter will result in bad times for all, while learning for yourself can help spread the knowledge to those that are both technically inclined or not (infosec is everyone's issue!).
Sure, just enumerate any and all possible types of sensitive data, the format they may be in, regex / matching functions to account for them (supported across 20+ programming languages) and I'm sure Github will have that done asap.
Alternatively, don't commit passwords/API-keys/sensitive-info to your repo.
Remember: Fingerprint locks are convenient, but they discard your ability to "forget" or refuse to unlock a device. They remove consent.
[ source - https://twitter.com/SwiftOnSecurity / https://imgur.com/a/1PDRJ / ]
Can anyone intent on downvoting explain what is factually wrong or misleading about the quote in the picture? Just because it's on a picture doesn't make it less valid.
I've found Piwik to be a great open-source (+ self-hosted) alternative - http://piwik.org/
(If you do flush out your thesis, I'd love to read it)
How long is the average paternity leave for new fathers? Or are you suggesting that fathers don't have a right to paternity leave and thus raise their children?
Interesting that you explicitly mention you'd do it without their knowledge/consent...
Never using VC backed services seems to be the first step.
When laws are in place to prevent jailbreaking or using alternative app stores, and those app stores are ordered to remove that application (by court order), for the majority of individuals it is banned (from a strictly law-abiding perspective). danieltillett was positing that it was good that Google and Apple had it ordered for removal because it was abused. But if we assert that it is acceptable to ban anything that can be abused, how does one (or everyone) decide that one tool should be banned but not another? That is what I was asking, and then I was told that no one mentioned banning yet DT and OP were both discussing the ban of an application.
Now if you'll excuse me, I have to get all stress-testing tools removed from the internet because someone could possibly use them to DDoS a site /s
How is a court order not considered banning?
See, that right there. That is why your anonymous social network isn't going to work or catch on. You're already openly declaring you're tracking your users and then planning on using their data in some fashion that they have no control over. You'll never get the early core adopters you'd need to verify the claims of anonymity, security/cryptography, and so on. Trying to involve money taints long-term roadmap direction and intentions.
We have a long way to go in educating the general public about technology, its benefits, and its pitfalls.