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

[RFC] Adding a challenge-response authentication method to git://

From
Stephen R. van den Berg <srb@cuci.nl>
Date
Aug 13, 2008, 16:26 UTC
Message-ID
<20080813162644.GC12200@cuci.nl>

What are the opinions on adding a basic challenge-response type authentication mechanism to the native git protocol? I.e. the authentication would be a simple one, which uses SHA1 (surprise ;-) to actually encrypt username/password/salt and authenticate the user.

I'm willing to do the work, if there are no objections.
-- 
Sincerely,
           Stephen R. van den Berg.

"And now for something *completely* different!"
Next: Petr Baudis
Message 1 of 18 in “[RFC] Adding a challenge-response authentication method to git://”
  1. Stephen R. van den BergAug 13, 2008
  2. Petr BaudisAug 13, 2008
  3. David BrownAug 14, 2008
  4. Petr BaudisAug 14, 2008
  5. Stephen R. van den BergAug 14, 2008
  6. Petr BaudisAug 14, 2008
  7. Stephen R. van den BergAug 14, 2008
  8. Shawn O. PearceAug 13, 2008
  9. Stephen R. van den BergAug 13, 2008
  10. Shawn O. PearceAug 13, 2008
  11. Stephen R. van den BergAug 14, 2008
  12. Shawn O. PearceAug 14, 2008
  13. Stephen R. van den BergAug 14, 2008
  14. Andreas EricssonAug 14, 2008
  15. Stephen R. van den BergAug 14, 2008
  16. david@lang.hmAug 14, 2008
  17. david@lang.hmAug 14, 2008
  18. Shawn O. PearceAug 14, 2008

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.