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

Re: User authentication in GIT

From
Ssupadhyay <supadhyay@imany.com>
Date
Feb 7, 2012, 11:47 UTC
Message-ID
<1328615262741-7262113.post@n2.nabble.com>
In-Reply-To
<1328595129258-7261349.post@n2.nabble.com>
Hi Robin and Jakub,

Thanks for your reply. But I am still not getting what exactly I need to perform on GIT server. Please find my reply on your suggestion below:

Robin: All users must have their own SSH key. You do not create keys for them. My rely: can you please give some more idea about how it works.. I am not getting this or if you can provide any link for this to understand.

Jakub: My reply: existing version control system used pserver protocol.

You would still need for each user to generate their own SSH key. My reply: Do I need to store all end users sSH key in .ssh/authorized_keys file on GIT server?

-- View this message in context: http://git.661346.n2.nabble.com/User-authentication-in-GIT-tp7261349p7262113.html Sent from the git mailing list archive at Nabble.com.

Previous: Jakub NarebskiNext: compufreak
Message 4 of 13 in “User authentication in GIT”
  1. supadhyayFeb 7, 2012
  2. Robin H. JohnsonFeb 7, 2012
  3. Jakub NarebskiFeb 7, 2012
  4. supadhyayFeb 7, 2012
  5. compufreakFeb 7, 2012
  6. Johan HerlandFeb 7, 2012
  7. supadhyayFeb 7, 2012
  8. Sitaram ChamartyFeb 7, 2012
  9. supadhyayFeb 10, 2012
  10. Sitaram ChamartyFeb 11, 2012
  11. supadhyayFeb 13, 2012
  12. Sitaram ChamartyFeb 13, 2012
  13. supadhyayFeb 13, 2012

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.