Fossil SCM

Fix typo on the [/doc/tip/www/password.wiki] page. Add a link to that page from the home page.

drh 2010-01-12 14:33 trunk
Commit c16017374e4318ade54ee0c1e269a0bc2ddde355
--- www/index.wiki
+++ www/index.wiki
@@ -117,10 +117,11 @@
117117
[http://www.mail-archive.com/[email protected] | archives]
118118
available for discussing fossil issues.
119119
* [./stats.wiki | Performance statistics] taken from real-world projects
120120
hosted on fossil.
121121
* How to [./shunning.wiki | delete content] from a fossil repository.
122
+ * How Fossil does [./password.wiki | password management].
122123
* Some (unfinished but expanding) extended
123124
[./reference.wiki | reference documentation] for the fossil command line.
124125
* Documentation on the
125126
[http://www.sqliteconcepts.org/THManual.pdf | TH1 Script Language] used
126127
to configure the ticketing subsystem.
127128
--- www/index.wiki
+++ www/index.wiki
@@ -117,10 +117,11 @@
117 [http://www.mail-archive.com/[email protected] | archives]
118 available for discussing fossil issues.
119 * [./stats.wiki | Performance statistics] taken from real-world projects
120 hosted on fossil.
121 * How to [./shunning.wiki | delete content] from a fossil repository.
 
122 * Some (unfinished but expanding) extended
123 [./reference.wiki | reference documentation] for the fossil command line.
124 * Documentation on the
125 [http://www.sqliteconcepts.org/THManual.pdf | TH1 Script Language] used
126 to configure the ticketing subsystem.
127
--- www/index.wiki
+++ www/index.wiki
@@ -117,10 +117,11 @@
117 [http://www.mail-archive.com/[email protected] | archives]
118 available for discussing fossil issues.
119 * [./stats.wiki | Performance statistics] taken from real-world projects
120 hosted on fossil.
121 * How to [./shunning.wiki | delete content] from a fossil repository.
122 * How Fossil does [./password.wiki | password management].
123 * Some (unfinished but expanding) extended
124 [./reference.wiki | reference documentation] for the fossil command line.
125 * Documentation on the
126 [http://www.sqliteconcepts.org/THManual.pdf | TH1 Script Language] used
127 to configure the ticketing subsystem.
128
--- www/password.wiki
+++ www/password.wiki
@@ -62,11 +62,11 @@
6262
essentially ignored for the special users named "anonymous", "developer",
6363
"reader", and "nobody". It is not possible to authenticate as users
6464
"developer", "reader", or "nobody" and the authentication protocol
6565
for "anonymous" use one-time captchas not persistent passwords.
6666
67
-<h2>Web Interface Authtentication</h2>
67
+<h2>Web Interface Authentication</h2>
6868
6969
When a user logs into Fossil using the web interface, the login name
7070
and password are sent in the clear to the server. The server then
7171
hashes the password and compares it against the value stored in USER.PW.
7272
If they match, the server sets a cookie on the client to record the
7373
--- www/password.wiki
+++ www/password.wiki
@@ -62,11 +62,11 @@
62 essentially ignored for the special users named "anonymous", "developer",
63 "reader", and "nobody". It is not possible to authenticate as users
64 "developer", "reader", or "nobody" and the authentication protocol
65 for "anonymous" use one-time captchas not persistent passwords.
66
67 <h2>Web Interface Authtentication</h2>
68
69 When a user logs into Fossil using the web interface, the login name
70 and password are sent in the clear to the server. The server then
71 hashes the password and compares it against the value stored in USER.PW.
72 If they match, the server sets a cookie on the client to record the
73
--- www/password.wiki
+++ www/password.wiki
@@ -62,11 +62,11 @@
62 essentially ignored for the special users named "anonymous", "developer",
63 "reader", and "nobody". It is not possible to authenticate as users
64 "developer", "reader", or "nobody" and the authentication protocol
65 for "anonymous" use one-time captchas not persistent passwords.
66
67 <h2>Web Interface Authentication</h2>
68
69 When a user logs into Fossil using the web interface, the login name
70 and password are sent in the clear to the server. The server then
71 hashes the password and compares it against the value stored in USER.PW.
72 If they match, the server sets a cookie on the client to record the
73

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button