[Osiris-devel]updated specs

[B Potter]

Howdy,
When you say "shipping master databases for common systems"... I know what
you mean (the md5 uber DB we talked about).  But what do you mean by
"shipping" and why do claim TW can't do it?

Osiris "will require the use of a configuration file".  Is there a chance
we could get it to run from . with sane defaults if you specify an output
file?  Do folks think this would be useful?  If the program runs like
that, it should prompt the user before it assumes these defaults to avoid
troubleshooting problems... and should have a way to override the prompt.

maybe a config file for scale?  maybe?

I like the command line options and stuff.. that looks solid.

With the uid(x), group(x), etc.. maybe.. just maybe md5(x) as well... to
uh.. hook into a DB of known "bad" md5's.  I still really like that
project idea... just need to find someone with time on their hands :)

I REALLY like the conf file now.  It feels... familiar, somehow ;)  The
only think I could think to change would be to shitcan the
"file" directive.  If you want just a file in a dir, I think we should
force them to do

<Directory /etc>
	ignore		file(!resolv.conf)
</Directory>

or something like that.  It just keeps everything unified.

thoughts?  swift kicks to the head?  feel free to shoot down any of
this.  I really think things are pretty solid now, we're just getting into
some of the nitty-gritty.

later

bruce




On Sat, 17 Mar 2001, Brian Wotring wrote:

> 
> speak up if anybody has problems or questions, specifically with the 
> inputs/outputs stuff.
> 
> --
>   Brian Wotring  ( brian at shmoo.com )
>   PGP KeyID: 0x9674763D
> 
> 
> _______________________________________________
> Osiris-devel mailing list
> Osiris-devel at shmoo.com
> http://www.shmoo.com/mailman/listinfo/osiris-devel
>