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

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

From
Shawn O. Pearce <spearce@spearce.org>
Date
Aug 13, 2008, 16:40 UTC
Message-ID
<20080813164038.GE3782@spearce.org>
In-Reply-To
<20080813162644.GC12200@cuci.nl>
"Stephen R. van den Berg" <srb@cuci.nl> wrote:
Show 7 quoted lines
> 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.

Last time we talked about this we got off onto some tagent about using GnuPG public keys to authenticate users, and then how we might store the public keys in a keyring and log pushes (changes to refs) so that one could replicate the log on another server and come up with the same result. Hence not just the current source code but also the "how we got here" could be verified externally.

Username/password management is always ugly. Some admins will want you to plug into PAM, others just want a flat file that is unique to the service, others want LDAP. And then you get into people wanting Kerberos support because they already have everything else in their domain supporting it. Tons of complexity for our project.

Isn't there some authentication frontend that some IMAP servers use to handle the authentication for them? I think last time I setup bincimap it used checkpassword. We might want to do the same if we are going down this road...

-- 
Shawn.
Previous: Stephen R. van den BergNext: Stephen R. van den Berg
Message 8 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.