#845 closed defect (fixed)
Document how to generate htdigest file without Apache
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | 0.9 |
Component: | web frontend/tracd | Version: | 0.7.1 |
Severity: | minor | Keywords: | documentation |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
tracd.README does not explain how to generate htdigest file.
It would be worth describing how to generate htdigest file. Especially for people working on Win32 not familiar with configuring Apache.
I ended up using following from Python prompt:
usr = 'usrname'; realm = 'trac'; passwrd = 'secret' kd = lambda x: md5.md5(':'.join(x)).hexdigest() usr = 'usrname'; realm = 'trac'; passwrd = 'secret' ':'.join((usr, realm, kd([usr, realm, passwrd]))) 'usrname:trac:41772e81f3dc44f35efd2de45cf9a4d3'
And pasting the result into htdigest file. Unfortunately I have spent half a day reading tracd source and RFC 2617 trying to understand what is expected. To add insult to injury I have later found out I could have used htdigest if I had Apache installed but that is what I was trying to avoid in the first place.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
Keywords: | documentation added |
---|
comment:2 by , 19 years ago
comment:3 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Okay, closing since it is now in the documentation.
comment:4 by , 18 years ago
Milestone: | → 0.9 |
---|
(setting the milestone as 0.9 as it seems the script was included by that time.)
I have just added a modified version of this code to TracStandalone, so you can probably close this ticket now :-)