Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of apache@robweir.com designates
 69.89.21.8 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <013401cc4e2e$03843580$0a8ca080$@apache.org>
References: <013401cc4e2e$03843580$0a8ca080$@apache.org>
Date: Fri, 29 Jul 2011 16:55:06 -0400
Message-ID: 
 <CAP-ksogcmEANRPsEQ7cg0nGnTsp=YQ6O7mR04HK73LLv3AaD2w@mail.gmail.com>
Subject: Re: Operating ooo-security (was RE: Population of ooo-security)
From: Rob Weir <apache@robweir.com>
To: ooo-dev@incubator.apache.org, orcmid@apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 29, 2011 at 4:28 PM, Dennis E. Hamilton <orcmid@apache.org> wro=
te:
> We are in a very fledgling situation here. =C2=A0Let's see if we can clea=
r up a few things.
>
> Here is my understanding of the situation as it exists at the moment.
>
> =C2=A0- Dennis
>
> =C2=A01. The ooo-security@i.a.o list is private and moderated. =C2=A0Anyo=
ne can send a message to the list. =C2=A0The three current moderators of th=
e list share responsibility for allowing a post onto the list or not. =C2=
=A0Anyone can also attempt to subscribe to the list. =C2=A0Once the request=
er completes the e-mail verification ceremony, the request is submitted for=
 approval by the moderators. =C2=A0In this case, the way the moderators dec=
line is by doing nothing.
>
> =C2=A02. It is the PPMC that is entirely responsible for handling the mit=
igation of security issues, including undisclosed exploits. =C2=A0No one el=
se. =C2=A0That means it is the PPMC that would authorize a patch. =C2=A0If,=
 for some reason, any non-Apache-committer submitted a patch, it would pres=
umably be treated the same as any patch submission on ooo-dev, apart from t=
he additional secrecy of the activity until the mitigation is in place.

Reading the process, I'm seeing that the security "project team"
decides if a patch is needed.  They authorize it.  That's why I said
the security list is acting as "agents" of the PPMC.  By agreement
we've decided that it is not best for security to have the entire PPMC
on the security list.   So the PPMC has the responsibility and
authority, but cannot effectively exercise it in the absence of
information.    So these decisions are effectively delegated to the
security list members.

So I think you are right, but only if we're careful how we distinguish
"responsibility" and "delegated authority".

> =C2=A0 However, there are many activities that go into the assessment of =
a security issue and the analysis of potential mitigation approaches. =C2=
=A0They might never involve the actual creation of code or patches.
>
> =C2=A03. It is the PPMC, as part of its responsibilities, with the advice=
 (and consent?) of security@a.o, that determines how the ooo-security@i.a.o=
 list is managed and who serves on it.
>
> =C2=A04. Perhaps we should look at the ooo-security@i.a.o list subscriber=
s as strictly advisory to the PPMC. =C2=A0The subscribers would have the sp=
ecific charge of handling the inputs that are accepted as bona fide securit=
y matters with appropriate sensitivity. =C2=A0We need to be careful to oper=
ate within the norms for dealing with undisclosed vulnerabilities and prosp=
ective exploits and maintaining the security of all preparations and ooo-se=
curity@i.a.o are the shepherds for this, let's say. =C2=A0We don't quite kn=
ow how this will work out in practice and how much the ooo-security@i.a.o s=
ubscribers will work things out before engaging the PPMC as a whole.
>

I'm seeing this as being more than advisory.  For example, I'm not
seeing at any stage where we would bring a summary of a reported
vulnerability to the PPMC, even on the private list.  The whole reason
for having the ooo-security list in the first place was to avoid
having information broadcast widely, which is what would happen with a
PPMC the size we have today.  So I think that ooo-security "owns" the
resolution of reported issues, at least that is how it is described by
this page:

http://www.apache.org/security/committers.html

> In none of this do I see a requirement for a committer, or even PPMC memb=
ership for someone who is subscribed to the list for purposes of supporting=
 the coordination with others who need to be responders (as in a multi-alar=
m fire), and reciprocally, since anyone might be the "first responder." =C2=
=A0Requiring an iCLA I can understand, with regard to IP matters that might=
 arise, although that might be more symbolic than essential. =C2=A0But if t=
he practice is to require PPMC members, then that is what we should do. =C2=
=A0The current subscribers are all PPMC members.
>

I'd also note that the subscribers of ooo-security must work well
together with each other and with security.a.o.  This is not only a
technical task, but also a social one and involves how we resolve
disagreements, make decisions, etc.  This should be done in accordance
with The Apache Way.  I think that is important.   We also have a
direct interaction (in the general case) with the external 3rd party
who has submitted the report.  So we're the "Face of Apache" at that
moment, and that is a serious responsibility.  Since we operate in
isolation from the PPMC, for secrecy reasons, we also need the
confidence and trust of the PPMC.  And since we are collaborating on a
patch, in secret, I think the iCLA is relevant.

> Although I favor a more ecumenical arrangement than we are putting in pla=
ce, we can of course make it work without that. =C2=A0We can provide liaiso=
n already with the small ooo-security@i.a.o subscriber list that we have no=
w. =C2=A0That will be necessarily selective, and it is not clear what agree=
ment needs to be reached before any external entities are engaged. =C2=A0We=
'll have to figure that out.
>

I think it will be good to tease out the differences between getting
help to analyze and resolve an issue versus what additional parties
should receive pre-notification.  It sounds like OpenOffice conflated
both of these things into one list, with one membership.  But they are
really two different things.

> We can also create the arrangements that Rob Weir proposes for having an =
alert mechanism and having a PPMC-maintained (private) list of contacts bot=
h for alerts and for experts.
>
> -----Original Message-----
> From: Danese Cooper [mailto:danese@gmail.com]
> Sent: Friday, July 29, 2011 09:55
> To: ooo-dev@incubator.apache.org
> Subject: Re: Population of ooo-security
>
> [ ... ]
>
> =C2=A0Only people recognized as committers can "own" the
> problem of security for this codebase. =C2=A0It is this way to protect bo=
th the
> ASF and the codebase.
>
> [ ... ]
>
> I'd propose that we (as a project) decide how best to work with LibreOffi=
ce
> to identify people who would like to serve as liasons for security. If
> indeed nobody wants to sign an iCLA, then we'll gladly subscribe LO to
> receive downstream notifications rather than early disclosure of any issu=
es
> that arise. =C2=A0That is suboptimal, but until more diplomacy and trust =
work is
> done it may be the best we can do.
>
> [ ... ]
>
>