[Bro-Dev] The BPAN project

Slagell, Adam J slagell at illinois.edu
Mon Mar 19 08:57:32 PDT 2012

On Mar 16, 2012, at 2:46 PM, Matthias Vallentin wrote:
> Requirements:
>    - Sharing scripts should be simple: one should be able to point
>      someone to a remote repository and the integration happens
>      automatically.

Dependencies will likely arise. Particularly problematic are extension scripts which require changes in base scripts that we ship. I don't think we can allow new scripts that require tweaks to base scripts.
>    - Organization by topic tags: similar to package managers, we need a
>      way to categorize scripts and bundle them. For example
>    - Separation between officially supported and user/experimental
>      scripts. For the official ones, we offer support and make sure
>      they'll always work with the latest/current version of Bro. We do
>      not make such a guarantee for external scripts.

I think the clear line between supported/not supported is what we ship with our tarballs.
> [1] Here are some other naming suggestions instead of BPAN:
>    - Bropane (Bro Policy script Archive NEtwork; inflammable)


>    - Brofuse (profuse: exuberantly plentiful)
>    - Browl (A bowl full of Bro scripts)
>    - Broil (Cooking with the community)
>    - Brodder (Bro protestants)
>    - Brovine (Grass-fed, no growth hormones)
> _______________________________________________
> bro-dev mailing list
> bro-dev at bro-ids.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Adam J. Slagell, CISO, CISSP
Chief Information Security Officer
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign

"Under the Illinois Freedom of Information Act (FOIA), any written communication to or from University employees regarding University business is a public record and may be subject to public disclosure." 

More information about the bro-dev mailing list