search

Talkaboutcybersecurity / GitMonitor

One way to continuously monitor sensitive information that could be exposed on Github
GNU Lesser General Public License v3.0
175 stars 42 forks source link

grep: Invalid range end why? #3

Open zglxw opened 4 years ago

zglxw commented 4 years ago

Cloning https://github.com/collective/groundwire.sf_payment_recorder.git

INFO: Working with Sensitive Filtering Rule ...

grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end

crazykid95 commented 4 years ago

It seems that this is a issue of grep. Which Grep version are you using? Let's try to get the Grep version using the Grep -V command

zglxw commented 4 years ago

[root@rc]# grep -V grep (GNU grep) 2.20 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

crazykid95 commented 4 years ago

Looks like an old version of grep, try upgrading your grep, egrep