Documentation bug in ProGit v2

[Hugo Connery <hmco@env.dtu.dk>]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

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,


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]