Added by Victor Julien over 13 years ago. Updated over 13 years ago.
Description
We'll have to see if we can make the buildbot website public.
Things to consider:
- auth: no one should be able to modify w/o auth
- private data: private data like test pcaps should remain private
Other things?
It is almost done. Anonymous can just look at the interface. Authenticated users can start build.
Thing missing is an URL and an apache redirect to have everything accessible in HTTPS.
To what extend is private information protected? Mostly care about pcaps that we can't share publicly. But also private sigs (like from etpro).
I've discussed with people on #buildbot IRC channel. Web status do not provide any mean to get files used by buildslave and buildmaster. I've also study the code with the help of a confirmed twisted user and we get to the conclusion that, given the protection method inside twisted, this is the case.
https://buildbot.suricata-ids.org/
Thanks Eric.