git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[Question] Documenting platform implications on CVE to git

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Oct 6, 2017, 13:28 UTC
Message-ID
<000801d33ea7$04a7c240$0df746c0$@nexbridge.com>
Hi All,

I wonder whether there is some mechanism for providing official responses from platform ports relating to security CVE reports, like CVE-2017-14867. For example, the Perl implementation on HPE NonStop does not include the SCM module so commands relating cvsserver may not be available - one thing to be verified so is a question #1. But the real question (#2) is: where would one most appropriately document issues like this to be consistent with other platform responses relating to git?

Thanks, Randall

-- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400)/NonStop(211288444200000000) -- In my real life, I talk too much.

Next: Jonathan Nieder
Message 1 of 5 in “[Question] Documenting platform implications on CVE to git”
  1. Randall S. BeckerOct 6, 2017
  2. Jonathan NiederOct 6, 2017
  3. Randall S. BeckerOct 6, 2017
  4. Jonathan NiederOct 6, 2017
  5. Randall S. BeckerOct 7, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.