On Tue, 30 Apr 2013 02:05:22 -0700 (PDT), Steve F wrote:
> Morning all,
Same to you.
You might want to set your Usenet client G2/webform to line wrap
around 70 characters. That allows reply depth indicators to not cause
line wrap most of the time. It also is good Usenet etiquette.
Some subject matter experts may not bother to reply if they have to
reformat your text to fit the Usenet guidelines.
> Complete md5sum newbie here, and don't have a lot of experience with
shell scripting either.
Well, these might help. Ignore the ! and keyword string
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html ! basic shell bash doc
http://cfaj.freeshell.org/shell ! bash script tips usage doc
http://tldp.org/LDP/abs/html/index.html ! bash advanced documentation
http://mywiki.wooledge.org/BashFAQ/050 ! bash variable expansion document
>
> I've got a requirement to check a few binaries on a nightly basis
> for modifications (essentially we think one of our servers on a
> testing environment has some code injection problems, but without
> trawling through every line of code to track it, md5sum can just
> tell us IF the code has changed).
I would have thought the "find" utility and modification argument
would find all those for you.
> I understand how md5sum can tell us this information
> What I want is a bit of bash script that I can cron to run nightly
Sounds pretty easy so far.
> I have a script now that can check to see if the md5 changes
> (md5sum -c /path/to/file.md5) but it's capturing that output and
> notifying me the status is abnormal.
Well that seems to be just what you asked for. Throw it in the nightly
cron directory and you should be good to go.
> i'm hoping this is just a case of my coffee not kicking in yet but I'm stuck.
With out seeing your code, and exactly what you want, it is pretty hard
to tell you what you need.