On 01/03/18 02:59, Echo Wang wrote:
>>
>> 1) [email protected]
> 
> 
> +1

With my mentor hat on:

No.

All security vulnerability reports need to be visible to the ASF
security team and if they are reported directly to the private@ list
that doesn't happen.

The podling needs to choose which of the following addresses it wishes
to publish for security reports and then make sure that the chosen
address is clearly signposted:

1. [email protected]
2. [email protected]

If the podling chooses the first, the podling will need to request that
that list is set up by INFRA. All security@<project>.apache.org lists
are automatically copied to the ASF security team.

If the podling chooses [email protected] (the ASF wide security address),
that team will then forward reports to [email protected]

Now is probably also a good time for the project community to review the
security vulnerability handling process:

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

Mark

Reply via email to