You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Michael Meeks <mi...@suse.com> on 2012/03/19 12:49:32 UTC
Fwd: Shutdown of the securityteam@openoffice.org mailing
Hi guys,
The appended mail was sent to the old multi-vendor security list at
openoffice.org recipients. That seems reasonable - the infrastructure is
coming to an end.
As previously discussed ( to death ;-) [ and I have no particular
desire to re-opening and re-hash the issue ] this
securityteam@openoffice.org list -used- to be the multi-vendor, neutral
place for reporting security vulnerabilities in openoffice.org and then
Apache OpenOffice.
With it's move to Apache hosting, I have a few questions:
a) will the composition of this list remain the same, or
will it change to exclude non Apache-committers ? or is
this cross-project list simply gone ?
b) in the light of a) will Apache OpenOffice be recommending
reports be made exclusively to this address ?
To re-iterate the status quo from the LibreOffice side: we recommend
that issues are directed to a joint mailing list:
officesecurity@lists.freedesktop.org that is vendor neutral,
cross-project, administered by both sides, neutrally hosted etc. That
helps avoid further, baseless accusations of information hiding, not
sharing etc. This was built on a foundation of reciprocal treatment.
Naturally, we maintain a private, internal security list for
LibreOffice developers to discuss fixes on in addition to that, and have
no issue with Apache OpenOffice doing likewise of course. It would be
good to know what the plan is from your side though.
Thanks,
Michael.
[snip]
Subject: [securityteam] Shutdown of the securityteam@openoffice.org mailing
Date: Mon, 12 Mar 2012 16:16:48 -0400
The securityteam@openoffice.org mailing list will cease operation on
or after March 15th, 2012. This list, as well as numerous other
legacy mailing lists, were kindly hosted by Oracle during the
transition of OpenOffice to Apache. Now that this infrastructure
transition is complete, the legacy lists will be retired.
The new address for reporting vulnerabilities to the Apache OpenOffice
project is : ooo-security@incubator.apache.org
Instructions for submitting reports to the project can be found at
http://security.openoffice.org
If you wish to be on a notification list for public announcements of
vulnerabilities and patches, you are invited to subscribe to our
announcement list by sending an email to
ooo-announce-subscribe@incubator.apache.org. We also publish
disclosures to full-disclosure@lists.grok.org.uk and
bugtraq@securityfocus.com.
Regards,
-Rob Weir, Apache OpenOffice Security Team
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Re: Shutdown of the securityteam@openoffice.org mailing
Posted by Rob Weir <ro...@apache.org>.
On Mon, Mar 19, 2012 at 8:44 AM, Michael Meeks <mi...@suse.com> wrote:
<snip>
* Do you commit to -immediately- forward any externally reported
> security vulnerabilities vs. OO.o to the LibreOffice project ?
>
> * If so - why not do this by advertising a cross-project
> shared security list, following our example ?
>
> * If not, why not ? & who does the forwarding & when ?
>
We (AOO Security Team) would contact the reporter of the issue to
determine their wishes. We would advise them if other products might
also be impacted. We would direct them to security contacts for the
other products, or offer to share their report with those projects,
as-is or in anonymized form.
Some security reporters appreciate and trust sending sensitive reports
to an Apache address, where they have ongoing relations and
experience. Some prefer this than sending to a list of unknown
composition and trustworthiness.
-Rob
Re: Shutdown of the securityteam@openoffice.org mailing
Posted by Michael Meeks <mi...@suse.com>.
Hi there,
On Mon, 2012-03-19 at 15:38 +0100, Jürgen Schmidt wrote:
> Michael, I really don't like to blame anybody here. You should know the
> truth and how the real story was. The patch was under ALv2 as our
> complete source code is now, at the least the code granted by Oracle.
Jurgen - this is simply not a blame game; the fact is that neither side
produced patches in a form that the other side could reasonably use :-)
We got this "... one LO developer refuses ..." stuff from Rob, the
reality is that it doesn't work well in either direction.
> So please stop to pervert the reality. We are open for any kind of
> collaboration here and we will share the information we have.
I dislike perverted realities as much as you do - but your statement
doesn't match what Rob suggests - that you will not share the
information you have in a timely way, but ask if submitters want to
share / re-submit elsewhere - which is rather different.
> It is another attempt to show that we don't want to
> collaborate but it is again not true and we are very open.
Sigh - the motivation is not to show anything, it is to discover what
the real situation is - and adapt to it.
> And the moment we have enough to do with our AOO project and don't take
> care about other projects. But we are open for any kind of serious
> collaboration at a time where we have time for it.
Well, it's encouraging. My concern is to clearly understand what your
project is doing - and then, separately to think about how best to react
to that.
And then Rob's mail:
On Mon, 2012-03-19 at 09:02 -0400, Rob Weir wrote:
> On Mon, Mar 19, 2012 at 8:44 AM, Michael Meeks <mi...@suse.com> wrote:
> > * Do you commit to -immediately- forward any externally reported
> > security vulnerabilities vs. OO.o to the LibreOffice project ?
>
> We (AOO Security Team) would contact the reporter of the issue to
> determine their wishes. We would advise them if other products might
> also be impacted. We would direct them to security contacts for the
> other products, or offer to share their report with those projects,
> as-is or in anonymized form.
Interesting. Reading your statement, it seems you commit to a
significant round-trip delay, and potential non-forwarding of relevant
security issues depending on the reporter's input.
> Some security reporters appreciate and trust sending sensitive reports
> to an Apache address, where they have ongoing relations and
> experience. Some prefer this than sending to a list of unknown
> composition and trustworthiness.
This could be read as casting a negative light on our competence and
trustworthiness which is an unappreciated slant.
It is at least clear however, and I am disappointed. We, LibreOffice
tried to reach out and ensure the highest standards of sharing
disclosures at source; if only in part to rebutt Rob's previous
ill-informed and inaccurate FUD in this area. We setup a neutrally
administered mailing list, and thus forced our submitters to
automatically send their reports to both projects.
It seems this collaborative method is not your preferred approach,
which is sad.
There are lots of other possible approaches that don't require a shared
mailing list - such as recommending multiple submitting to each other's
security lists on vulnerability submission pages that might work. To
make that a collaborative experience it has the downside of needing to
maintain CC's - something that has been broken in ~every other reply
made to this thread, sadly.
Constructive suggestions appreciated.
Regards,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Re: Shutdown of the securityteam@openoffice.org mailing
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 3/19/12 1:44 PM, Michael Meeks wrote:
> Hi Rob,
>
> On Mon, 2012-03-19 at 08:11 -0400, Rob Weir wrote:
>> We've discussed this all before, but to reiterate, the previous list
>> was a security list for a single open source project. It was hosted by
>> that open source project. I'm not seeing in what sense that was
>> neutral.
>
> It was project-neutral, it included LibreOffice and Apache OpenOffice,
> and Symphony developers and distributors.
>
>>> a) will the composition of this list remain the same, or
>>> will it change to exclude non Apache-committers ? or is
>>> this cross-project list simply gone ?
>>
>> The list subscribers consists of a subset of AOO committers as well
>> the Apache Security Team. As with all private lists, any Apache
>> Member is also able to subscribe or view the list archives.
>
> So I'll take that as: the previous project-neutral list being killed,
> and being replaced with an Apache OpenOffice specific list. That is
> indeed an unfortunate development worth noticing.
>
>> I> b) in the light of a) will Apache OpenOffice be recommending
>>> reports be made exclusively to this address ?
>>
>> You can see our security guidelines here:
>> http://incubator.apache.org/openofficeorg/security.html
>
> And you can contrast with ours here:
>
> http://www.libreoffice.org/advisories/
>
> "The security teams for products associated with the code-base
> can be contacted at officesecurity@lists.freedesktop.org, this
> includes representatives of many vendors, and associated
> projects."
>
>> Note: this has been our policy for several months, and in that time
>> we've been open with LO on sharing reports, analysis and even patches.
>
> That is interesting. I had imagined that you would continue to direct
> security bugs to the cross-project list, given your enthusiasm for that
> being -the- list to send reports to. I must admit I'm disappointed.
>
>> So this has been working. The practical difficulty is that at least
>> one LO developer refuses to share their security patches with Apache
>> under the ALv2. So our primary challenge has not been communications.
>
> Wow - my perception is the converse of that, let me invert your
> statement:
>
> One Apache OpenOffice developer refuses to share their security patches
> with LibreOffice under the MPL/LGPLv3+. While the AL2 license is in
> theory compatible, this is a real issue due to compliance and header
> requirements. Combine an LGPLv3-only work with a header-less AL2 patch,
> and what does the header look like ? :-) That's an expensive question to
> answer satisfactorily - and one that would be substantially eased by
> more flexibility. So - this cuts both ways.
Michael, I really don't like to blame anybody here. You should know the
truth and how the real story was. The patch was under ALv2 as our
complete source code is now, at the least the code granted by Oracle.
And the patch was offered as it is. And there was another patch that was
not shared by somebody (not from AOO) and where we have by the way found
a better fix for.
So please stop to pervert the reality. We are open for any kind of
collaboration here and we will share the information we have.
Sharing in a way that is adequate for security issues and as transparent
and open as possible for this kind of issues.
Before people start blaming against Rob, think twice about it. It is a
sensitive topic and we don't want discuss it more than necessary here on
this list. It is another attempt to show that we don't want to
collaborate but it is again not true and we are very open.
And the moment we have enough to do with our AOO project and don't take
care about other projects. But we are open for any kind of serious
collaboration at a time where we have time for it. And of course
security issue are take serious and in time from our perspective and
people involved in the security issues should have already noticed this.
Juergen
>
> On the other hand, it's a total red-herring wrt. transparent,
> simultaneous disclosure to both projects on a shared list, these are
> orthogonal issues; it is at least better to have one without the other.
>
>>> To re-iterate the status quo from the LibreOffice side: we recommend
>>> that issues are directed to a joint mailing list:
>>> officesecurity@lists.freedesktop.org that is vendor neutral,
>>> cross-project, administered by both sides, neutrally hosted etc. That
>>> helps avoid further, baseless accusations of information hiding, not
>>> sharing etc. This was built on a foundation of reciprocal treatment.
>>
>> We have in the past and will in the future continue to share
>> appropriate information with LO and other concerned parties.
>
> It is highly regrettable that you are not willing and/or able to
> reciprocate in sharing all your incoming vulnerability reports in this
> way, as we have done. Is this something that the Apache OpenOffice
> project has decided to do, or is this your decision ?
>
>> Your freedesktop list is one way to share information more broadly,
>> when needed. In fact we've used it for that purpose recently, yes?
>
> We have a private security mailing list that should suffice for this
> purpose. Indeed - having a project-neutral, vendor neutral, neutrally
> administered list elsewhere is more work.
>
>> Is the above clear? If not, please ask questions.
>
> * Do you commit to -immediately- forward any externally reported
> security vulnerabilities vs. OO.o to the LibreOffice project ?
>
> * If so - why not do this by advertising a cross-project
> shared security list, following our example ?
>
> * If not, why not ?& who does the forwarding& when ?
>
> All the best,
>
> Michael.
>
Re: Shutdown of the securityteam@openoffice.org mailing
Posted by Michael Meeks <mi...@suse.com>.
Hi Rob,
On Mon, 2012-03-19 at 08:11 -0400, Rob Weir wrote:
> We've discussed this all before, but to reiterate, the previous list
> was a security list for a single open source project. It was hosted by
> that open source project. I'm not seeing in what sense that was
> neutral.
It was project-neutral, it included LibreOffice and Apache OpenOffice,
and Symphony developers and distributors.
> > a) will the composition of this list remain the same, or
> > will it change to exclude non Apache-committers ? or is
> > this cross-project list simply gone ?
>
> The list subscribers consists of a subset of AOO committers as well
> the Apache Security Team. As with all private lists, any Apache
> Member is also able to subscribe or view the list archives.
So I'll take that as: the previous project-neutral list being killed,
and being replaced with an Apache OpenOffice specific list. That is
indeed an unfortunate development worth noticing.
> I> b) in the light of a) will Apache OpenOffice be recommending
> > reports be made exclusively to this address ?
>
> You can see our security guidelines here:
> http://incubator.apache.org/openofficeorg/security.html
And you can contrast with ours here:
http://www.libreoffice.org/advisories/
"The security teams for products associated with the code-base
can be contacted at officesecurity@lists.freedesktop.org, this
includes representatives of many vendors, and associated
projects."
> Note: this has been our policy for several months, and in that time
> we've been open with LO on sharing reports, analysis and even patches.
That is interesting. I had imagined that you would continue to direct
security bugs to the cross-project list, given your enthusiasm for that
being -the- list to send reports to. I must admit I'm disappointed.
> So this has been working. The practical difficulty is that at least
> one LO developer refuses to share their security patches with Apache
> under the ALv2. So our primary challenge has not been communications.
Wow - my perception is the converse of that, let me invert your
statement:
One Apache OpenOffice developer refuses to share their security patches
with LibreOffice under the MPL/LGPLv3+. While the AL2 license is in
theory compatible, this is a real issue due to compliance and header
requirements. Combine an LGPLv3-only work with a header-less AL2 patch,
and what does the header look like ? :-) That's an expensive question to
answer satisfactorily - and one that would be substantially eased by
more flexibility. So - this cuts both ways.
On the other hand, it's a total red-herring wrt. transparent,
simultaneous disclosure to both projects on a shared list, these are
orthogonal issues; it is at least better to have one without the other.
> > To re-iterate the status quo from the LibreOffice side: we recommend
> > that issues are directed to a joint mailing list:
> > officesecurity@lists.freedesktop.org that is vendor neutral,
> > cross-project, administered by both sides, neutrally hosted etc. That
> > helps avoid further, baseless accusations of information hiding, not
> > sharing etc. This was built on a foundation of reciprocal treatment.
>
> We have in the past and will in the future continue to share
> appropriate information with LO and other concerned parties.
It is highly regrettable that you are not willing and/or able to
reciprocate in sharing all your incoming vulnerability reports in this
way, as we have done. Is this something that the Apache OpenOffice
project has decided to do, or is this your decision ?
> Your freedesktop list is one way to share information more broadly,
> when needed. In fact we've used it for that purpose recently, yes?
We have a private security mailing list that should suffice for this
purpose. Indeed - having a project-neutral, vendor neutral, neutrally
administered list elsewhere is more work.
> Is the above clear? If not, please ask questions.
* Do you commit to -immediately- forward any externally reported
security vulnerabilities vs. OO.o to the LibreOffice project ?
* If so - why not do this by advertising a cross-project
shared security list, following our example ?
* If not, why not ? & who does the forwarding & when ?
All the best,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Re: Shutdown of the securityteam@openoffice.org mailing
Posted by Rob Weir <ro...@apache.org>.
On Mon, Mar 19, 2012 at 7:49 AM, Michael Meeks <mi...@suse.com> wrote:
> Hi guys,
>
> The appended mail was sent to the old multi-vendor security list at
> openoffice.org recipients. That seems reasonable - the infrastructure is
> coming to an end.
>
> As previously discussed ( to death ;-) [ and I have no particular
> desire to re-opening and re-hash the issue ] this
> securityteam@openoffice.org list -used- to be the multi-vendor, neutral
> place for reporting security vulnerabilities in openoffice.org and then
> Apache OpenOffice.
>
We've discussed this all before, but to reiterate, the previous list
was a security list for a single open source project. It was hosted by
that open source project. I'm not seeing in what sense that was
neutral.
> With it's move to Apache hosting, I have a few questions:
>
> a) will the composition of this list remain the same, or
> will it change to exclude non Apache-committers ? or is
> this cross-project list simply gone ?
>
The list subscribers consists of a subset of AOO committers as well
the Apache Security Team. As with all private lists, any Apache
Member is also able to subscribe or view the list archives.
I> b) in the light of a) will Apache OpenOffice be recommending
> reports be made exclusively to this address ?
>
You can see our security guidelines here:
http://incubator.apache.org/openofficeorg/security.html
Note: this has been our policy for several months, and in that time
we've been open with LO on sharing reports, analysis and even patches.
So this has been working. The practical difficulty is that at least
one LO developer refuses to share their security patches with Apache
under the ALv2. So our primary challenge has not been communications.
> To re-iterate the status quo from the LibreOffice side: we recommend
> that issues are directed to a joint mailing list:
> officesecurity@lists.freedesktop.org that is vendor neutral,
> cross-project, administered by both sides, neutrally hosted etc. That
> helps avoid further, baseless accusations of information hiding, not
> sharing etc. This was built on a foundation of reciprocal treatment.
>
We have in the past and will in the future continue to share
appropriate information with LO and other concerned parties. Your
freedesktop list is one way to share information more broadly, when
needed. In fact we've used it for that purpose recently, yes?
> Naturally, we maintain a private, internal security list for
> LibreOffice developers to discuss fixes on in addition to that, and have
> no issue with Apache OpenOffice doing likewise of course. It would be
> good to know what the plan is from your side though.
>
Is the above clear? If not, please ask questions.
-Rob
> Thanks,
>
> Michael.
>
> [snip]
> Subject: [securityteam] Shutdown of the securityteam@openoffice.org mailing
> Date: Mon, 12 Mar 2012 16:16:48 -0400
>
> The securityteam@openoffice.org mailing list will cease operation on
> or after March 15th, 2012. This list, as well as numerous other
> legacy mailing lists, were kindly hosted by Oracle during the
> transition of OpenOffice to Apache. Now that this infrastructure
> transition is complete, the legacy lists will be retired.
>
> The new address for reporting vulnerabilities to the Apache OpenOffice
> project is : ooo-security@incubator.apache.org
>
> Instructions for submitting reports to the project can be found at
> http://security.openoffice.org
>
> If you wish to be on a notification list for public announcements of
> vulnerabilities and patches, you are invited to subscribe to our
> announcement list by sending an email to
> ooo-announce-subscribe@incubator.apache.org. We also publish
> disclosures to full-disclosure@lists.grok.org.uk and
> bugtraq@securityfocus.com.
>
> Regards,
>
> -Rob Weir, Apache OpenOffice Security Team
>
> --
> michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
>
>
> ---------- Forwarded message ----------
> From: Rob Weir <ro...@apache.org>
> To: securityteam@openoffice.org
> Cc: ooo-security@incubator.apache.org
> Date: Mon, 12 Mar 2012 16:16:48 -0400
> Subject: [securityteam] Shutdown of the securityteam@openoffice.org mailing
> The securityteam@openoffice.org mailing list will cease operation on
> or after March 15th, 2012. This list, as well as numerous other
> legacy mailing lists, were kindly hosted by Oracle during the
> transition of OpenOffice to Apache. Now that this infrastructure
> transition is complete, the legacy lists will be retired.
>
> The new address for reporting vulnerabilities to the Apache OpenOffice
> project is : ooo-security@incubator.apache.org
>
> Instructions for submitting reports to the project can be found at
> http://security.openoffice.org
>
> If you wish to be on a notification list for public announcements of
> vulnerabilities and patches, you are invited to subscribe to our
> announcement list by sending an email to
> ooo-announce-subscribe@incubator.apache.org. We also publish
> disclosures to full-disclosure@lists.grok.org.uk and
> bugtraq@securityfocus.com.
>
> Regards,
>
> -Rob Weir, Apache OpenOffice Security Team
> --
> -----------------------------------------------------------------
> To unsubscribe send email to securityteam-unsubscribe@openoffice.org
> For additional commands send email to sympa@openoffice.org
> with Subject: help
>