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

Re: [PATCH] Implement https public key pinning

From
Daniel Stenberg <daniel@haxx.se>
Date
Feb 11, 2016, 23:30 UTC
Message-ID
<alpine.DEB.2.20.1602120030120.5268@tvnag.unkk.fr>
In-Reply-To
<20160211225437.GA33955@mitoraj.siccegge.de>
On Thu, 11 Feb 2016, Christoph Egger wrote:
> +#if LIBCURL_VERSION_NUM >= 0x074400
That should probably be 0x072c00 ...
-- 
  / daniel.haxx.se
Previous: Christoph EggerNext: Christoph Egger
Message 2 of 16 in “Implement https public key pinning”
  1. Implement https public key pinningChristoph Egger, Feb 11, 2016
  2. Daniel StenbergFeb 11, 2016
  3. Christoph EggerFeb 12, 2016
  4. Implement https public key pinningChristoph Egger, Feb 12, 2016
  5. Thomas GummererFeb 12, 2016
  6. Jeff KingFeb 12, 2016
  7. Christoph EggerFeb 15, 2016
  8. Implement https public key pinningChristoph Egger, Feb 15, 2016
  9. Junio C HamanoFeb 15, 2016
  10. Jeff KingFeb 16, 2016
  11. Junio C HamanoFeb 16, 2016
  12. Jeff KingFeb 16, 2016
  13. Implement https public key pinningChristoph Egger, Feb 16, 2016
  14. Junio C HamanoFeb 16, 2016
  15. Junio C HamanoFeb 17, 2016
  16. Christoph EggerFeb 22, 2016

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.