Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Parsing data from an NBE file |
|---|---|
| Date: | Sat, 13 Nov 2004 18:22:59 +0100 |
On Fri Nov 12 2004 at 20:54, Christopher J Bidwell wrote:
grep 172.23.3 oldnbe.nbe > newnbe.nbe This obviously isn't very precise in that I'm going to get 172.23.3, 172.23.30-39, etc. How can I make my greps more precise when doing this?
grep uses regex. "." is a special character that matches anything. You have to escape it (as it was already answered) or use fgrep (or grep -F) which matches strings -- arboi@alussinan.org http://arboi.da.ru NASL2 reference manual http://michel.arboi.free.fr/nasl2ref/ _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Inprotect interface question - MySQL version, Greg Kuhnert |
|---|---|
| Next by Date: | Is this expected output or a bug?, Greg Kuhnert |
| Previous by Thread: | Re: Parsing data from an NBE file, Erik Stephens |
| Next by Thread: | RE: Parsing data from an NBE file, SRH-Lists |
| Indexes: | [Date] [Thread] [Top] [All Lists] |