Bug 215890 - www/h2o: add CPE information
Summary: www/h2o: add CPE information
Status: Closed DUPLICATE of bug 217088
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 23:41 UTC by shun
Modified: 2017-03-06 10:14 UTC (History)
2 users (show)

See Also:
dch: maintainer-feedback+

Attachments
adding CPE information to Makefile (316 bytes, patch)
2017-01-08 23:41 UTC, shun 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description shun 2017-01-08 23:41:51 UTC 
Created attachment 178645 [details]
adding CPE information to Makefile

www/h2o has had vulnerabilities with a CPE identifier assigned (e.g. CVE-2016-4817). This patch adds CPE information as suggested in the FreeBSD wiki[0].

[0] https://wiki.freebsd.org/Ports/CPE
Comment 1 Dave Cottlehuber freebsd_committer freebsd_triage 2017-01-17 21:58:11 UTC 
\o/ thanks! I am just preparing the 2.1.0 release for h2o so I will include
your contribution into that directly, as its a very small patch. If that's acceptable please close this PR.
Comment 2 Dave Cottlehuber freebsd_committer freebsd_triage 2017-01-17 22:00:31 UTC 
BTW cpe database seems a bit out of date - https://web.nvd.nist.gov/view/cpe/search/results?keyword=h2o&status=FINAL&orderBy=CPEURI&namingFormat=2.3 so I hope this doesn't confuse people. I have tried to keep security/vuxml 100% complete so that should be found in `pkg audit` and friends.
Comment 3 Dave Cottlehuber freebsd_committer freebsd_triage 2017-02-14 14:03:58 UTC 
thanks shun@ I added PR#217088 which has your cpe patch in it. If you want your patch credit details in that PR amended, please comment over there. I think we can close this PR now.
Comment 4 Wen Heping freebsd_committer freebsd_triage 2017-03-06 10:14:49 UTC 

*** This bug has been marked as a duplicate of bug 217088 ***