Welcome to my frustration ;-) I'm probably naive, but I think our VMs are pretty secure. We're running on Azure, we are fully patched on all the software we use (Win2008, Apache Server, Java, Jenkins and the various players) and we expose a minimal attach surface (ports, access controls etc.). I'd say the weakest link is (as always) the carbon based life form at the keyboard. Anybody subscribed to private@ has the admin account credentials... but if we can't trust ourselves, who can we trust?
EdB On Sat, Apr 19, 2014 at 6:56 AM, Alex Harui <aha...@adobe.com> wrote: > After seeing this latest run of failures, does anybody still want to rely > on build.a.o for anything? > > If anything, we should ask builds@ to email their list when they do > critical security upgrades so we can try to keep up on our build machine. > I think there's a chance that a multi-project server is likely to have a > huge pile of jars from all over the place which is more exposed than the > few jars for our flex-only server. We just have to learn how to harden it > at least as well as builds.a.o. Shouldn't that be possible? > > And I have to admit that I'm tempted to point the next version of the > installer out to our Flex CI server for its config or mirror the whole > site. We can't even modify our site right now. > > -Alex > > On 4/17/14 3:58 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > >HI, > > > >> Do we want to at least use the ASF build server for providing official > >> nightly dev builds? > >+1 We can resonably trust infra machines to be secure and that non one > >has fiddled with the nightly builds. Our own set up machines are likely > >to be less secure and there's a small risk that something bad could > >happen. > > > >Thanks, > >Justin > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
