[Bro-Dev] CBAN design proposal
Slagell, Adam J
slagell at illinois.edu
Tue May 24 10:11:24 PDT 2016
> On May 24, 2016, at 12:07 PM, Siwek, Jon <jsiwek at illinois.edu> wrote:
>> On May 23, 2016, at 6:30 PM, Slagell, Adam J <slagell at illinois.edu> wrote:
>> I guess there is a balance here. If we do no mandatory checks and you could submit something that isn’t even a Bro plugin, the repository could become cluttered with junk. Do we really want things that don’t even “compile”?
> The clutter could still be removed by an out-of-band process. e.g. there’s no initial check for whether a submission actually works, but after X days of a nightly process finding it is broken, it gets auto-removed.
That is a good point. I am more concerned about accumulating clutter.
Adam J. Slagell
Chief Information Security Officer
Director, Cybersecurity Division
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