You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Main Uddin (JIRA)" <ji...@apache.org> on 2012/10/11 06:01:03 UTC
[jira] [Created] (TS-1519) How the Apache HTTP web server stays
secure
Main Uddin created TS-1519:
------------------------------
Summary: How the Apache HTTP web server stays secure
Key: TS-1519
URL: https://issues.apache.org/jira/browse/TS-1519
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Affects Versions: Doc 3.2
Environment: How Apache works internally with security
Reporter: Main Uddin
Priority: Minor
Fix For: Doc 3.2
depending on whether the project can reproduce the reported vulnerability, the security team can help put together a response to the security researcher (usually the person or organization reporting the vulnerability). Bill explained: “We say to them, hey, in our next release, we will have a fix, and would you embargo the release until that particular point, and here’s the time frame
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1519) How the Apache HTTP web server stays
secure
Posted by "James Peach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473823#comment-13473823 ]
James Peach commented on TS-1519:
---------------------------------
We follow the Apache security policy, see http://www.apache.org/security/.
This bug tracker is for reporting bugs and requesting software changes. If you would like to discuss security policy, then the mailing list is the right place for that, users@trafficserver.apache.org.
> How the Apache HTTP web server stays secure
> -------------------------------------------
>
> Key: TS-1519
> URL: https://issues.apache.org/jira/browse/TS-1519
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
> Affects Versions: Doc 3.2
> Environment: How Apache works internally with security
> Reporter: Main Uddin
> Priority: Minor
> Labels: loadbalancer
> Fix For: Doc 3.2
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> depending on whether the project can reproduce the reported vulnerability, the security team can help put together a response to the security researcher (usually the person or organization reporting the vulnerability). Bill explained: “We say to them, hey, in our next release, we will have a fix, and would you embargo the release until that particular point, and here’s the time frame
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1519) How the Apache HTTP web server stays
secure
Posted by "James Peach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach resolved TS-1519.
-----------------------------
Resolution: Invalid
Closing; not a bug.
> How the Apache HTTP web server stays secure
> -------------------------------------------
>
> Key: TS-1519
> URL: https://issues.apache.org/jira/browse/TS-1519
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
> Affects Versions: Doc 3.2
> Environment: How Apache works internally with security
> Reporter: Main Uddin
> Priority: Minor
> Labels: loadbalancer
> Fix For: Doc 3.2
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> depending on whether the project can reproduce the reported vulnerability, the security team can help put together a response to the security researcher (usually the person or organization reporting the vulnerability). Bill explained: “We say to them, hey, in our next release, we will have a fix, and would you embargo the release until that particular point, and here’s the time frame
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira