[Osiris-devel]updated specs

[B Potter]

> Sorry, poor wording on my part.  I meant "provide", and I meant it's 
> something that Tripwire does not make available.  If you didn't create a 
> database before you put the machine on the network, you can't track things 
> from the very beginning.  I know it would be time consuming to maintain but 
> I'm for giving it a try.  The subject keeps coming up as a great idea with 
> the various people I talk to.

roger that.. kewl.
> 
> I agree.  How about this.  If no configuration file is used, it assumes 
> reasonable defaults.  These defaults are then clearly shown before it 
> begins, with a prompt.  This prompt can be overidden.  If no directories 
> are given ( -i ) then "." is the default.  I think this covers everything 
> you suggested.  Basically you could run osiris in the current directory 
> with only:   ./osiris -o scan.osi

groovy
> 
> > maybe a config file for scale?  maybe?
> 
> what for?
> 
ignore me on that.. I just looked at the usage statement for scale and
it's really small and would vary from run to run.  I thought if someone
would have a "common" enough run for scale they might want a conf file for
it... but I _really_ doubt that would ever happen.  I'll go back to
smoking crack now

> yup.  That sounds useful, basically you would need one for every algorithm 
> supported:
> 
>     md5(x)
>     sha(x)
>     haval(x)
>     ripemd(x)
doh.. I keep forgetting about the other hashes... yeah, we'll have to do
them all.

later

bruce