AI Can Scour Code To Find Accidentally Public Passwords (qz.com)
An anonymous reader shares a report: Researchers at software infrastructure firm Pivotal have taught AI to locate this accidentally public sensitive information in a surprising way: By looking at the code as if it were a picture. Since modern artificial intelligence is arguably better than humans at identifying minute differences in images, telling the difference between a password and normal code for a computer is just like recognizing a dog from a cat. The best way to check whether private passwords or sensitive information has been left public today is to use hand-coded rules called "regular expressions." These rules tell a computer to find any string of characters that meets specific criteria, like length and included characters.
There's realtively few instances where mixed capitals, symbols and numbers are valid syntax. yes there are, but few. sounds like we just made it easy to spot thepassword.
Some drink at the fountain of knowledge. Others just gargle.
I do this from time to time myself. I just do the following: .bash_history and cause an issue there.
# grep -r Pa55W0rd $HOME
Note the space before the grep. That way it does not end up in
I have found some from time to time.
I am the only person on my PC, but security is a mentality.
Don't fight for your country, if your country does not fight for you.
I think what they are trying to say is this:
Researchers have a new way using AI.
In currently deployed, publicly available systems, the best way is regex. The new AI way may be better.
While regex is a reasonably good tool for the task, I don't know that it's the BEST way currently used. A small, simple routine built specifically for the task may be better because regex takes characters in order. It's difficult (and slow) to build a really good regex for this because you mostly don't care what order they are in. You care that you have groups of upper case, lower case, numbers, and certain punctuation. Regex is good for finding this OR that, but not so good at this AND that AND that, in any order.
Google Search. site:Domain and the word password.
You'd be dismayed at how stupid some people are. Or maybe just not surprised.
Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.
and if it becomes self-aware regex then they have three problems, two of which don't matter anymore
Some drink at the fountain of knowledge. Others just gargle.
Sounds like another "let's force everything into TensorFlow's image prediction system" thing.
...to find clickbait articles about AI?
Have we really reached the point on a 'News for Nerds' site where we need to explain the term 'regular expression'?
telling the difference between a password and normal code for a computer is just like recognizing a dog from a cat.
Well, unless the code is PERL - then it looks like a password that has been spread over however many lines.
That is all.
best way to check whether private passwords or sensitive information
Easily defeated
politicians are like babies' nappies: they should both be changed regularly and for the same reasons
> ...is to use hand-coded rules called "regular expressions."
You mean: ...is to use hand-coded rules called "^regular expressions\.$"
Good luck avoiding those "relatively few instances" in a Perl script.
I do not have a signature
every language is parsable. Parsing rule sets can be written out in YACC. the rules tend to be incredibly simple and simply use recursion for deep nested cases. As a result it's not a terribly hard task to decide if a small fragment could be expanded to legal code or if it's not legal code.
Perls use of sigils actually is actually there to improve both to simplify parsing as well as to make it human readable. Yeah yeah... human readable jokes about perl. Ha Ha. But really you can look at perl and tell what catergory a variable is from the sigils-- it's actually giving you information. And as result constrains the parse.
Some drink at the fountain of knowledge. Others just gargle.
If I were doing it I'd have the AI discriminate what regexes will extract passwords most efficiently.
Some drink at the fountain of knowledge. Others just gargle.
There's realtively few instances where mixed capitals, symbols and numbers are valid syntax. yes there are, but few. sounds like we just made it easy to spot thepassword.
When you're talking about b00B$ but don't want to hit on any keyword censors at work?
"That's the way to do it" - Punch
/sarcasm Ah, cool, another alternative to for: