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

Documentation bug in ProGit v2

From
HCHugo Connery <hmco@env.dtu.dk>
Date
Jul 31, 2015, 10:13 UTC
Message-ID
<55BB4A52.2060404@env.dtu.dk>
Hi,
When discussing establishing git over Smart HTTP on pages 140 and 141:

[quote] Finally you’ll want to make writes be authenticated somehow, possibly with an Auth block like this:

<LocationMatch "^/git/.*/git-receive-pack$"> AuthType Basic 140GitWeb AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user </LocationMatch>

That will require you to create a .htaccess file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file:

$ htdigest -c /opt/git/.htpasswd "Git Access" schacon [end quote]

This will 401 every time.  You either do:

AuthType Digest and use htdigest, or you do AuthType Basic and use htpasswd

Apache recommend Basic + SSL rather than Digest.
Thanks for the book.

Regards, Hugo Connery -- Head of IT, Department of Environmental Engineering Technical University of Denmark,

Message 1 of 1 in “Documentation bug in ProGit v2”
  1. Hugo ConneryJul 31, 2015

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.