[jira] [Commented] (KAFKA-3709) Create project security page
[ https://issues.apache.org/jira/browse/KAFKA-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297978#comment-15297978 ] ASF GitHub Bot commented on KAFKA-3709: --- Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/12 > Create project security page > > > Key: KAFKA-3709 > URL: https://issues.apache.org/jira/browse/KAFKA-3709 > Project: Kafka > Issue Type: Improvement > Components: website >Reporter: Flavio Junqueira >Assignee: Flavio Junqueira > > We are creating a security@k.a.o mailing list to receive reports of potential > vulnerabilities. Now that Kafka has security in place, the community might > starts receiving vulnerability reports and we need to follow the guidelines > here: > http://www.apache.org/security/ > Specifically, security issues are better handled in a project-specific list. > This jira is to create a web page that informs users and contributors of how > we are supposed to handle security issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-3709) Create project security page
[ https://issues.apache.org/jira/browse/KAFKA-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297378#comment-15297378 ] ASF GitHub Bot commented on KAFKA-3709: --- Github user ijuma commented on the pull request: https://github.com/apache/kafka-site/pull/12#issuecomment-221129684 Thanks Jun. I emailed active committers informing them about the creation of the mailing list. I sent an email to the list from a different account and verified that messages are going through. I'll merge this PR tomorrow morning if there are no objections. > Create project security page > > > Key: KAFKA-3709 > URL: https://issues.apache.org/jira/browse/KAFKA-3709 > Project: Kafka > Issue Type: Improvement > Components: website >Reporter: Flavio Junqueira >Assignee: Flavio Junqueira > > We are creating a security@k.a.o mailing list to receive reports of potential > vulnerabilities. Now that Kafka has security in place, the community might > starts receiving vulnerability reports and we need to follow the guidelines > here: > http://www.apache.org/security/ > Specifically, security issues are better handled in a project-specific list. > This jira is to create a web page that informs users and contributors of how > we are supposed to handle security issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-3709) Create project security page
[ https://issues.apache.org/jira/browse/KAFKA-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295087#comment-15295087 ] ASF GitHub Bot commented on KAFKA-3709: --- Github user junrao commented on the pull request: https://github.com/apache/kafka-site/pull/12#issuecomment-220784809 The mailing list has been created. We can invite all committers/contributors who are interested in security to join the list. secur...@kafka.apache.org Moderators: jun...@gmail.com,ism...@juma.me.uk,csh...@gmail.com This list is private. > Create project security page > > > Key: KAFKA-3709 > URL: https://issues.apache.org/jira/browse/KAFKA-3709 > Project: Kafka > Issue Type: Improvement > Components: website >Reporter: Flavio Junqueira >Assignee: Flavio Junqueira > > We are creating a security@k.a.o mailing list to receive reports of potential > vulnerabilities. Now that Kafka has security in place, the community might > starts receiving vulnerability reports and we need to follow the guidelines > here: > http://www.apache.org/security/ > Specifically, security issues are better handled in a project-specific list. > This jira is to create a web page that informs users and contributors of how > we are supposed to handle security issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
