From: Fernando <ferosspublic@comcast.net>
To: linux-admin@vger.kernel.org
Subject: Re: Need Help with making a bash script
Date: Tue, 01 Jun 2004 09:03:46 -0400 [thread overview]
Message-ID: <c9huri$mk5$1@sea.gmane.org> (raw)
In-Reply-To: <20040529130043.1ac11622@downtown>
Russell Evans wrote:
> On Fri, 28 May 2004 17:36:49 -0400
> "Fernando" <ferosspublic@comcast.net> wrote:
>
>
>>I have two problems.
>>
>>
>>1. I'm making a script to add IP's to my blacklist...
>>
>>I need to add three <tabs>, the word 'REJECT' and a #DDMMYYYY that
>>it's being done to a text file that has the IP's in it... ie this is
>>the original list;
>>
>>80.25.148.216
>>80.43.197.197
>>
>>needs to end up like this...
>>
>>80.25.148.216 REJECT #28052004
>>80.43.197.197 REJECT #28052004
>>
>
>
> Assuming that you are documenting why you are blocking an address,
> instead of the date as a comment, you might was to use a case number.
> The case number would point to a record of the event that triggered the
> blocking, with the appropriate log files snips, packet traces, machines
> effected, ...
>
> Thank you
> Russell
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I was thinking about putting the date in because I was going to clear
out IP's after a couple of months. Just in case it was a one time error
where they sent out infected email. The case number system sounds
interesting, would I need it for CYA for anything?
prev parent reply other threads:[~2004-06-01 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 21:36 Need Help with making a bash script Fernando
2004-05-28 22:40 ` Jens Knoell
2004-05-28 22:43 ` Herta Van den Eynde
2004-05-29 5:04 ` Fernando
2004-05-28 23:52 ` chuck gelm
2004-05-29 0:05 ` chuck gelm
2004-05-29 0:59 ` A. R. Vener
2004-05-29 20:00 ` Russell Evans
2004-06-01 13:03 ` Fernando [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='c9huri$mk5$1@sea.gmane.org' \
--to=ferosspublic@comcast.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.