RĂ¼diger, you are also probably looking at this. Who runs he shell scripts to 
generate the mds? It seems we need to do that on changing the cves?

Also, the converter script stumbles on CVEs without "timeline".

Are you on it or should I?

> Am 16.09.2021 um 14:17 schrieb ste...@eissing.org:
> 
> 
> 
>> Am 16.09.2021 um 14:14 schrieb ste...@eissing.org:
>> 
>>> 
>>> Am 16.09.2021 um 14:04 schrieb Ruediger Pluem <rpl...@apache.org>:
>>> 
>>> 
>>> 
>>> On 9/16/21 12:33 PM, ic...@apache.org wrote:
>>>> This is an automated email from the ASF dual-hosted git repository.
>>>> 
>>>> icing pushed a commit to branch main
>>>> in repository https://gitbox.apache.org/repos/asf/httpd-site.git
>>>> 
>>>> 
>>>> The following commit(s) were added to refs/heads/main by this push:
>>>>   new 51476c4  publishing release httpd-2.4.49
>>>> 51476c4 is described below
>>>> 
>>>> commit 51476c4d2261ea5b68951054a50c08a249ea1306
>>>> Author: Stefan Eissing <stefan.eiss...@greenbytes.de>
>>>> AuthorDate: Thu Sep 16 09:58:23 2021 +0200
>>>> 
>>>>  publishing release httpd-2.4.49
>>>> ---
>>>> content/doap.rdf    |  4 ++--
>>>> content/download.md | 24 ++++++++++++------------
>>>> content/index.md    |  6 +++---
>>>> 3 files changed, 17 insertions(+), 17 deletions(-)
>>> 
>>> The vulnerabilties page is not updated yet. I guess this can be fixed by 
>>> copying the respective json files
>>> to https://github.com/apache/httpd-site/tree/main/content/security/json
>>> Does https://cveprocess.apache.org/ provide any RESTFUL API to extract the 
>>> JSON from the tool such that this can be scripted?
>> 
>> With links such as these it looks unguessable
>> 
>> blob:https://cveprocess.apache.org/3c51c80b-1d31-403a-9d1d-95c928f91574
>> 
>> (involuntarily learning about 'blob:' url schemes...aaahhhhh!)
> 
> And analyzing the page, the JSON data is embedded in the Javascript embedded 
> in the HTML. Hmm...
> 
>> 
>>> 
>>> Regards
>>> 
>>> RĂ¼diger

Reply via email to