Implementing authenticated Smart HTTP - which URLs to secure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Howdy!

I'd like to implement HTTP authentication for Git Smart HTTP using Dulwich (a Python binding):

1) read-only if unauthenticated and write only if authenticated
2) read/write only if authenticated

I couldn't find any documentation on which URLs need be secured and what response codes are expected in case the cloner/pusher is unauthenticated.

Is there any documentation on Smart HTTP workflow? The C sources (vanilla Git and libgit2) didn't help me too much since I found it very difficult to follow the code-flow... it's probably just abstracted too well :-)

Thanks!
Jonas
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]