Maybe word-regexp is not needed? about git-secrets HOT 3 OPEN

@vladimir-chernenko you pattern doesn't seem to match regardless. [a-z]*_(ro|rw|admin): is broken for your given example.

grep -nwHEI 'postgresql://[a-z]*:[a-z0-9]+' works, though. However, if a password might contain something that isn't letter, number, or underscore, you'll have to adjust accordingly. And test using grep -nwHEI since that is what git-secrets uses.

from git-secrets.

@russellshackleford
Hello. I have got a similar problem because git-secrets uses --word-regexp option implicitly.
So I propose to add some comments about --word-regexp option as follows:

<pattern>
The regex pattern to search. The pattern is passed to `git grep -nwHEI`.

I wanted to detect an api key in "apikey: ABCDEFGHIJKLMNOPQRST" format. But it failed.
You can reproduce the my situation as follows:

$ git init test-repo
Initialized empty Git repository in /Users/myoshiz/tmp/test-repo/.git/
$ cd test-repo
$ echo "apikey: ABCDEFGHIJKLMNOPQRST" > test.yml
$ git add .
$ git commit -m "test"
[master (root-commit) 19aa53b] test
 1 file changed, 1 insertion(+)
 create mode 100644 test.yml
$ git grep -nwHEI "\\s*(:|=>|=)\\s*(\"|')?[A-Za-z0-9]{20}(\"|')?"
(failed)
$ git grep -nwHEI "\\w+\\s*(:|=>|=)\\s*(\"|')?[A-Za-z0-9]{20}(\"|')?"
(succeeded)

from git-secrets.

grep is no longer invoked with -w

from git-secrets.