Fossil SCM

Merged caps-doc branch down to trunk, improving documentation of user capabilities in Fossil.

wyoung 2019-09-04 00:58 trunk merge
Commit 779ddefa190931fd55d5df2d2467632aa0df69bef74294e9b322e1c950f98c45
Parent c5561039e1fffe3…
21 files changed +1 -1 +1 -1 -6 +15 -9 +21 -24 +8 -5 +9 +64 +39 +6 +35 +5 -5 +1 -1 +1 -1 +1 -1 +34 -66 +4 -5 +4 -1 +16 -7 +5 -5 +2 -2
~ src/capabilities.c ~ src/main.c - www/admin-v-setup.md ~ www/alerts.md ~ www/antibot.wiki ~ www/caps/admin-v-setup.md + www/caps/admin-v-setup.md ~ www/caps/impl.md ~ www/caps/index.md ~ www/caps/login-groups.md ~ www/caps/ref.html ~ www/cgi.wiki ~ www/custom_ticket.wiki ~ www/defcsp.md ~ www/defcsp.md ~ www/forum.wiki ~ www/fossil-v-git.wiki ~ www/mkindex.tcl ~ www/permutedindex.html ~ www/server/index.html ~ www/serverext.wiki
M src/capabilities.c
+1 -1
--- src/capabilities.c
+++ src/capabilities.c
@@ -297,11 +297,11 @@
297297
 { '4', CAPCLASS_FORUM, 0,
298298
 "Forum-Trusted", "Create forum messages that bypass moderation" },
299299
 { '5', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
300300
 "Forum-Mod", "Moderator for forum messages" },
301301
 { '6', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
302
- "Forum-Admin", "Set or remove capability '4' from other users" },
302
+ "Forum-Admin", "Grant capability '4' to other users" },
303303
 { '7', CAPCLASS_ALERT, 0,
304304
 "Alerts", "Sign up for email alerts" },
305305
 { 'A', CAPCLASS_ALERT|CAPCLASS_SUPER, 0,
306306
 "Announce", "Send announcements to all subscribers" },
307307
 { 'D', CAPCLASS_OTHER, 0,
308308
--- src/capabilities.c
+++ src/capabilities.c
@@ -297,11 +297,11 @@
297 { '4', CAPCLASS_FORUM, 0,
298 "Forum-Trusted", "Create forum messages that bypass moderation" },
299 { '5', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
300 "Forum-Mod", "Moderator for forum messages" },
301 { '6', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
302 "Forum-Admin", "Set or remove capability '4' from other users" },
303 { '7', CAPCLASS_ALERT, 0,
304 "Alerts", "Sign up for email alerts" },
305 { 'A', CAPCLASS_ALERT|CAPCLASS_SUPER, 0,
306 "Announce", "Send announcements to all subscribers" },
307 { 'D', CAPCLASS_OTHER, 0,
308
--- src/capabilities.c
+++ src/capabilities.c
@@ -297,11 +297,11 @@
297 { '4', CAPCLASS_FORUM, 0,
298 "Forum-Trusted", "Create forum messages that bypass moderation" },
299 { '5', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
300 "Forum-Mod", "Moderator for forum messages" },
301 { '6', CAPCLASS_FORUM|CAPCLASS_SUPER, 0,
302 "Forum-Admin", "Grant capability '4' to other users" },
303 { '7', CAPCLASS_ALERT, 0,
304 "Alerts", "Sign up for email alerts" },
305 { 'A', CAPCLASS_ALERT|CAPCLASS_SUPER, 0,
306 "Announce", "Send announcements to all subscribers" },
307 { 'D', CAPCLASS_OTHER, 0,
308
M src/main.c
+1 -1
--- src/main.c
+++ src/main.c
@@ -105,11 +105,11 @@
105105
 char WrUnver; /* y: can push unversioned content */
106106
 char RdForum; /* 2: Read forum posts */
107107
 char WrForum; /* 3: Create new forum posts */
108108
 char WrTForum; /* 4: Post to forums not subject to moderation */
109109
 char ModForum; /* 5: Moderate (approve or reject) forum posts */
110
- char AdminForum; /* 6: Set or remove capability 4 on other users */
110
+ char AdminForum; /* 6: Grant capability 4 to other users */
111111
 char EmailAlert; /* 7: Sign up for email notifications */
112112
 char Announce; /* A: Send announcements */
113113
 char Debug; /* D: show extra Fossil debugging features */
114114
 /* These last two are included to block infinite recursion */
115115
 char XReader; /* u: Inherit all privileges of "reader" */
116116
117117
DELETED www/admin-v-setup.md
--- src/main.c
+++ src/main.c
@@ -105,11 +105,11 @@
105 char WrUnver; /* y: can push unversioned content */
106 char RdForum; /* 2: Read forum posts */
107 char WrForum; /* 3: Create new forum posts */
108 char WrTForum; /* 4: Post to forums not subject to moderation */
109 char ModForum; /* 5: Moderate (approve or reject) forum posts */
110 char AdminForum; /* 6: Set or remove capability 4 on other users */
111 char EmailAlert; /* 7: Sign up for email notifications */
112 char Announce; /* A: Send announcements */
113 char Debug; /* D: show extra Fossil debugging features */
114 /* These last two are included to block infinite recursion */
115 char XReader; /* u: Inherit all privileges of "reader" */
116
117 ELETED www/admin-v-setup.md
--- src/main.c
+++ src/main.c
@@ -105,11 +105,11 @@
105 char WrUnver; /* y: can push unversioned content */
106 char RdForum; /* 2: Read forum posts */
107 char WrForum; /* 3: Create new forum posts */
108 char WrTForum; /* 4: Post to forums not subject to moderation */
109 char ModForum; /* 5: Moderate (approve or reject) forum posts */
110 char AdminForum; /* 6: Grant capability 4 to other users */
111 char EmailAlert; /* 7: Sign up for email notifications */
112 char Announce; /* A: Send announcements */
113 char Debug; /* D: show extra Fossil debugging features */
114 /* These last two are included to block infinite recursion */
115 char XReader; /* u: Inherit all privileges of "reader" */
116
117 ELETED www/admin-v-setup.md
D www/admin-v-setup.md
-6
--- a/www/admin-v-setup.md
+++ b/www/admin-v-setup.md
@@ -1,6 +0,0 @@
1
-# The Differences Between theilitiestween Sthe power hierarcKeep Several of the Fossil user capabilities form a clear power hierarchy.
2
-Mathematically speaking:
3
-
4
-> *Setup > Admin > Moderator > User > Subsc# The Differences Betw
5
-o@3x,g@4j,j@5O,rE@6z,2rO@yg,7:[ucap]:W@3ln,G:setup_ucap_list
6
-12p~Gn;
--- a/www/admin-v-setup.md
+++ b/www/admin-v-setup.md
@@ -1,6 +0,0 @@
1 # The Differences Between theilitiestween Sthe power hierarcKeep Several of the Fossil user capabilities form a clear power hierarchy.
2 Mathematically speaking:
3
4 > *Setup > Admin > Moderator > User > Subsc# The Differences Betw
5 o@3x,g@4j,j@5O,rE@6z,2rO@yg,7:[ucap]:W@3ln,G:setup_ucap_list
6 12p~Gn;
--- a/www/admin-v-setup.md
+++ b/www/admin-v-setup.md
@@ -1,6 +0,0 @@
 
 
 
 
 
 
M www/alerts.md
+15 -9
--- www/alerts.md
+++ www/alerts.md
@@ -30,11 +30,11 @@
3030
3131
 Much of this document describes how to set up Fossil's email alert
3232
 system. To follow this guide, you will need a Fossil UI browser window
3333
 open to the [Admin → Notification](/setup_notification) Fossil UI screen
3434
 on the Fossil server that will be sending these email alerts, logged
35
-in as a user with Admin capability. It is not possible to work on a
35
+in as a user with [**Admin** capability](./caps/ref.html#a). It is not possible to work on a
3636
 clone of the server's repository and push the configuration changes up
3737
 to that repo as an Admin user, [on purpose](#backup).
3838
3939
 **Important:** Do not confuse that screen with Admin → Email-Server,
4040
 which sets up a different subsystem within Fossil. That feature is
@@ -160,11 +160,12 @@
160160
 <blockquote>
161161
 Use a different login with greater privilege than FOO to access
162162
 /subscribe
163163
 </blockquote>
164164
165
-...then the repository's administrator forgot to [give the Alerts capability](#cap7)
165
+...then the repository's administrator forgot to give the
166
+[**EmailAlert** capability][cap7]
166167
 to that user or to a user category that the user is a member of.
167168
168169
 After a subscriber signs up for alerts for the first time, a single
169170
 verification email is sent to that subscriber's given email address.
170171
 The new subscriber must click a link in that email in order to activate
@@ -188,10 +189,12 @@
188189
 settings by visiting the `/alerts` page on the repository. With the
189190
 default skin, you can get there by clicking the "Logout" link in the
190191
 upper right corner of any Fossil UI page then clicking the "Email
191192
 Alerts" link. That link is also available via the Sitemap (`/sitemap`)
192193
 and via the default skin's hamburger menu (&#9776;).
194
+
195
+[cap7]: ./caps/ref.html#7
193196
194197
195198
 <a id="unsub" name="unsubscribe"></a>
196199
 ### Unsubscribing
197200
@@ -223,24 +226,27 @@
223226
 Checklist][cl], right? Right.
224227
225228
 [cl]: https://sendgrid.com/blog/programming-style-guide-checklist/
226229
227230
228
-<a id="cap7"></a>
231
+<a id="cap7" name="ucap"></a>
229232
 ### User Capabilities
230233
231
-Once email alerts are working, one must also adjust user permissions to
232
-allow users to subscribe to email alerts. In the capability list for
233
-each user on the Admin → Users page is a new capability called "Email
234
-Alerts". The corresponding capability letter is "7", which you must
235
-give to any user that needs to use the subscription setup pages,
236
-`/subscribe` and `/alerts`.
234
+Once email alerts are working, you may need to [adjust the default user
235
+capabilities](./caps/) to give "[Email Alerts][cap7]" capability to any
236
+[user category](./caps/#ucat) or [individual user](./caps/#ucap) that
237
+needs to use the subscription setup pages, `/subscribe` and `/alerts`.
238
+[**Admin**][capa] and [**Setup**][caps] users always have this
239
+capability.
237240
238241
 To allow any passer-by on the Internet to subscribe, give the "Email
239242
 Alerts" capability to the "nobody" user category. To require that a
240243
 person solve a simple CAPTCHA first, give that capability to the
241244
 "anonymous" user category instead.
245
+
246
+[capa]: ./caps/ref.html#a
247
+[caps]: ./caps/ref.html#s
242248
243249
244250
 <a id="first" name="frist"></a>
245251
 ### First Post
246252
247253
--- www/alerts.md
+++ www/alerts.md
@@ -30,11 +30,11 @@
30
31 Much of this document describes how to set up Fossil's email alert
32 system. To follow this guide, you will need a Fossil UI browser window
33 open to the [Admin → Notification](/setup_notification) Fossil UI screen
34 on the Fossil server that will be sending these email alerts, logged
35 in as a user with Admin capability. It is not possible to work on a
36 clone of the server's repository and push the configuration changes up
37 to that repo as an Admin user, [on purpose](#backup).
38
39 **Important:** Do not confuse that screen with Admin → Email-Server,
40 which sets up a different subsystem within Fossil. That feature is
@@ -160,11 +160,12 @@
160 <blockquote>
161 Use a different login with greater privilege than FOO to access
162 /subscribe
163 </blockquote>
164
165 ...then the repository's administrator forgot to [give the Alerts capability](#cap7)
 
166 to that user or to a user category that the user is a member of.
167
168 After a subscriber signs up for alerts for the first time, a single
169 verification email is sent to that subscriber's given email address.
170 The new subscriber must click a link in that email in order to activate
@@ -188,10 +189,12 @@
188 settings by visiting the `/alerts` page on the repository. With the
189 default skin, you can get there by clicking the "Logout" link in the
190 upper right corner of any Fossil UI page then clicking the "Email
191 Alerts" link. That link is also available via the Sitemap (`/sitemap`)
192 and via the default skin's hamburger menu (&#9776;).
 
 
193
194
195 <a id="unsub" name="unsubscribe"></a>
196 ### Unsubscribing
197
@@ -223,24 +226,27 @@
223 Checklist][cl], right? Right.
224
225 [cl]: https://sendgrid.com/blog/programming-style-guide-checklist/
226
227
228 <a id="cap7"></a>
229 ### User Capabilities
230
231 Once email alerts are working, one must also adjust user permissions to
232 allow users to subscribe to email alerts. In the capability list for
233 each user on the Admin → Users page is a new capability called "Email
234 Alerts". The corresponding capability letter is "7", which you must
235 give to any user that needs to use the subscription setup pages,
236 `/subscribe` and `/alerts`.
237
238 To allow any passer-by on the Internet to subscribe, give the "Email
239 Alerts" capability to the "nobody" user category. To require that a
240 person solve a simple CAPTCHA first, give that capability to the
241 "anonymous" user category instead.
 
 
 
242
243
244 <a id="first" name="frist"></a>
245 ### First Post
246
247
--- www/alerts.md
+++ www/alerts.md
@@ -30,11 +30,11 @@
30
31 Much of this document describes how to set up Fossil's email alert
32 system. To follow this guide, you will need a Fossil UI browser window
33 open to the [Admin → Notification](/setup_notification) Fossil UI screen
34 on the Fossil server that will be sending these email alerts, logged
35 in as a user with [**Admin** capability](./caps/ref.html#a). It is not possible to work on a
36 clone of the server's repository and push the configuration changes up
37 to that repo as an Admin user, [on purpose](#backup).
38
39 **Important:** Do not confuse that screen with Admin → Email-Server,
40 which sets up a different subsystem within Fossil. That feature is
@@ -160,11 +160,12 @@
160 <blockquote>
161 Use a different login with greater privilege than FOO to access
162 /subscribe
163 </blockquote>
164
165 ...then the repository's administrator forgot to give the
166 [**EmailAlert** capability][cap7]
167 to that user or to a user category that the user is a member of.
168
169 After a subscriber signs up for alerts for the first time, a single
170 verification email is sent to that subscriber's given email address.
171 The new subscriber must click a link in that email in order to activate
@@ -188,10 +189,12 @@
189 settings by visiting the `/alerts` page on the repository. With the
190 default skin, you can get there by clicking the "Logout" link in the
191 upper right corner of any Fossil UI page then clicking the "Email
192 Alerts" link. That link is also available via the Sitemap (`/sitemap`)
193 and via the default skin's hamburger menu (&#9776;).
194
195 [cap7]: ./caps/ref.html#7
196
197
198 <a id="unsub" name="unsubscribe"></a>
199 ### Unsubscribing
200
@@ -223,24 +226,27 @@
226 Checklist][cl], right? Right.
227
228 [cl]: https://sendgrid.com/blog/programming-style-guide-checklist/
229
230
231 <a id="cap7" name="ucap"></a>
232 ### User Capabilities
233
234 Once email alerts are working, you may need to [adjust the default user
235 capabilities](./caps/) to give "[Email Alerts][cap7]" capability to any
236 [user category](./caps/#ucat) or [individual user](./caps/#ucap) that
237 needs to use the subscription setup pages, `/subscribe` and `/alerts`.
238 [**Admin**][capa] and [**Setup**][caps] users always have this
239 capability.
240
241 To allow any passer-by on the Internet to subscribe, give the "Email
242 Alerts" capability to the "nobody" user category. To require that a
243 person solve a simple CAPTCHA first, give that capability to the
244 "anonymous" user category instead.
245
246 [capa]: ./caps/ref.html#a
247 [caps]: ./caps/ref.html#s
248
249
250 <a id="first" name="frist"></a>
251 ### First Post
252
253
M www/antibot.wiki
+21 -24
--- www/antibot.wiki
+++ www/antibot.wiki
@@ -10,44 +10,41 @@
1010
 The website presented by a Fossil server is intended to be used
1111
 interactively by humans, not walked by spiders. This article
1212
 describes the techniques used by Fossil to try to welcome human
1313
 users while keeping out spiders.
1414
15
-<h2>The "hyperlink" user capability</h2>
15
+<h2>The Hyperlink User Capability</h2>
1616
1717
 Every Fossil web session has a "user". For random passers-by on the internet
1818
 (and for spiders) that user is "nobody". The "anonymous" user is also
1919
 available for humans who do not wish to identify themselves. The difference
2020
 is that "anonymous" requires a login (using a password supplied via
2121
 a CAPTCHA) whereas "nobody" does not require a login.
2222
 The site administrator can also create logins with
2323
 passwords for specific individuals.
2424
25
-The "h" or "hyperlink" capability is a permission that can be granted
26
-to users that enables the display of hyperlinks. Most of the hyperlinks
27
-generated by Fossil are suppressed if this capability is missing. So
28
-one simple defense against spiders is to disable the "h" permission for
29
-the "nobody" user. This means that users must log in (perhaps as
30
-"anonymous") before they can see any of the hyperlinks. Spiders do not
31
-normally attempt to log into websites and will therefore
32
-not see most of the hyperlinks and will not try to walk the millions of
33
-historical check-ins and diffs available on a Fossil-generated website.
34
-
35
-If the "h" capability is missing from user "nobody" but is present for
36
-user "anonymous", then a message automatically appears at the top of each
37
-page inviting the user to log in as anonymous in order to activate hyperlinks.
38
-
39
-Removing the "h" capability from user "nobody" is an effective means
40
-of preventing spiders from walking a Fossil-generated website. But
41
-it can also be annoying to humans, since it requires them to log in.
42
-Hence, Fossil provides other techniques for blocking spiders which
25
+Users without the <b>[./caps/ref.html#h | Hyperlink]</b> capability
26
+do not see most Fossil-generated hyperlinks. This is
27
+a simple defense against spiders, since [./caps/#ucat | the "nobody"
28
+user category] does not have this capability by default.
29
+Users must log in (perhaps as
30
+"anonymous") before they can see any of the hyperlinks. A spider
31
+that cannot log into your Fossil repository will be unable to walk
32
+its historical check-ins, create diffs between versions, pull zip
33
+archives, etc. by visiting links, because they aren't there.
34
+
35
+A text message appears at the top of each page in this situation to
36
+invite humans to log in as anonymous in order to activate hyperlinks.
37
+
38
+Because this required login step is annoying to some,
39
+Fossil provides other techniques for blocking spiders which
4340
 are less cumbersome to humans.
4441
45
-<h2>Automatic hyperlinks based on UserAgent</h2>
42
+<h2>Automatic Hyperlinks Based on UserAgent</h2>
4643
4744
 Fossil has the ability to selectively enable hyperlinks for users
48
-that lack the "h" capability based on their UserAgent string in the
45
+that lack the <b>Hyperlink</b> capability based on their UserAgent string in the
4946
 HTTP request header and on the browsers ability to run Javascript.
5047
5148
 The UserAgent string is a text identifier that is included in the header
5249
 of most HTTP requests that identifies the specific maker and version of
5350
 the browser (or spider) that generated the request. Typical UserAgent
@@ -76,11 +73,11 @@
7673
7774
 In Fossil, under the Admin/Access menu, there is a setting entitled
7875
 "<b>Enable hyperlinks for "nobody" based on User-Agent and Javascript</b>".
7976
 If this setting is enabled, and if the UserAgent string looks like a
8077
 human and not a spider, then Fossil will enable hyperlinks even if
81
-the "h" capability is omitted from the user permissions. This setting
78
+the <b>Hyperlink</b> capability is omitted from the user permissions. This setting
8279
 gives humans easy access to the hyperlinks while preventing spiders
8380
 from walking the millions of pages on a typical Fossil site.
8481
8582
 But the hyperlinks are not enabled directly with the setting above.
8683
 Instead, the HTML code that is generated contains anchor tags ("&lt;a&gt;")
@@ -92,11 +89,11 @@
9289
 UserAgent string. Most spiders do not bother to run JavaScript and
9390
 so to the spider the empty anchor tag will be useless. But all modern
9491
 web browsers implement JavaScript, so hyperlinks will show up
9592
 normally for human users.
9693
97
-<h2>Further defenses</h2>
94
+<h2>Further Defenses</h2>
9895
9996
 Recently (as of this writing, in the spring of 2013) the Fossil server
10097
 on the SQLite website ([http://www.sqlite.org/src/]) has been hit repeatedly
10198
 by Chinese spiders that use forged UserAgent strings to make them look
10299
 like normal web browsers and which interpret JavaScript. We do not
@@ -134,11 +131,11 @@
134131
135132
 See also [./loadmgmt.md|Managing Server Load] for a description
136133
 of how expensive pages can be disabled when the server is under heavy
137134
 load.
138135
139
-<h2>The ongoing struggle</h2>
136
+<h2>The Ongoing Struggle</h2>
140137
141138
 Fossil currently does a very good job of providing easy access to humans
142139
 while keeping out troublesome robots and spiders. However, spiders and
143140
 bots continue to grow more sophisticated, requiring ever more advanced
144141
 defenses. This "arms race" is unlikely to ever end. The developers of
145142
146143
ADDED www/caps/admin-v-setup.md
147144
ADDED www/caps/impl.md
148145
ADDED www/caps/index.md
149146
ADDED www/caps/login-groups.md
150147
ADDED www/caps/ref.html
--- www/antibot.wiki
+++ www/antibot.wiki
@@ -10,44 +10,41 @@
10 The website presented by a Fossil server is intended to be used
11 interactively by humans, not walked by spiders. This article
12 describes the techniques used by Fossil to try to welcome human
13 users while keeping out spiders.
14
15 <h2>The "hyperlink" user capability</h2>
16
17 Every Fossil web session has a "user". For random passers-by on the internet
18 (and for spiders) that user is "nobody". The "anonymous" user is also
19 available for humans who do not wish to identify themselves. The difference
20 is that "anonymous" requires a login (using a password supplied via
21 a CAPTCHA) whereas "nobody" does not require a login.
22 The site administrator can also create logins with
23 passwords for specific individuals.
24
25 The "h" or "hyperlink" capability is a permission that can be granted
26 to users that enables the display of hyperlinks. Most of the hyperlinks
27 generated by Fossil are suppressed if this capability is missing. So
28 one simple defense against spiders is to disable the "h" permission for
29 the "nobody" user. This means that users must log in (perhaps as
30 "anonymous") before they can see any of the hyperlinks. Spiders do not
31 normally attempt to log into websites and will therefore
32 not see most of the hyperlinks and will not try to walk the millions of
33 historical check-ins and diffs available on a Fossil-generated website.
34
35 If the "h" capability is missing from user "nobody" but is present for
36 user "anonymous", then a message automatically appears at the top of each
37 page inviting the user to log in as anonymous in order to activate hyperlinks.
38
39 Removing the "h" capability from user "nobody" is an effective means
40 of preventing spiders from walking a Fossil-generated website. But
41 it can also be annoying to humans, since it requires them to log in.
42 Hence, Fossil provides other techniques for blocking spiders which
43 are less cumbersome to humans.
44
45 <h2>Automatic hyperlinks based on UserAgent</h2>
46
47 Fossil has the ability to selectively enable hyperlinks for users
48 that lack the "h" capability based on their UserAgent string in the
49 HTTP request header and on the browsers ability to run Javascript.
50
51 The UserAgent string is a text identifier that is included in the header
52 of most HTTP requests that identifies the specific maker and version of
53 the browser (or spider) that generated the request. Typical UserAgent
@@ -76,11 +73,11 @@
76
77 In Fossil, under the Admin/Access menu, there is a setting entitled
78 "<b>Enable hyperlinks for "nobody" based on User-Agent and Javascript</b>".
79 If this setting is enabled, and if the UserAgent string looks like a
80 human and not a spider, then Fossil will enable hyperlinks even if
81 the "h" capability is omitted from the user permissions. This setting
82 gives humans easy access to the hyperlinks while preventing spiders
83 from walking the millions of pages on a typical Fossil site.
84
85 But the hyperlinks are not enabled directly with the setting above.
86 Instead, the HTML code that is generated contains anchor tags ("&lt;a&gt;")
@@ -92,11 +89,11 @@
92 UserAgent string. Most spiders do not bother to run JavaScript and
93 so to the spider the empty anchor tag will be useless. But all modern
94 web browsers implement JavaScript, so hyperlinks will show up
95 normally for human users.
96
97 <h2>Further defenses</h2>
98
99 Recently (as of this writing, in the spring of 2013) the Fossil server
100 on the SQLite website ([http://www.sqlite.org/src/]) has been hit repeatedly
101 by Chinese spiders that use forged UserAgent strings to make them look
102 like normal web browsers and which interpret JavaScript. We do not
@@ -134,11 +131,11 @@
134
135 See also [./loadmgmt.md|Managing Server Load] for a description
136 of how expensive pages can be disabled when the server is under heavy
137 load.
138
139 <h2>The ongoing struggle</h2>
140
141 Fossil currently does a very good job of providing easy access to humans
142 while keeping out troublesome robots and spiders. However, spiders and
143 bots continue to grow more sophisticated, requiring ever more advanced
144 defenses. This "arms race" is unlikely to ever end. The developers of
145
146 DDED www/caps/admin-v-setup.md
147 DDED www/caps/impl.md
148 DDED www/caps/index.md
149 DDED www/caps/login-groups.md
150 DDED www/caps/ref.html
--- www/antibot.wiki
+++ www/antibot.wiki
@@ -10,44 +10,41 @@
10 The website presented by a Fossil server is intended to be used
11 interactively by humans, not walked by spiders. This article
12 describes the techniques used by Fossil to try to welcome human
13 users while keeping out spiders.
14
15 <h2>The Hyperlink User Capability</h2>
16
17 Every Fossil web session has a "user". For random passers-by on the internet
18 (and for spiders) that user is "nobody". The "anonymous" user is also
19 available for humans who do not wish to identify themselves. The difference
20 is that "anonymous" requires a login (using a password supplied via
21 a CAPTCHA) whereas "nobody" does not require a login.
22 The site administrator can also create logins with
23 passwords for specific individuals.
24
25 Users without the <b>[./caps/ref.html#h | Hyperlink]</b> capability
26 do not see most Fossil-generated hyperlinks. This is
27 a simple defense against spiders, since [./caps/#ucat | the "nobody"
28 user category] does not have this capability by default.
29 Users must log in (perhaps as
30 "anonymous") before they can see any of the hyperlinks. A spider
31 that cannot log into your Fossil repository will be unable to walk
32 its historical check-ins, create diffs between versions, pull zip
33 archives, etc. by visiting links, because they aren't there.
34
35 A text message appears at the top of each page in this situation to
36 invite humans to log in as anonymous in order to activate hyperlinks.
37
38 Because this required login step is annoying to some,
39 Fossil provides other techniques for blocking spiders which
 
 
 
40 are less cumbersome to humans.
41
42 <h2>Automatic Hyperlinks Based on UserAgent</h2>
43
44 Fossil has the ability to selectively enable hyperlinks for users
45 that lack the <b>Hyperlink</b> capability based on their UserAgent string in the
46 HTTP request header and on the browsers ability to run Javascript.
47
48 The UserAgent string is a text identifier that is included in the header
49 of most HTTP requests that identifies the specific maker and version of
50 the browser (or spider) that generated the request. Typical UserAgent
@@ -76,11 +73,11 @@
73
74 In Fossil, under the Admin/Access menu, there is a setting entitled
75 "<b>Enable hyperlinks for "nobody" based on User-Agent and Javascript</b>".
76 If this setting is enabled, and if the UserAgent string looks like a
77 human and not a spider, then Fossil will enable hyperlinks even if
78 the <b>Hyperlink</b> capability is omitted from the user permissions. This setting
79 gives humans easy access to the hyperlinks while preventing spiders
80 from walking the millions of pages on a typical Fossil site.
81
82 But the hyperlinks are not enabled directly with the setting above.
83 Instead, the HTML code that is generated contains anchor tags ("&lt;a&gt;")
@@ -92,11 +89,11 @@
89 UserAgent string. Most spiders do not bother to run JavaScript and
90 so to the spider the empty anchor tag will be useless. But all modern
91 web browsers implement JavaScript, so hyperlinks will show up
92 normally for human users.
93
94 <h2>Further Defenses</h2>
95
96 Recently (as of this writing, in the spring of 2013) the Fossil server
97 on the SQLite website ([http://www.sqlite.org/src/]) has been hit repeatedly
98 by Chinese spiders that use forged UserAgent strings to make them look
99 like normal web browsers and which interpret JavaScript. We do not
@@ -134,11 +131,11 @@
131
132 See also [./loadmgmt.md|Managing Server Load] for a description
133 of how expensive pages can be disabled when the server is under heavy
134 load.
135
136 <h2>The Ongoing Struggle</h2>
137
138 Fossil currently does a very good job of providing easy access to humans
139 while keeping out troublesome robots and spiders. However, spiders and
140 bots continue to grow more sophisticated, requiring ever more advanced
141 defenses. This "arms race" is unlikely to ever end. The developers of
142
143 DDED www/caps/admin-v-setup.md
144 DDED www/caps/impl.md
145 DDED www/caps/index.md
146 DDED www/caps/login-groups.md
147 DDED www/caps/ref.html
M www/caps/admin-v-setup.md
+8 -5
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -1,6 +1,9 @@
1
-# The Differences Between theilitiestween Sthe power hierarcKeep Several of the Fossil user capabilities form a clear power hierarchy.
2
-Mathematically speaking:
1
+# Differences Btween Sthe power hierarcKeep in mind that
2
+which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since
3
+this also copiesthe `user` table on theies. In this way, /antibot.wiki)
34
4
-> *Setup > Admin > Moderator > User > Subsc# The Differences Betw
5
-o@3x,g@4j,j@5O,rE@6z,2rO@yg,7:[ucap]:W@3ln,G:setup_ucap_list
6
-12p~Gn;
5
+[au]: geable clones. This is useful not o, it is a useful element of a load balancing and
6
+failover system# Differences Between Sthe power hierarchy laid out at tblock
7
+chain][bc], blockchainblockchainblockchainTH [`fossil
8
+ (“y”)
9
+ ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -1,6 +1,9 @@
1 # The Differences Between theilitiestween Sthe power hierarcKeep Several of the Fossil user capabilities form a clear power hierarchy.
2 Mathematically speaking:
 
3
4 > *Setup > Admin > Moderator > User > Subsc# The Differences Betw
5 o@3x,g@4j,j@5O,rE@6z,2rO@yg,7:[ucap]:W@3ln,G:setup_ucap_list
6 12p~Gn;
 
 
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -1,6 +1,9 @@
1 # Differences Btween Sthe power hierarcKeep in mind that
2 which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since
3 this also copiesthe `user` table on theies. In this way, /antibot.wiki)
4
5 [au]: geable clones. This is useful not o, it is a useful element of a load balancing and
6 failover system# Differences Between Sthe power hierarchy laid out at tblock
7 chain][bc], blockchainblockchainblockchainTH [`fossil
8 (“y”)
9 ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)
A www/caps/admin-v-setup.md
+9
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -0,0 +1,9 @@
1
+# Differences Btween Sthe power hierarcKeep in mind that
2
+which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since
3
+this also copiesthe `user` table on theies. In this way, /antibot.wiki)
4
+
5
+[au]: geable clones. This is useful not o, it is a useful element of a load balancing and
6
+failover system# Differences Between Sthe power hierarchy laid out at tblock
7
+chain][bc], blockchainblockchainblockchainTH [`fossil
8
+ (“y”)
9
+ ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -0,0 +1,9 @@
 
 
 
 
 
 
 
 
 
--- a/www/caps/admin-v-setup.md
+++ b/www/caps/admin-v-setup.md
@@ -0,0 +1,9 @@
1 # Differences Btween Sthe power hierarcKeep in mind that
2 which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since
3 this also copiesthe `user` table on theies. In this way, /antibot.wiki)
4
5 [au]: geable clones. This is useful not o, it is a useful element of a load balancing and
6 failover system# Differences Between Sthe power hierarchy laid out at tblock
7 chain][bc], blockchainblockchainblockchainTH [`fossil
8 (“y”)
9 ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)
M www/caps/impl.md
+64
--- a/www/caps/impl.md
+++ b/www/caps/impl.md
@@ -0,0 +1,64 @@
1
+# Implementation Details onameUser Capabilities
2
+
3
+## <a id="choices"></a>Capability Letter Choices
4
+
5
+We [assigned][ref] user capability characters using only lowercase ASCII
6
+letters at first, so those are the most important within Fossil: they
7
+control the functions most core to Fossil’s operation. Once we used up
8
+most of the lowercase letters, we started using uppercase, and then
9
+during the development of the [forum feature][for] we assigned most of
10
+the decimal numerals. All of the lowercase ASCII letters are now
11
+assigned. Eventually, we might have to start using ASCII
12
+punctuation and symbols. We expect to run out of reasons to define new caps before
13
+we’re forced to switch to Unicode, though the possibilities for [mnemonic][mn]
14
+assignments with emoji are intriguing. <span style="vertical-align:
15
+bottom">😉</span>
16
+
17
+The existing caps are usually mnemonic, especially among the
18
+earliest and therefore most central assignments, made when we still had
19
+lots of letters to choose from. There is still hope for good future
20
+mnemonic assignments among the uppename="bitfield"></a>Why Not Bitfields?
21
+
22
+Some may question the use of ASCII character strings for [capability
23
+sets][ucap] instead of bitfields, which are more efficient, both in
24
+terms of storage and processing time.
25
+
26
+Fossil handles these character strings in one of two ways. For most HTTP
27
+hitsblock chain[expands][sexp] the string into a [`struct` full of
28
+flags][sff] so that later code can just do simple Boolean tests. In a
29
+minority of cases, where Fossil only needs to check for the presence of
30
+a single flag, it just does a [`strchr()` call][sc] on the string
31
+instead.
32
+
33
+Both methods are slower than bit testing in a bitfield, but keep the
34
+execution context in mind: at the front end of an HTTP request handler,
35
+where the nanosecond differences in such implementation details are
36
+completely swamped by the millisecond scale ping time of that repo’s
37
+network connection, followed by the required I/O to satisfy the request.
38
+Either method is plenty fast in that context.
39
+
40
+In exchange for this immeasurable cost per hit, we get human-readablname="filter"></a>Why Doesn’t Fossil Filter “Bad” Artifacts on Sync?
41
+
42
+Fossil is more trusting about the content it receives from a remote
43
+clone during sync than you might expect. Common manifestations of this
44
+design choice are:
45
+
46
+1. A user may be able to impersonate other users. This can be
47
+ [accidental](./index.md#defuser) as well as purposeful.
48
+
49
+2. If your local system clock is out-of-sync with absolute time,
50
+ artifacts committed to that repo will appear with the “wrong” time
51
+ when sync’d. If the time sync error is big enough, it can make
52
+ check-ins appear to go back in time and other bad effects.
53
+
54
+3. You can purposely overwrite good timestamps with bad ones and push
55
+ those changes up to the remote with no interference, even though
56
+ Fossil tries to make that a Setup-only operation.
57
+
58
+All of this falls out of two of Fossil’s design choices: sync is
59
+all-or-nothing, and [the Fossil hash tree][bc] is immutable. Fossil
60
+would have to violate one or both of these principles to filter such
61
+problems out of incoming syncs.
62
+
63
+We have considered auto-[shunning][shun] “bad” content on sync, but this
64
+is [difficult][asd] due to [the design of th
--- a/www/caps/impl.md
+++ b/www/caps/impl.md
@@ -0,0 +1,64 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/caps/impl.md
+++ b/www/caps/impl.md
@@ -0,0 +1,64 @@
1 # Implementation Details onameUser Capabilities
2
3 ## <a id="choices"></a>Capability Letter Choices
4
5 We [assigned][ref] user capability characters using only lowercase ASCII
6 letters at first, so those are the most important within Fossil: they
7 control the functions most core to Fossil’s operation. Once we used up
8 most of the lowercase letters, we started using uppercase, and then
9 during the development of the [forum feature][for] we assigned most of
10 the decimal numerals. All of the lowercase ASCII letters are now
11 assigned. Eventually, we might have to start using ASCII
12 punctuation and symbols. We expect to run out of reasons to define new caps before
13 we’re forced to switch to Unicode, though the possibilities for [mnemonic][mn]
14 assignments with emoji are intriguing. <span style="vertical-align:
15 bottom">😉</span>
16
17 The existing caps are usually mnemonic, especially among the
18 earliest and therefore most central assignments, made when we still had
19 lots of letters to choose from. There is still hope for good future
20 mnemonic assignments among the uppename="bitfield"></a>Why Not Bitfields?
21
22 Some may question the use of ASCII character strings for [capability
23 sets][ucap] instead of bitfields, which are more efficient, both in
24 terms of storage and processing time.
25
26 Fossil handles these character strings in one of two ways. For most HTTP
27 hitsblock chain[expands][sexp] the string into a [`struct` full of
28 flags][sff] so that later code can just do simple Boolean tests. In a
29 minority of cases, where Fossil only needs to check for the presence of
30 a single flag, it just does a [`strchr()` call][sc] on the string
31 instead.
32
33 Both methods are slower than bit testing in a bitfield, but keep the
34 execution context in mind: at the front end of an HTTP request handler,
35 where the nanosecond differences in such implementation details are
36 completely swamped by the millisecond scale ping time of that repo’s
37 network connection, followed by the required I/O to satisfy the request.
38 Either method is plenty fast in that context.
39
40 In exchange for this immeasurable cost per hit, we get human-readablname="filter"></a>Why Doesn’t Fossil Filter “Bad” Artifacts on Sync?
41
42 Fossil is more trusting about the content it receives from a remote
43 clone during sync than you might expect. Common manifestations of this
44 design choice are:
45
46 1. A user may be able to impersonate other users. This can be
47 [accidental](./index.md#defuser) as well as purposeful.
48
49 2. If your local system clock is out-of-sync with absolute time,
50 artifacts committed to that repo will appear with the “wrong” time
51 when sync’d. If the time sync error is big enough, it can make
52 check-ins appear to go back in time and other bad effects.
53
54 3. You can purposely overwrite good timestamps with bad ones and push
55 those changes up to the remote with no interference, even though
56 Fossil tries to make that a Setup-only operation.
57
58 All of this falls out of two of Fossil’s design choices: sync is
59 all-or-nothing, and [the Fossil hash tree][bc] is immutable. Fossil
60 would have to violate one or both of these principles to filter such
61 problems out of incoming syncs.
62
63 We have considered auto-[shunning][shun] “bad” content on sync, but this
64 is [difficult][asd] due to [the design of th
M www/caps/index.md
+39
--- a/www/caps/index.md
+++ b/www/caps/index.md
@@ -0,0 +1,39 @@
1
+local fileadding a
2
+[**Se capability
3
+namenamenamenamenamenamenamenamenamenamecap].
4
+
5
+ The SSH client command defaults to “`ssh -e none -T`” on most
6
+ platforms except Windows where it defaults to “`plink -ssh -T`”.
7
+ Yssh-command`
8
+ setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over
9
+`http[s]://` URLs, and [the JSON API][japi].
10
+
11
+User caps *do not* affect operations done on a local repo opened via a
12
+`file://` URL or a file system path. as sensible:
13
+only localmatter when operating on a local SQLite DB
14
+file. The same is true when working on a clone done over such a path,
15
+except thAsat there are
16
+
17
+[sync][sync] with
18
+effectively
19
+both sides of the sync.
20
+
21
+What may surprise you is that user caps *also do not affect SSH!* When
22
+
23
+local clone,
24
+
25
+is on the local file system. If you can log into the remote system over
26
+ on that
27
+, it isfor `file://` URLs.
28
+
29
+All��.
30
+ Yssh-command`
31
+ selocal fileadd
32
+ie without cap checks. The SSH client defaults to “`ssh
33
+ -e none -T`” on most platforms, except on Windows where it defaults
34
+ ,n’t do this
35
+ withBecause both mechanisms work on local repos, the checks for capabilities
36
+for
37
+such URLs can never return “false,” because you are the [**Setup**][s]
38
+user on both sides of the conversation. Such check
39
+effect ddd][d][e][e][i][i]**: delete,
--- a/www/caps/index.md
+++ b/www/caps/index.md
@@ -0,0 +1,39 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/caps/index.md
+++ b/www/caps/index.md
@@ -0,0 +1,39 @@
1 local fileadding a
2 [**Se capability
3 namenamenamenamenamenamenamenamenamenamecap].
4
5 The SSH client command defaults to “`ssh -e none -T`” on most
6 platforms except Windows where it defaults to “`plink -ssh -T`”.
7 Yssh-command`
8 setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over
9 `http[s]://` URLs, and [the JSON API][japi].
10
11 User caps *do not* affect operations done on a local repo opened via a
12 `file://` URL or a file system path. as sensible:
13 only localmatter when operating on a local SQLite DB
14 file. The same is true when working on a clone done over such a path,
15 except thAsat there are
16
17 [sync][sync] with
18 effectively
19 both sides of the sync.
20
21 What may surprise you is that user caps *also do not affect SSH!* When
22
23 local clone,
24
25 is on the local file system. If you can log into the remote system over
26 on that
27 , it isfor `file://` URLs.
28
29 All��.
30 Yssh-command`
31 selocal fileadd
32 ie without cap checks. The SSH client defaults to “`ssh
33 -e none -T`” on most platforms, except on Windows where it defaults
34 ,n’t do this
35 withBecause both mechanisms work on local repos, the checks for capabilities
36 for
37 such URLs can never return “false,” because you are the [**Setup**][s]
38 user on both sides of the conversation. Such check
39 effect ddd][d][e][e][i][i]**: delete,
M www/caps/login-groups.md
+6
--- a/www/caps/login-groups.md
+++ b/www/caps/login-groups.md
@@ -0,0 +1,6 @@
1
+# Login Groups
2
+
3
+The Admin → Login-Groups UI feature and its corresponding [`login-groet of users all need access to, those users all
4
+have the same access level on all oconfigure the us. With this configureIf repo C
5
+joined repo B and repo B joined A, changes in C’s user table affect both
6
+A and B, if you tell Fossil that the change applilogin group
--- a/www/caps/login-groups.md
+++ b/www/caps/login-groups.md
@@ -0,0 +1,6 @@
 
 
 
 
 
 
--- a/www/caps/login-groups.md
+++ b/www/caps/login-groups.md
@@ -0,0 +1,6 @@
1 # Login Groups
2
3 The Admin → Login-Groups UI feature and its corresponding [`login-groet of users all need access to, those users all
4 have the same access level on all oconfigure the us. With this configureIf repo C
5 joined repo B and repo B joined A, changes in C’s user table affect both
6 A and B, if you tell Fossil that the change applilogin group
M www/caps/ref.html
+35
--- a/www/caps/ref.html
+++ b/www/caps/ref.html
@@ -0,0 +1,35 @@
1
+<div class='fossil This
2
+ letter was assigned by default to Developer in repos created with
3
+ Fossil 2.10 or earlier, but it has no effect in current or past
4
+. Mnemonic:
5
+ repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This
6
+ letter was assigned by default to Developer in repos created with
7
+ Fossil 2.10 or earlier, but it has no effect in current or past
8
+. Mnemonic:
9
+ repository contentits durable blockchain natureis
10
+ letter was assigned“key”’ated with
11
+ Fossil 2.10 or earlier, but it has no effect in current or past
12
+. Mnemonic:
13
+ repository contentits durable bl<div class='fossil This
14
+ letter was assigned by default to Developer in repos created with
15
+ Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This
16
+ letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This
17
+ letter was assigned by default to Developer in repos created with
18
+ Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past
19
+. Mnemonic:
20
+ repositorytter was assigned by default to Developer in repos created with
21
+ Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This
22
+ letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with
23
+ Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This
24
+ letter was assigned by default to Developer in repos created with
25
+ Fossil 2.10 or earlier, but it has no effect in current or past
26
+. Mnemonic:
27
+ repository c
28
+ ’ os created with
29
+ Fossil 2.10 or earlier, but it has no effect in current or past
30
+. Mnemonic:
31
+ repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This
32
+ letter was assigned by default to Developer in repos created with
33
+ Fossil 2.10 or earlier, but it has no effect in current or past
34
+. Mnemonic:
35
+ repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’
--- a/www/caps/ref.html
+++ b/www/caps/ref.html
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/caps/ref.html
+++ b/www/caps/ref.html
@@ -0,0 +1,35 @@
1 <div class='fossil This
2 letter was assigned by default to Developer in repos created with
3 Fossil 2.10 or earlier, but it has no effect in current or past
4 . Mnemonic:
5 repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This
6 letter was assigned by default to Developer in repos created with
7 Fossil 2.10 or earlier, but it has no effect in current or past
8 . Mnemonic:
9 repository contentits durable blockchain natureis
10 letter was assigned“key”’ated with
11 Fossil 2.10 or earlier, but it has no effect in current or past
12 . Mnemonic:
13 repository contentits durable bl<div class='fossil This
14 letter was assigned by default to Developer in repos created with
15 Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This
16 letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This
17 letter was assigned by default to Developer in repos created with
18 Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past
19 . Mnemonic:
20 repositorytter was assigned by default to Developer in repos created with
21 Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This
22 letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with
23 Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This
24 letter was assigned by default to Developer in repos created with
25 Fossil 2.10 or earlier, but it has no effect in current or past
26 . Mnemonic:
27 repository c
28 ’ os created with
29 Fossil 2.10 or earlier, but it has no effect in current or past
30 . Mnemonic:
31 repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This
32 letter was assigned by default to Developer in repos created with
33 Fossil 2.10 or earlier, but it has no effect in current or past
34 . Mnemonic:
35 repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’
M www/cgi.wiki
+5 -5
--- www/cgi.wiki
+++ www/cgi.wiki
@@ -67,11 +67,11 @@
6767
 of the HTTP request does not correspond to any Fossil repository, then
6868
 the request redirects to URL.
6969
7070
 <h2 id="repolist">repolist</h2>
7171
72
-This is a boolean property.
72
+This is a Boolean property.
7373
 If it is present, and if the [#directory:|<b>directory:</b>] option is used,
7474
 and if the PATH_INFO string is empty, then Fossil will show a list
7575
 of available Fossil repositories.
7676
7777
 The "skin" of the reply is determined by the first
@@ -100,15 +100,15 @@
100100
 If N is zero, then there is no timeout. If this property is omitted,
101101
 then the default timeout is 300 seconds (5 minutes).
102102
103103
 <h2 id="localauth">localauth</h2>
104104
105
-This is a boolean property.
106
-If it is present, setup administrator privileges
107
-(capability letter 's') are granted to any HTTP request that
105
+This is a Boolean property.
106
+If it is present, [./caps/ref.html#s | setup capability]
107
+is granted to any HTTP request that
108108
 comes in over a loopback interface, such as 127.0.0.1.
109
-and if the PATH_INFO string is empty, then Fossil will show a list
109
+If the PATH_INFO string is empty, Fossil will show a list
110110
 of available Fossil repositories.
111111
112112
 <h2 id="skin">skin: <i>NAME</i></h2>
113113
114114
 If NAME is the name of one of the built-in skins supported by Fossil,
115115
--- www/cgi.wiki
+++ www/cgi.wiki
@@ -67,11 +67,11 @@
67 of the HTTP request does not correspond to any Fossil repository, then
68 the request redirects to URL.
69
70 <h2 id="repolist">repolist</h2>
71
72 This is a boolean property.
73 If it is present, and if the [#directory:|<b>directory:</b>] option is used,
74 and if the PATH_INFO string is empty, then Fossil will show a list
75 of available Fossil repositories.
76
77 The "skin" of the reply is determined by the first
@@ -100,15 +100,15 @@
100 If N is zero, then there is no timeout. If this property is omitted,
101 then the default timeout is 300 seconds (5 minutes).
102
103 <h2 id="localauth">localauth</h2>
104
105 This is a boolean property.
106 If it is present, setup administrator privileges
107 (capability letter 's') are granted to any HTTP request that
108 comes in over a loopback interface, such as 127.0.0.1.
109 and if the PATH_INFO string is empty, then Fossil will show a list
110 of available Fossil repositories.
111
112 <h2 id="skin">skin: <i>NAME</i></h2>
113
114 If NAME is the name of one of the built-in skins supported by Fossil,
115
--- www/cgi.wiki
+++ www/cgi.wiki
@@ -67,11 +67,11 @@
67 of the HTTP request does not correspond to any Fossil repository, then
68 the request redirects to URL.
69
70 <h2 id="repolist">repolist</h2>
71
72 This is a Boolean property.
73 If it is present, and if the [#directory:|<b>directory:</b>] option is used,
74 and if the PATH_INFO string is empty, then Fossil will show a list
75 of available Fossil repositories.
76
77 The "skin" of the reply is determined by the first
@@ -100,15 +100,15 @@
100 If N is zero, then there is no timeout. If this property is omitted,
101 then the default timeout is 300 seconds (5 minutes).
102
103 <h2 id="localauth">localauth</h2>
104
105 This is a Boolean property.
106 If it is present, [./caps/ref.html#s | setup capability]
107 is granted to any HTTP request that
108 comes in over a loopback interface, such as 127.0.0.1.
109 If the PATH_INFO string is empty, Fossil will show a list
110 of available Fossil repositories.
111
112 <h2 id="skin">skin: <i>NAME</i></h2>
113
114 If NAME is the name of one of the built-in skins supported by Fossil,
115
M www/custom_ticket.wiki
+1 -1
--- www/custom_ticket.wiki
+++ www/custom_ticket.wiki
@@ -83,11 +83,11 @@
8383
 &lt;td align="right">Opened by:&lt;/td>&lt;td bgcolor="#d0d0d0">
8484
 $&lt;opened_by>
8585
 &lt;/td>
8686
 </pre>
8787
 This will add a row which displays these two fields, in the event the user has
88
-"edit" capability.
88
+<a href="./caps/ref.html#w">ticket "edit" capability</a>.
8989
 </p>
9090
 </blockquote>
9191
9292
 <h2>Modify the 'edit ticket' page</h2><blockquote>
9393
 <p>
9494
--- www/custom_ticket.wiki
+++ www/custom_ticket.wiki
@@ -83,11 +83,11 @@
83 &lt;td align="right">Opened by:&lt;/td>&lt;td bgcolor="#d0d0d0">
84 $&lt;opened_by>
85 &lt;/td>
86 </pre>
87 This will add a row which displays these two fields, in the event the user has
88 "edit" capability.
89 </p>
90 </blockquote>
91
92 <h2>Modify the 'edit ticket' page</h2><blockquote>
93 <p>
94
--- www/custom_ticket.wiki
+++ www/custom_ticket.wiki
@@ -83,11 +83,11 @@
83 &lt;td align="right">Opened by:&lt;/td>&lt;td bgcolor="#d0d0d0">
84 $&lt;opened_by>
85 &lt;/td>
86 </pre>
87 This will add a row which displays these two fields, in the event the user has
88 <a href="./caps/ref.html#w">ticket "edit" capability</a>.
89 </p>
90 </blockquote>
91
92 <h2>Modify the 'edit ticket' page</h2><blockquote>
93 <p>
94
M www/defcsp.md
+1 -1
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146146
 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147147
 use in `<script>` elements it generates. Because these extensions
148148
 can only be installed by the Fossil server’s system administrator,
149149
 this path is also considered safe.
150150
151
-[su]: ./admin-v-setup.md
152151
 [ext]: ./serverext.wiki
152
+[su]: ./caps/admin-v-setup.md#apsu
153153
154154
155155
 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156156
157157
 We’re so restrictive about how we treat JavaScript because it can lead
158158
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147 use in `<script>` elements it generates. Because these extensions
148 can only be installed by the Fossil server’s system administrator,
149 this path is also considered safe.
150
151 [su]: ./admin-v-setup.md
152 [ext]: ./serverext.wiki
 
153
154
155 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156
157 We’re so restrictive about how we treat JavaScript because it can lead
158
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147 use in `<script>` elements it generates. Because these extensions
148 can only be installed by the Fossil server’s system administrator,
149 this path is also considered safe.
150
 
151 [ext]: ./serverext.wiki
152 [su]: ./caps/admin-v-setup.md#apsu
153
154
155 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156
157 We’re so restrictive about how we treat JavaScript because it can lead
158
M www/defcsp.md
+1 -1
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146146
 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147147
 use in `<script>` elements it generates. Because these extensions
148148
 can only be installed by the Fossil server’s system administrator,
149149
 this path is also considered safe.
150150
151
-[su]: ./admin-v-setup.md
152151
 [ext]: ./serverext.wiki
152
+[su]: ./caps/admin-v-setup.md#apsu
153153
154154
155155
 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156156
157157
 We’re so restrictive about how we treat JavaScript because it can lead
158158
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147 use in `<script>` elements it generates. Because these extensions
148 can only be installed by the Fossil server’s system administrator,
149 this path is also considered safe.
150
151 [su]: ./admin-v-setup.md
152 [ext]: ./serverext.wiki
 
153
154
155 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156
157 We’re so restrictive about how we treat JavaScript because it can lead
158
--- www/defcsp.md
+++ www/defcsp.md
@@ -146,12 +146,12 @@
146 CGI in the `FOSSIL_NONCE` environment variable, which it can then
147 use in `<script>` elements it generates. Because these extensions
148 can only be installed by the Fossil server’s system administrator,
149 this path is also considered safe.
150
 
151 [ext]: ./serverext.wiki
152 [su]: ./caps/admin-v-setup.md#apsu
153
154
155 #### <a name="xss"></a>Cross-Site Scripting via Ordinary User Capabilities
156
157 We’re so restrictive about how we treat JavaScript because it can lead
158
M www/forum.wiki
+34 -66
--- www/forum.wiki
+++ www/forum.wiki
@@ -74,14 +74,14 @@
7474
 third-party forum software and mailing list search engines, your
7575
 links are only valid until the third-party component changes its
7676
 URL scheme or disappears from the web.
7777
7878
 * <b>Role-Based Access Control:</b> The forum uses the same
79
- [https://en.wikipedia.org/wiki/Role-based_access_control | RBAC
79
+ [./caps/ | capability-based access control
8080
 system] that Fossil uses to control all other repository accesses.
81
- The Fossil forum feature simply adds several new fine-grained
82
- capability bits to the existing system.
81
+ The Fossil forum feature simply adds [./caps/ref.html#2 | several new fine-grained
82
+ capabilities] to the existing system.
8383
8484
 * <b>Enduring, Open File Format:</b> Since Fossil has an
8585
 [./fileformat.wiki | open and well-documented file format], your
8686
 discussion archives are truly that: <em>archives</em>. You are no
8787
 longer dependent on the lifetime and business model of a
@@ -109,63 +109,37 @@
109109
110110
 <h2 id="setup">Setting up a Fossil Forum</h2>
111111
112112
 <h3 id="caps">Capabilities</h3>
113113
114
-Fossil forums use the same role-based access control mechanism as
115
-for normal Fossil repository logins.
116
-
117
-There are several dedicated forum-related capability bits you can grant
118
-a user:
119
-
120
- * <b>Read Forum</b> (<tt>2</tt>): The user may read forum posts.
121
-
122
- * <b>Write Forum</b> (<tt>3</tt>): The user may create new forum
123
- threads, reply to existing threads, and edit their own posts. New
124
- posts are held for moderation, and they are marked to prevent them
125
- from being included in clone and sync operations.
126
-
127
- * <b>WriteTrusted Forum</b> (<tt>4</tt>): Same as <b>Write Forum</b>
128
- except that forum updates bypass the [#moderation | moderation and
129
- private artifact restrictions].
130
-
131
- * <b>Moderate Forum</b> (<tt>5</tt>): User gets buttons on posts
132
- which allow them to either reject or approve posts held for
133
- moderation. User also gets access to a page (<tt>/modreq</tt>)
134
- showing the list of pending moderation tasks.
135
-
136
- * <b>Supervise Forum</b> (<tt>6</tt>): User can grant or revoke
137
- <b>WriteTrusted</b> capability for other users. (Currently
138
- unimplemented.)
139
-
140
- * <b>Email Alerts</b> (<tt>7</tt>): User can sign themselves up for
141
- email alerts, a.k.a. notifications.
142
-
143114
 By default, no Fossil user has permission to use the forums except for
144115
 users with Setup and Admin capabilities, which get these as part of the
145116
 large package of other capabilities they get.
146117
147118
 For public Fossil repositories that wish to accept new users without
148119
 involving a human, go into Admin &rarr; Access and enable the "Allow
149120
 users to register themselves" setting. You may also wish to give users
150
-in the <tt>anonymous</tt> category the Read Forum (2) and Write Forum
151
-(3) capabilities: this allows people to post without creating an account
121
+in [./caps/#ucat | the <tt>anonymous</tt> user category] the
122
+<b>[./caps/ref.html#2 | RdForum]</b> and
123
+<b>[./caps/ref.html#3 | WrForum]</b>
124
+capabilities: this allows people to post without creating an account
152125
 simply by solving [./antibot.wiki | a simple CAPTCHA].
153126
154127
 For a private repository, you probably won't want to give the
155128
 <tt>anonymous</tt> user any forum access, but you may wish to give the
156
-Read Forum capability (2) to users in the <tt>reader</tt> category.
129
+<b>RdForum</b> capability to users in the <tt>reader</tt> category.
157130
158131
 For either type of repository, you are likely to want to give at least
159
-the WriteTrusted capability (4) to users in the <tt>developer</tt>
160
-category. If you did not give the Read Forum capability (2) to
132
+the <b>[./caps/ref.html#4 | WrTForum]</b> capability to users in the <tt>developer</tt>
133
+category. If you did not give the <b>RdForum</b> capability to
161134
 <tt>anonymous</tt> above, you should give <tt>developer</tt> that
162
-capability here if you choose to give it capability 3 or 4.
135
+capability here if you choose to give it <b>WrForum</b> or
136
+<b>WrTForum</b> capability.
163137
164138
 If you want to use the email alert feature, by default only those
165139
 users in the Setup and Admin user categories can make use of it. Grant
166
-the Email Alerts capability (7) to give others access to this feature.
140
+the <b>[./caps/ref.html#7 | EmailAlert]</b> capability to give others access to this feature.
167141
 Alternately, you can handle alert signups outside of Fossil, with
168142
 a Setup or Admin users manually signing users up via Admin &rarr;
169143
 Notification. You'll want to grant this capability to the
170144
 <tt>nobody</tt> user category if you want anyone to sign up without any
171145
 restrictions. Give it to <tt>anonymous</tt> instead if you want the
@@ -174,11 +148,11 @@
174148
 logins to have this ability. (That's assuming you give one or both of
175149
 these capabilities to every user on your Fossil repository.)
176150
177151
 By following this advice, you should not need to tediously add
178152
 capabilities to individual accounts except in atypical cases, such as
179
-to grant the Moderate Forum capability (5) to an uncommonly
153
+to grant the <b>[./caps/ref.html#5 | ModForum]</b> capability to an uncommonly
180154
 highly-trusted user.
181155
182156
183157
 <h3 id="skin">Skin Setup</h3>
184158
@@ -210,13 +184,13 @@
210184
 if {[anycap 23456] || [anoncap 2] || [anoncap 3]} {
211185
 menulink /forum Forum
212186
 }
213187
 </verbatim>
214188
215
-These rules say that any logged-in user with any forum-related
216
-capability (2-6 inclusive, as of this writing) or an anonymous user with
217
-read or write capability on the forum (2, 3) will see the "Forum" navbar
189
+These rules say that any logged-in user with any [./caps/ref.html#2 |
190
+forum-related capability] or an anonymous user <b>RdForum</b> or
191
+<b>WrForum</b> capability will see the "Forum" navbar
218192
 link, which just takes you to <tt>/forum</tt>.
219193
220194
 The exact code you need here varies depending on which skin you're
221195
 using. Follow the style you see for the other navbar links.
222196
@@ -303,14 +277,11 @@
303277
304278
 Yet, what of the users who will have logins on both repositories? Some
305279
 users will be trusted with access to the project's main Fossil
306280
 repository, and these users will probably also participate in the
307281
 project's Fossil-hosted forum. Fossil has a feature to solve this
308
-problem which is probably less well known than it should be, and which
309
-has been a feature of Fossil since April of 2011: Admin &rarr;
310
-Login-Group. This allows one Fossil repository to recognize users
311
-authorized on a different Fossil repository.
282
+problem: [./caps/login-groups.md | login groups].
312283
313284
314285
 <h3 id="alerts">Email Alerts (a.k.a. Notifications)</h3>
315286
316287
 Internet email service has become rather complicated since its initial
@@ -327,20 +298,18 @@
327298
328299
 There are many paths to a repository's Fossil forum:
329300
330301
 <ul>
331302
 <li>
332
- <p>If you're using the default Fossil skin as shipped with Fossil
333
- 2.7 or one updated to include the changes since 2.6 or prior, there
334
- is a Forum button in the navbar which appears for users with any of
335
- the forum-related user capabilities: 2 through 6 inclusive for those
336
- with repository logins, or caps 2 and 3 for users without a user
337
- account but who have solved the Anonymous user CAPTCHA.</p>
338
- <p>This button will not appear in the default skin for such users if
339
- their browser window is not greater than 1200 pixels wide. The
303
+ If you're using the default Fossil skin as shipped with Fossil
304
+ 2.7+ or one [#skin | updated] to support it, there
305
+ is a Forum button in the navbar which appears for users able to
306
+ access the forum. With the default skin, that button will only
307
+ appear if the user's browser window is at least
308
+ 1200 pixels wide. The
340309
 Fossil admin can adjust this limit in the skin's CSS section, down
341
- near the bottom in the definition of the `wideonly` style.</p>
310
+ near the bottom in the definition of the `wideonly` style.
342311
 </li>
343312
344313
 <li>The other stock skins have this button in them as of 2.7 as well,
345314
 without the screen width restriction, since the navbar in those skins
346315
 wraps on narrow screens more gracefully than the default skin
@@ -368,11 +337,11 @@
368337
369338
 * create a new post
370339
 * reply to an existing post
371340
 * edit a post or reply
372341
373
-When a person with the normal <b>Write Forum</b> capability (<tt>3</tt>)
342
+When a person with the normal <b>WrForum</b> capability
374343
 updates the forum, Fossil saves the update in its block chain, but this
375344
 update is impermanent because of two other table updates made at the
376345
 same time:
377346
378347
 <ol>
@@ -386,14 +355,13 @@
386355
 what causes Fossil to leave out the Reply button when rendering that
387356
 post's HTML in the forum's web interface.</li>
388357
 </ol>
389358
390359
 When a moderator approves an update, Fossil deletes these table entries,
391
-making the update semi-permanent. This changes how Fossil renders the
360
+making the update [./shunning.wiki | semi-permanent]. This changes how Fossil renders the
392361
 HTML for that update. It also means the artifact will now sync to
393
-clones, if the sync is done by a user with <b>Check-Out</b> capability
394
-(<tt>o</tt>).
362
+users with <b>[./caps/ref.html#g | Clone]</b> capability.
395363
396364
 When a forum user edits a moderator-approved artifact, what actually
397365
 happens under the hood is that Fossil writes another artifact to the
398366
 repository which refers to the original version as its parent, causing
399367
 Fossil UI to present the new version instead of the original. The
@@ -403,11 +371,11 @@
403371
404372
 When you "Delete" a moderator-approved post or reply through Fossil UI,
405373
 it's actually an edit with blank replacement content. The only way to
406374
 truly delete such artifacts is through [./shunning.wiki | shunning].
407375
408
-When a user with <b>WriteTrusted Forum</b> capability (<tt>4</tt>)
376
+When a user with <b>WrTForum</b> capability
409377
 updates the forum, it happens in the same way except that Fossil skips
410378
 the <tt>private</tt> and <tt>modreq</tt> table insertions.
411379
412380
 When a moderator rejects an update, that artifact is unceremoniously
413381
 removed from the tip of the block chain. This is safe because Fossil
@@ -422,21 +390,21 @@
422390
 Having described all of the work that Fossil performs under the hood on
423391
 behalf of its users, we can now give the short list of work left for the
424392
 repository's administrators and moderators:
425393
426394
 <ol>
427
- <li>Add the <b>Moderate Forum</b> capability (<tt>5</tt>) to any of
395
+ <li>Add the <b>[./caps/ref.html#5 | ModForum]</b> capability to any of
428396
 your users who should have this ability. You don't need to do this
429
- for any user with Setup (<tt>s</tt>) or Admin (<tt>a</tt>)
430
- capability; it's
397
+ for any user with <b>[./caps/ref.html#s | Setup]</b> or
398
+ <b>[./caps/ref.html#a | Admin]</b> capability; it's
431399
 [http://fossil-scm.org/index.html/artifact/b16221ffb736caa2?ln=1246-1257
432400
 | already included].</li>
433401
434402
 <li>When someone updates the forum, an entry will appear in the
435403
 timeline if the type filter is set to "Forum" or "Any Type". If that
436
- user has only the <b>Write Forum</b> capability (<tt>3</tt>), any
437
- other user with the <b>Moderate Forum</b> capability (<tt>5</tt>)
404
+ user has only the <b>WrForum</b> capability, any
405
+ other user with the <b>ModForum</b> capability
438406
 will see a conditional link appear at the top of the main forum
439407
 page: "Moderation Requests". Clicking this takes the moderator to
440408
 the <tt>/modreq</tt> page. A moderator may wish to keep the main
441409
 forum page open in a browser tab, reloading it occasionally to see
442410
 when the "Moderation Requests" link reappears.</li>
443411
--- www/forum.wiki
+++ www/forum.wiki
@@ -74,14 +74,14 @@
74 third-party forum software and mailing list search engines, your
75 links are only valid until the third-party component changes its
76 URL scheme or disappears from the web.
77
78 * <b>Role-Based Access Control:</b> The forum uses the same
79 [https://en.wikipedia.org/wiki/Role-based_access_control | RBAC
80 system] that Fossil uses to control all other repository accesses.
81 The Fossil forum feature simply adds several new fine-grained
82 capability bits to the existing system.
83
84 * <b>Enduring, Open File Format:</b> Since Fossil has an
85 [./fileformat.wiki | open and well-documented file format], your
86 discussion archives are truly that: <em>archives</em>. You are no
87 longer dependent on the lifetime and business model of a
@@ -109,63 +109,37 @@
109
110 <h2 id="setup">Setting up a Fossil Forum</h2>
111
112 <h3 id="caps">Capabilities</h3>
113
114 Fossil forums use the same role-based access control mechanism as
115 for normal Fossil repository logins.
116
117 There are several dedicated forum-related capability bits you can grant
118 a user:
119
120 * <b>Read Forum</b> (<tt>2</tt>): The user may read forum posts.
121
122 * <b>Write Forum</b> (<tt>3</tt>): The user may create new forum
123 threads, reply to existing threads, and edit their own posts. New
124 posts are held for moderation, and they are marked to prevent them
125 from being included in clone and sync operations.
126
127 * <b>WriteTrusted Forum</b> (<tt>4</tt>): Same as <b>Write Forum</b>
128 except that forum updates bypass the [#moderation | moderation and
129 private artifact restrictions].
130
131 * <b>Moderate Forum</b> (<tt>5</tt>): User gets buttons on posts
132 which allow them to either reject or approve posts held for
133 moderation. User also gets access to a page (<tt>/modreq</tt>)
134 showing the list of pending moderation tasks.
135
136 * <b>Supervise Forum</b> (<tt>6</tt>): User can grant or revoke
137 <b>WriteTrusted</b> capability for other users. (Currently
138 unimplemented.)
139
140 * <b>Email Alerts</b> (<tt>7</tt>): User can sign themselves up for
141 email alerts, a.k.a. notifications.
142
143 By default, no Fossil user has permission to use the forums except for
144 users with Setup and Admin capabilities, which get these as part of the
145 large package of other capabilities they get.
146
147 For public Fossil repositories that wish to accept new users without
148 involving a human, go into Admin &rarr; Access and enable the "Allow
149 users to register themselves" setting. You may also wish to give users
150 in the <tt>anonymous</tt> category the Read Forum (2) and Write Forum
151 (3) capabilities: this allows people to post without creating an account
 
 
152 simply by solving [./antibot.wiki | a simple CAPTCHA].
153
154 For a private repository, you probably won't want to give the
155 <tt>anonymous</tt> user any forum access, but you may wish to give the
156 Read Forum capability (2) to users in the <tt>reader</tt> category.
157
158 For either type of repository, you are likely to want to give at least
159 the WriteTrusted capability (4) to users in the <tt>developer</tt>
160 category. If you did not give the Read Forum capability (2) to
161 <tt>anonymous</tt> above, you should give <tt>developer</tt> that
162 capability here if you choose to give it capability 3 or 4.
 
163
164 If you want to use the email alert feature, by default only those
165 users in the Setup and Admin user categories can make use of it. Grant
166 the Email Alerts capability (7) to give others access to this feature.
167 Alternately, you can handle alert signups outside of Fossil, with
168 a Setup or Admin users manually signing users up via Admin &rarr;
169 Notification. You'll want to grant this capability to the
170 <tt>nobody</tt> user category if you want anyone to sign up without any
171 restrictions. Give it to <tt>anonymous</tt> instead if you want the
@@ -174,11 +148,11 @@
174 logins to have this ability. (That's assuming you give one or both of
175 these capabilities to every user on your Fossil repository.)
176
177 By following this advice, you should not need to tediously add
178 capabilities to individual accounts except in atypical cases, such as
179 to grant the Moderate Forum capability (5) to an uncommonly
180 highly-trusted user.
181
182
183 <h3 id="skin">Skin Setup</h3>
184
@@ -210,13 +184,13 @@
210 if {[anycap 23456] || [anoncap 2] || [anoncap 3]} {
211 menulink /forum Forum
212 }
213 </verbatim>
214
215 These rules say that any logged-in user with any forum-related
216 capability (2-6 inclusive, as of this writing) or an anonymous user with
217 read or write capability on the forum (2, 3) will see the "Forum" navbar
218 link, which just takes you to <tt>/forum</tt>.
219
220 The exact code you need here varies depending on which skin you're
221 using. Follow the style you see for the other navbar links.
222
@@ -303,14 +277,11 @@
303
304 Yet, what of the users who will have logins on both repositories? Some
305 users will be trusted with access to the project's main Fossil
306 repository, and these users will probably also participate in the
307 project's Fossil-hosted forum. Fossil has a feature to solve this
308 problem which is probably less well known than it should be, and which
309 has been a feature of Fossil since April of 2011: Admin &rarr;
310 Login-Group. This allows one Fossil repository to recognize users
311 authorized on a different Fossil repository.
312
313
314 <h3 id="alerts">Email Alerts (a.k.a. Notifications)</h3>
315
316 Internet email service has become rather complicated since its initial
@@ -327,20 +298,18 @@
327
328 There are many paths to a repository's Fossil forum:
329
330 <ul>
331 <li>
332 <p>If you're using the default Fossil skin as shipped with Fossil
333 2.7 or one updated to include the changes since 2.6 or prior, there
334 is a Forum button in the navbar which appears for users with any of
335 the forum-related user capabilities: 2 through 6 inclusive for those
336 with repository logins, or caps 2 and 3 for users without a user
337 account but who have solved the Anonymous user CAPTCHA.</p>
338 <p>This button will not appear in the default skin for such users if
339 their browser window is not greater than 1200 pixels wide. The
340 Fossil admin can adjust this limit in the skin's CSS section, down
341 near the bottom in the definition of the `wideonly` style.</p>
342 </li>
343
344 <li>The other stock skins have this button in them as of 2.7 as well,
345 without the screen width restriction, since the navbar in those skins
346 wraps on narrow screens more gracefully than the default skin
@@ -368,11 +337,11 @@
368
369 * create a new post
370 * reply to an existing post
371 * edit a post or reply
372
373 When a person with the normal <b>Write Forum</b> capability (<tt>3</tt>)
374 updates the forum, Fossil saves the update in its block chain, but this
375 update is impermanent because of two other table updates made at the
376 same time:
377
378 <ol>
@@ -386,14 +355,13 @@
386 what causes Fossil to leave out the Reply button when rendering that
387 post's HTML in the forum's web interface.</li>
388 </ol>
389
390 When a moderator approves an update, Fossil deletes these table entries,
391 making the update semi-permanent. This changes how Fossil renders the
392 HTML for that update. It also means the artifact will now sync to
393 clones, if the sync is done by a user with <b>Check-Out</b> capability
394 (<tt>o</tt>).
395
396 When a forum user edits a moderator-approved artifact, what actually
397 happens under the hood is that Fossil writes another artifact to the
398 repository which refers to the original version as its parent, causing
399 Fossil UI to present the new version instead of the original. The
@@ -403,11 +371,11 @@
403
404 When you "Delete" a moderator-approved post or reply through Fossil UI,
405 it's actually an edit with blank replacement content. The only way to
406 truly delete such artifacts is through [./shunning.wiki | shunning].
407
408 When a user with <b>WriteTrusted Forum</b> capability (<tt>4</tt>)
409 updates the forum, it happens in the same way except that Fossil skips
410 the <tt>private</tt> and <tt>modreq</tt> table insertions.
411
412 When a moderator rejects an update, that artifact is unceremoniously
413 removed from the tip of the block chain. This is safe because Fossil
@@ -422,21 +390,21 @@
422 Having described all of the work that Fossil performs under the hood on
423 behalf of its users, we can now give the short list of work left for the
424 repository's administrators and moderators:
425
426 <ol>
427 <li>Add the <b>Moderate Forum</b> capability (<tt>5</tt>) to any of
428 your users who should have this ability. You don't need to do this
429 for any user with Setup (<tt>s</tt>) or Admin (<tt>a</tt>)
430 capability; it's
431 [http://fossil-scm.org/index.html/artifact/b16221ffb736caa2?ln=1246-1257
432 | already included].</li>
433
434 <li>When someone updates the forum, an entry will appear in the
435 timeline if the type filter is set to "Forum" or "Any Type". If that
436 user has only the <b>Write Forum</b> capability (<tt>3</tt>), any
437 other user with the <b>Moderate Forum</b> capability (<tt>5</tt>)
438 will see a conditional link appear at the top of the main forum
439 page: "Moderation Requests". Clicking this takes the moderator to
440 the <tt>/modreq</tt> page. A moderator may wish to keep the main
441 forum page open in a browser tab, reloading it occasionally to see
442 when the "Moderation Requests" link reappears.</li>
443
--- www/forum.wiki
+++ www/forum.wiki
@@ -74,14 +74,14 @@
74 third-party forum software and mailing list search engines, your
75 links are only valid until the third-party component changes its
76 URL scheme or disappears from the web.
77
78 * <b>Role-Based Access Control:</b> The forum uses the same
79 [./caps/ | capability-based access control
80 system] that Fossil uses to control all other repository accesses.
81 The Fossil forum feature simply adds [./caps/ref.html#2 | several new fine-grained
82 capabilities] to the existing system.
83
84 * <b>Enduring, Open File Format:</b> Since Fossil has an
85 [./fileformat.wiki | open and well-documented file format], your
86 discussion archives are truly that: <em>archives</em>. You are no
87 longer dependent on the lifetime and business model of a
@@ -109,63 +109,37 @@
109
110 <h2 id="setup">Setting up a Fossil Forum</h2>
111
112 <h3 id="caps">Capabilities</h3>
113
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
114 By default, no Fossil user has permission to use the forums except for
115 users with Setup and Admin capabilities, which get these as part of the
116 large package of other capabilities they get.
117
118 For public Fossil repositories that wish to accept new users without
119 involving a human, go into Admin &rarr; Access and enable the "Allow
120 users to register themselves" setting. You may also wish to give users
121 in [./caps/#ucat | the <tt>anonymous</tt> user category] the
122 <b>[./caps/ref.html#2 | RdForum]</b> and
123 <b>[./caps/ref.html#3 | WrForum]</b>
124 capabilities: this allows people to post without creating an account
125 simply by solving [./antibot.wiki | a simple CAPTCHA].
126
127 For a private repository, you probably won't want to give the
128 <tt>anonymous</tt> user any forum access, but you may wish to give the
129 <b>RdForum</b> capability to users in the <tt>reader</tt> category.
130
131 For either type of repository, you are likely to want to give at least
132 the <b>[./caps/ref.html#4 | WrTForum]</b> capability to users in the <tt>developer</tt>
133 category. If you did not give the <b>RdForum</b> capability to
134 <tt>anonymous</tt> above, you should give <tt>developer</tt> that
135 capability here if you choose to give it <b>WrForum</b> or
136 <b>WrTForum</b> capability.
137
138 If you want to use the email alert feature, by default only those
139 users in the Setup and Admin user categories can make use of it. Grant
140 the <b>[./caps/ref.html#7 | EmailAlert]</b> capability to give others access to this feature.
141 Alternately, you can handle alert signups outside of Fossil, with
142 a Setup or Admin users manually signing users up via Admin &rarr;
143 Notification. You'll want to grant this capability to the
144 <tt>nobody</tt> user category if you want anyone to sign up without any
145 restrictions. Give it to <tt>anonymous</tt> instead if you want the
@@ -174,11 +148,11 @@
148 logins to have this ability. (That's assuming you give one or both of
149 these capabilities to every user on your Fossil repository.)
150
151 By following this advice, you should not need to tediously add
152 capabilities to individual accounts except in atypical cases, such as
153 to grant the <b>[./caps/ref.html#5 | ModForum]</b> capability to an uncommonly
154 highly-trusted user.
155
156
157 <h3 id="skin">Skin Setup</h3>
158
@@ -210,13 +184,13 @@
184 if {[anycap 23456] || [anoncap 2] || [anoncap 3]} {
185 menulink /forum Forum
186 }
187 </verbatim>
188
189 These rules say that any logged-in user with any [./caps/ref.html#2 |
190 forum-related capability] or an anonymous user <b>RdForum</b> or
191 <b>WrForum</b> capability will see the "Forum" navbar
192 link, which just takes you to <tt>/forum</tt>.
193
194 The exact code you need here varies depending on which skin you're
195 using. Follow the style you see for the other navbar links.
196
@@ -303,14 +277,11 @@
277
278 Yet, what of the users who will have logins on both repositories? Some
279 users will be trusted with access to the project's main Fossil
280 repository, and these users will probably also participate in the
281 project's Fossil-hosted forum. Fossil has a feature to solve this
282 problem: [./caps/login-groups.md | login groups].
 
 
 
283
284
285 <h3 id="alerts">Email Alerts (a.k.a. Notifications)</h3>
286
287 Internet email service has become rather complicated since its initial
@@ -327,20 +298,18 @@
298
299 There are many paths to a repository's Fossil forum:
300
301 <ul>
302 <li>
303 If you're using the default Fossil skin as shipped with Fossil
304 2.7+ or one [#skin | updated] to support it, there
305 is a Forum button in the navbar which appears for users able to
306 access the forum. With the default skin, that button will only
307 appear if the user's browser window is at least
308 1200 pixels wide. The
 
 
309 Fossil admin can adjust this limit in the skin's CSS section, down
310 near the bottom in the definition of the `wideonly` style.
311 </li>
312
313 <li>The other stock skins have this button in them as of 2.7 as well,
314 without the screen width restriction, since the navbar in those skins
315 wraps on narrow screens more gracefully than the default skin
@@ -368,11 +337,11 @@
337
338 * create a new post
339 * reply to an existing post
340 * edit a post or reply
341
342 When a person with the normal <b>WrForum</b> capability
343 updates the forum, Fossil saves the update in its block chain, but this
344 update is impermanent because of two other table updates made at the
345 same time:
346
347 <ol>
@@ -386,14 +355,13 @@
355 what causes Fossil to leave out the Reply button when rendering that
356 post's HTML in the forum's web interface.</li>
357 </ol>
358
359 When a moderator approves an update, Fossil deletes these table entries,
360 making the update [./shunning.wiki | semi-permanent]. This changes how Fossil renders the
361 HTML for that update. It also means the artifact will now sync to
362 users with <b>[./caps/ref.html#g | Clone]</b> capability.
 
363
364 When a forum user edits a moderator-approved artifact, what actually
365 happens under the hood is that Fossil writes another artifact to the
366 repository which refers to the original version as its parent, causing
367 Fossil UI to present the new version instead of the original. The
@@ -403,11 +371,11 @@
371
372 When you "Delete" a moderator-approved post or reply through Fossil UI,
373 it's actually an edit with blank replacement content. The only way to
374 truly delete such artifacts is through [./shunning.wiki | shunning].
375
376 When a user with <b>WrTForum</b> capability
377 updates the forum, it happens in the same way except that Fossil skips
378 the <tt>private</tt> and <tt>modreq</tt> table insertions.
379
380 When a moderator rejects an update, that artifact is unceremoniously
381 removed from the tip of the block chain. This is safe because Fossil
@@ -422,21 +390,21 @@
390 Having described all of the work that Fossil performs under the hood on
391 behalf of its users, we can now give the short list of work left for the
392 repository's administrators and moderators:
393
394 <ol>
395 <li>Add the <b>[./caps/ref.html#5 | ModForum]</b> capability to any of
396 your users who should have this ability. You don't need to do this
397 for any user with <b>[./caps/ref.html#s | Setup]</b> or
398 <b>[./caps/ref.html#a | Admin]</b> capability; it's
399 [http://fossil-scm.org/index.html/artifact/b16221ffb736caa2?ln=1246-1257
400 | already included].</li>
401
402 <li>When someone updates the forum, an entry will appear in the
403 timeline if the type filter is set to "Forum" or "Any Type". If that
404 user has only the <b>WrForum</b> capability, any
405 other user with the <b>ModForum</b> capability
406 will see a conditional link appear at the top of the main forum
407 page: "Moderation Requests". Clicking this takes the moderator to
408 the <tt>/modreq</tt> page. A moderator may wish to keep the main
409 forum page open in a browser tab, reloading it occasionally to see
410 when the "Moderation Requests" link reappears.</li>
411
M www/fossil-v-git.wiki
+4 -5
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -65,12 +65,11 @@
6565
 [./bugtheory.wiki | ticketing &amp; bug tracking],
6666
 [./embeddeddoc.wiki | embedded documentation],
6767
 [./event.wiki | technical notes], and a [./forum.wiki | web forum],
6868
 all within a single nicely-designed [./customskin.md|skinnable] web
6969
 [/help?cmd=ui|UI],
70
-protected by a fine-grained
71
-[https://en.wikipedia.org/wiki/Role-based_access_control|role-based
70
+protected by [./caps/ | a fine-grained role-based
7271
 access control system].
7372
 These additional capabilities are available for Git as 3rd-party
7473
 add-ons, but with Fossil they are integrated into
7574
 the design. One way to describe Fossil is that it is
7675
 "[https://github.com/ | GitHub]-in-a-box."
@@ -325,13 +324,13 @@
325324
 automatically synchronized up to the central repository; there is no
326325
 "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator
327326
 and lieutenants]" hierarchy as with Linux kernel contributions. D.
328327
 Richard Hipp rarely overrides decisions made by those he has trusted
329328
 with commit access on his repositories. Fossil allows you to give
330
- [/doc/trunk/www/admin-v-setup.md|some users] more power over what
331
- they can do with the repository, but Fossil does not otherwise
332
- directly support the enforcement of a development organization's
329
+ [./caps/admin-v-setup.md|some users] more power over what
330
+ they can do with the repository, but Fossil [./caps/index.md#ucap |
331
+ only loosely supports] the enforcement of a development organization's
333332
 social and power hierarchies. Fossil is a great fit for
334333
 [https://en.wikipedia.org/wiki/Flat_organization|flat
335334
 organizations].</p></li>
336335
337336
 <li><p><b>No easy drive-by contributions:</b> Git
338337
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -65,12 +65,11 @@
65 [./bugtheory.wiki | ticketing &amp; bug tracking],
66 [./embeddeddoc.wiki | embedded documentation],
67 [./event.wiki | technical notes], and a [./forum.wiki | web forum],
68 all within a single nicely-designed [./customskin.md|skinnable] web
69 [/help?cmd=ui|UI],
70 protected by a fine-grained
71 [https://en.wikipedia.org/wiki/Role-based_access_control|role-based
72 access control system].
73 These additional capabilities are available for Git as 3rd-party
74 add-ons, but with Fossil they are integrated into
75 the design. One way to describe Fossil is that it is
76 "[https://github.com/ | GitHub]-in-a-box."
@@ -325,13 +324,13 @@
325 automatically synchronized up to the central repository; there is no
326 "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator
327 and lieutenants]" hierarchy as with Linux kernel contributions. D.
328 Richard Hipp rarely overrides decisions made by those he has trusted
329 with commit access on his repositories. Fossil allows you to give
330 [/doc/trunk/www/admin-v-setup.md|some users] more power over what
331 they can do with the repository, but Fossil does not otherwise
332 directly support the enforcement of a development organization's
333 social and power hierarchies. Fossil is a great fit for
334 [https://en.wikipedia.org/wiki/Flat_organization|flat
335 organizations].</p></li>
336
337 <li><p><b>No easy drive-by contributions:</b> Git
338
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -65,12 +65,11 @@
65 [./bugtheory.wiki | ticketing &amp; bug tracking],
66 [./embeddeddoc.wiki | embedded documentation],
67 [./event.wiki | technical notes], and a [./forum.wiki | web forum],
68 all within a single nicely-designed [./customskin.md|skinnable] web
69 [/help?cmd=ui|UI],
70 protected by [./caps/ | a fine-grained role-based
 
71 access control system].
72 These additional capabilities are available for Git as 3rd-party
73 add-ons, but with Fossil they are integrated into
74 the design. One way to describe Fossil is that it is
75 "[https://github.com/ | GitHub]-in-a-box."
@@ -325,13 +324,13 @@
324 automatically synchronized up to the central repository; there is no
325 "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator
326 and lieutenants]" hierarchy as with Linux kernel contributions. D.
327 Richard Hipp rarely overrides decisions made by those he has trusted
328 with commit access on his repositories. Fossil allows you to give
329 [./caps/admin-v-setup.md|some users] more power over what
330 they can do with the repository, but Fossil [./caps/index.md#ucap |
331 only loosely supports] the enforcement of a development organization's
332 social and power hierarchies. Fossil is a great fit for
333 [https://en.wikipedia.org/wiki/Flat_organization|flat
334 organizations].</p></li>
335
336 <li><p><b>No easy drive-by contributions:</b> Git
337
M www/mkindex.tcl
+4 -1
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -9,19 +9,22 @@
99
 set doclist {
1010
 aboutcgi.wiki {How CGI Works In Fossil}
1111
 aboutdownload.wiki {How The Download Page Works}
1212
 adding_code.wiki {Adding New Features To Fossil}
1313
 adding_code.wiki {Hacking Fossil}
14
- admin-v-setup.md {The Differences Between the Setup and Admin User Capabilities}
1514
 alerts.md {Email Alerts And Notifications}
1615
 antibot.wiki {Defense against Spiders and Bots}
1716
 backoffice.md {The "Backoffice" mechanism of Fossil}
1817
 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
1918
 blockchain.md {Fossil As Blockchain}
2019
 branching.wiki {Branching, Forking, Merging, and Tagging}
2120
 bugtheory.wiki {Bug Tracking In Fossil}
2221
 build.wiki {Compiling and Installing Fossil}
22
+ caps/ {Administering User Capabilities}
23
+ caps/admin-v-setup.md {Differences Between Setup and Admin Users}
24
+ caps/login-groups.md {Differences Between Setup and Admin Users}
25
+ caps/ref.html {User Capability Reference}
2326
 cgi.wiki {CGI Script Configuration Options}
2427
 changes.wiki {Fossil Changelog}
2528
 checkin_names.wiki {Check-in And Version Names}
2629
 checkin.wiki {Check-in Checklist}
2730
 childprojects.wiki {Child Projects}
2831
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -9,19 +9,22 @@
9 set doclist {
10 aboutcgi.wiki {How CGI Works In Fossil}
11 aboutdownload.wiki {How The Download Page Works}
12 adding_code.wiki {Adding New Features To Fossil}
13 adding_code.wiki {Hacking Fossil}
14 admin-v-setup.md {The Differences Between the Setup and Admin User Capabilities}
15 alerts.md {Email Alerts And Notifications}
16 antibot.wiki {Defense against Spiders and Bots}
17 backoffice.md {The "Backoffice" mechanism of Fossil}
18 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
19 blockchain.md {Fossil As Blockchain}
20 branching.wiki {Branching, Forking, Merging, and Tagging}
21 bugtheory.wiki {Bug Tracking In Fossil}
22 build.wiki {Compiling and Installing Fossil}
 
 
 
 
23 cgi.wiki {CGI Script Configuration Options}
24 changes.wiki {Fossil Changelog}
25 checkin_names.wiki {Check-in And Version Names}
26 checkin.wiki {Check-in Checklist}
27 childprojects.wiki {Child Projects}
28
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -9,19 +9,22 @@
9 set doclist {
10 aboutcgi.wiki {How CGI Works In Fossil}
11 aboutdownload.wiki {How The Download Page Works}
12 adding_code.wiki {Adding New Features To Fossil}
13 adding_code.wiki {Hacking Fossil}
 
14 alerts.md {Email Alerts And Notifications}
15 antibot.wiki {Defense against Spiders and Bots}
16 backoffice.md {The "Backoffice" mechanism of Fossil}
17 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
18 blockchain.md {Fossil As Blockchain}
19 branching.wiki {Branching, Forking, Merging, and Tagging}
20 bugtheory.wiki {Bug Tracking In Fossil}
21 build.wiki {Compiling and Installing Fossil}
22 caps/ {Administering User Capabilities}
23 caps/admin-v-setup.md {Differences Between Setup and Admin Users}
24 caps/login-groups.md {Differences Between Setup and Admin Users}
25 caps/ref.html {User Capability Reference}
26 cgi.wiki {CGI Script Configuration Options}
27 changes.wiki {Fossil Changelog}
28 checkin_names.wiki {Check-in And Version Names}
29 checkin.wiki {Check-in Checklist}
30 childprojects.wiki {Child Projects}
31
M www/permutedindex.html
+16 -7
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -23,11 +23,13 @@
2323
 <li><a href="fiveminutes.wiki">5 Minutes as a Single User &mdash; Up and Running in</a></li>
2424
 <li><a href="fossil-from-msvc.wiki">2010 IDE &mdash; Integrating Fossil in the Microsoft Express</a></li>
2525
 <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li>
2626
 <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li>
2727
 <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li>
28
-<li><a href="admin-v-setup.md">Admin User Capabilities &mdash; The Differences Between the Setup and</a></li>
28
+<li><a href="caps/admin-v-setup.md">Admin Users &mdash; Differences Between Setup and</a></li>
29
+<li><a href="caps/login-groups.md">Admin Users &mdash; Differences Between Setup and</a></li>
30
+<li><a href="caps/"><b>Administering User Capabilities</b></a></li>
2931
 <li><a href="copyright-release.html">Agreement &mdash; Contributor License</a></li>
3032
 <li><a href="alerts.md">Alerts And Notifications &mdash; Email</a></li>
3133
 <li><a href="delta_encoder_algorithm.wiki">Algorithm &mdash; Fossil Delta Encoding</a></li>
3234
 <li><a href="blame.wiki">Algorithm Of Fossil &mdash; The Annotate/Blame</a></li>
3335
 <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil &mdash; The</a></li>
@@ -35,19 +37,21 @@
3537
 <li><a href="faq.wiki">Asked Questions &mdash; Frequently</a></li>
3638
 <li><a href="password.wiki">Authentication &mdash; Password Management And</a></li>
3739
 <li><a href="backoffice.md">Backoffice mechanism of Fossil &mdash; The</a></li>
3840
 <li><a href="fossil_prompt.wiki">Bash Prompt &mdash; Fossilized</a></li>
3941
 <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li>
42
+<li><a href="caps/admin-v-setup.md">Between Setup and Admin Users &mdash; Differences</a></li>
43
+<li><a href="caps/login-groups.md">Between Setup and Admin Users &mdash; Differences</a></li>
4044
 <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 &mdash; Hash Policy: Choosing</a></li>
41
-<li><a href="admin-v-setup.md">Between the Setup and Admin User Capabilities &mdash; The Differences</a></li>
4245
 <li><a href="blockchain.md">Blockchain &mdash; Fossil As</a></li>
4346
 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
4447
 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
4548
 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
4649
 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
4750
 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
48
-<li><a href="admin-v-setup.md">Capabilities &mdash; The Differences Between the Setup and Admin User</a></li>
51
+<li><a href="caps/">Capabilities &mdash; Administering User</a></li>
52
+<li><a href="caps/ref.html">Capability Reference &mdash; User</a></li>
4953
 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
5054
 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
5155
 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
5256
 <li><a href="aboutcgi.wiki">CGI Works In Fossil &mdash; How</a></li>
5357
 <li><a href="changes.wiki">Changelog &mdash; Fossil</a></li>
@@ -86,11 +90,12 @@
8690
 <li><a href="private.wiki">Deleting Private Branches &mdash; Creating, Syncing, and</a></li>
8791
 <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm &mdash; Fossil</a></li>
8892
 <li><a href="delta_format.wiki">Delta Format &mdash; Fossil</a></li>
8993
 <li><a href="tech_overview.wiki">Design And Implementation Of Fossil &mdash; A Technical Overview Of The</a></li>
9094
 <li><a href="theory1.wiki">Design Of The Fossil DVCS &mdash; Thoughts On The</a></li>
91
-<li><a href="admin-v-setup.md">Differences Between the Setup and Admin User Capabilities &mdash; The</a></li>
95
+<li><a href="caps/admin-v-setup.md"><b>Differences Between Setup and Admin Users</b></a></li>
96
+<li><a href="caps/login-groups.md"><b>Differences Between Setup and Admin Users</b></a></li>
9297
 <li><a href="embeddeddoc.wiki">Documentation &mdash; Embedded Project</a></li>
9398
 <li><a href="contribute.wiki">Documentation To The Fossil Project &mdash; Contributing Code or</a></li>
9499
 <li><a href="aboutdownload.wiki">Download Page Works &mdash; How The</a></li>
95100
 <li><a href="theory1.wiki">DVCS &mdash; Thoughts On The Design Of The Fossil</a></li>
96101
 <li><a href="quotes.wiki">DVCSes in General &mdash; Quotes: What People Are Saying About Fossil, Git, and</a></li>
@@ -215,10 +220,11 @@
215220
 <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li>
216221
 <li><a href="faq.wiki">Questions &mdash; Frequently Asked</a></li>
217222
 <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li>
218223
 <li><a href="quickstart.wiki">Quick Start Guide &mdash; Fossil</a></li>
219224
 <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li>
225
+<li><a href="caps/ref.html">Reference &mdash; User Capability</a></li>
220226
 <li><a href="image-format-vs-repo-size.md">Repo Size &mdash; Image Format vs Fossil</a></li>
221227
 <li><a href="selfhost.wiki">Repositories &mdash; Fossil Self Hosting</a></li>
222228
 <li><a href="encryptedrepos.wiki">Repositories &mdash; How To Use Encrypted</a></li>
223229
 <li><a href="newrepo.wiki">Repository &mdash; How To Create A New Fossil</a></li>
224230
 <li><a href="selfcheck.wiki">Repository Integrity Self Checks &mdash; Fossil</a></li>
@@ -236,11 +242,12 @@
236242
 <li><a href="selfhost.wiki">Self Hosting Repositories &mdash; Fossil</a></li>
237243
 <li><a href="server/">Server &mdash; How To Configure A Fossil</a></li>
238244
 <li><a href="serverext.wiki">Server Extensions &mdash; CGI</a></li>
239245
 <li><a href="serverext.wiki">Server Using CGI Scripts &mdash; Adding Extensions To A Fossil</a></li>
240246
 <li><a href="settings.wiki">Settings &mdash; Fossil</a></li>
241
-<li><a href="admin-v-setup.md">Setup and Admin User Capabilities &mdash; The Differences Between the</a></li>
247
+<li><a href="caps/admin-v-setup.md">Setup and Admin Users &mdash; Differences Between</a></li>
248
+<li><a href="caps/login-groups.md">Setup and Admin Users &mdash; Differences Between</a></li>
242249
 <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 &mdash; Hash Policy: Choosing Between</a></li>
243250
 <li><a href="hashpolicy.wiki">SHA3-256 &mdash; Hash Policy: Choosing Between SHA1 and</a></li>
244251
 <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li>
245252
 <li><a href="fiveminutes.wiki">Single User &mdash; Up and Running in 5 Minutes as a</a></li>
246253
 <li><a href="../../../sitemap"><b>Site Map</b></a></li>
@@ -263,11 +270,10 @@
263270
 <li><a href="../test/release-checklist.wiki">Testing Checklist &mdash; Pre-Release</a></li>
264271
 <li><a href="th1.md">TH1 Scripting Language &mdash; The</a></li>
265272
 <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li>
266273
 <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li>
267274
 <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li>
268
-<li><a href="admin-v-setup.md"><b>The Differences Between the Setup and Admin User Capabilities</b></a></li>
269275
 <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li>
270276
 <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li>
271277
 <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li>
272278
 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
273279
 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
@@ -281,11 +287,14 @@
281287
 <li><a href="bugtheory.wiki">Tracking In Fossil &mdash; Bug</a></li>
282288
 <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li>
283289
 <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li>
284290
 <li><a href="hints.wiki">Usage Hints &mdash; Fossil Tips And</a></li>
285291
 <li><a href="fiveminutes.wiki">User &mdash; Up and Running in 5 Minutes as a Single</a></li>
286
-<li><a href="admin-v-setup.md">User Capabilities &mdash; The Differences Between the Setup and Admin</a></li>
292
+<li><a href="caps/">User Capabilities &mdash; Administering</a></li>
293
+<li><a href="caps/ref.html"><b>User Capability Reference</b></a></li>
294
+<li><a href="caps/admin-v-setup.md">Users &mdash; Differences Between Setup and Admin</a></li>
295
+<li><a href="caps/login-groups.md">Users &mdash; Differences Between Setup and Admin</a></li>
287296
 <li><a href="serverext.wiki">Using CGI Scripts &mdash; Adding Extensions To A Fossil Server</a></li>
288297
 <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li>
289298
 <li><a href="env-opts.md">Variables and Global Options &mdash; Environment</a></li>
290299
 <li><a href="whyusefossil.wiki">Version Control &mdash; Benefits Of</a></li>
291300
 <li><a href="checkin_names.wiki">Version Names &mdash; Check-in And</a></li>
292301
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -23,11 +23,13 @@
23 <li><a href="fiveminutes.wiki">5 Minutes as a Single User &mdash; Up and Running in</a></li>
24 <li><a href="fossil-from-msvc.wiki">2010 IDE &mdash; Integrating Fossil in the Microsoft Express</a></li>
25 <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li>
26 <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li>
27 <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li>
28 <li><a href="admin-v-setup.md">Admin User Capabilities &mdash; The Differences Between the Setup and</a></li>
 
 
29 <li><a href="copyright-release.html">Agreement &mdash; Contributor License</a></li>
30 <li><a href="alerts.md">Alerts And Notifications &mdash; Email</a></li>
31 <li><a href="delta_encoder_algorithm.wiki">Algorithm &mdash; Fossil Delta Encoding</a></li>
32 <li><a href="blame.wiki">Algorithm Of Fossil &mdash; The Annotate/Blame</a></li>
33 <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil &mdash; The</a></li>
@@ -35,19 +37,21 @@
35 <li><a href="faq.wiki">Asked Questions &mdash; Frequently</a></li>
36 <li><a href="password.wiki">Authentication &mdash; Password Management And</a></li>
37 <li><a href="backoffice.md">Backoffice mechanism of Fossil &mdash; The</a></li>
38 <li><a href="fossil_prompt.wiki">Bash Prompt &mdash; Fossilized</a></li>
39 <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li>
 
 
40 <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 &mdash; Hash Policy: Choosing</a></li>
41 <li><a href="admin-v-setup.md">Between the Setup and Admin User Capabilities &mdash; The Differences</a></li>
42 <li><a href="blockchain.md">Blockchain &mdash; Fossil As</a></li>
43 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
44 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
45 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
46 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
47 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
48 <li><a href="admin-v-setup.md">Capabilities &mdash; The Differences Between the Setup and Admin User</a></li>
 
49 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
50 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
51 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
52 <li><a href="aboutcgi.wiki">CGI Works In Fossil &mdash; How</a></li>
53 <li><a href="changes.wiki">Changelog &mdash; Fossil</a></li>
@@ -86,11 +90,12 @@
86 <li><a href="private.wiki">Deleting Private Branches &mdash; Creating, Syncing, and</a></li>
87 <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm &mdash; Fossil</a></li>
88 <li><a href="delta_format.wiki">Delta Format &mdash; Fossil</a></li>
89 <li><a href="tech_overview.wiki">Design And Implementation Of Fossil &mdash; A Technical Overview Of The</a></li>
90 <li><a href="theory1.wiki">Design Of The Fossil DVCS &mdash; Thoughts On The</a></li>
91 <li><a href="admin-v-setup.md">Differences Between the Setup and Admin User Capabilities &mdash; The</a></li>
 
92 <li><a href="embeddeddoc.wiki">Documentation &mdash; Embedded Project</a></li>
93 <li><a href="contribute.wiki">Documentation To The Fossil Project &mdash; Contributing Code or</a></li>
94 <li><a href="aboutdownload.wiki">Download Page Works &mdash; How The</a></li>
95 <li><a href="theory1.wiki">DVCS &mdash; Thoughts On The Design Of The Fossil</a></li>
96 <li><a href="quotes.wiki">DVCSes in General &mdash; Quotes: What People Are Saying About Fossil, Git, and</a></li>
@@ -215,10 +220,11 @@
215 <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li>
216 <li><a href="faq.wiki">Questions &mdash; Frequently Asked</a></li>
217 <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li>
218 <li><a href="quickstart.wiki">Quick Start Guide &mdash; Fossil</a></li>
219 <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li>
 
220 <li><a href="image-format-vs-repo-size.md">Repo Size &mdash; Image Format vs Fossil</a></li>
221 <li><a href="selfhost.wiki">Repositories &mdash; Fossil Self Hosting</a></li>
222 <li><a href="encryptedrepos.wiki">Repositories &mdash; How To Use Encrypted</a></li>
223 <li><a href="newrepo.wiki">Repository &mdash; How To Create A New Fossil</a></li>
224 <li><a href="selfcheck.wiki">Repository Integrity Self Checks &mdash; Fossil</a></li>
@@ -236,11 +242,12 @@
236 <li><a href="selfhost.wiki">Self Hosting Repositories &mdash; Fossil</a></li>
237 <li><a href="server/">Server &mdash; How To Configure A Fossil</a></li>
238 <li><a href="serverext.wiki">Server Extensions &mdash; CGI</a></li>
239 <li><a href="serverext.wiki">Server Using CGI Scripts &mdash; Adding Extensions To A Fossil</a></li>
240 <li><a href="settings.wiki">Settings &mdash; Fossil</a></li>
241 <li><a href="admin-v-setup.md">Setup and Admin User Capabilities &mdash; The Differences Between the</a></li>
 
242 <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 &mdash; Hash Policy: Choosing Between</a></li>
243 <li><a href="hashpolicy.wiki">SHA3-256 &mdash; Hash Policy: Choosing Between SHA1 and</a></li>
244 <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li>
245 <li><a href="fiveminutes.wiki">Single User &mdash; Up and Running in 5 Minutes as a</a></li>
246 <li><a href="../../../sitemap"><b>Site Map</b></a></li>
@@ -263,11 +270,10 @@
263 <li><a href="../test/release-checklist.wiki">Testing Checklist &mdash; Pre-Release</a></li>
264 <li><a href="th1.md">TH1 Scripting Language &mdash; The</a></li>
265 <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li>
266 <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li>
267 <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li>
268 <li><a href="admin-v-setup.md"><b>The Differences Between the Setup and Admin User Capabilities</b></a></li>
269 <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li>
270 <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li>
271 <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li>
272 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
273 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
@@ -281,11 +287,14 @@
281 <li><a href="bugtheory.wiki">Tracking In Fossil &mdash; Bug</a></li>
282 <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li>
283 <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li>
284 <li><a href="hints.wiki">Usage Hints &mdash; Fossil Tips And</a></li>
285 <li><a href="fiveminutes.wiki">User &mdash; Up and Running in 5 Minutes as a Single</a></li>
286 <li><a href="admin-v-setup.md">User Capabilities &mdash; The Differences Between the Setup and Admin</a></li>
 
 
 
287 <li><a href="serverext.wiki">Using CGI Scripts &mdash; Adding Extensions To A Fossil Server</a></li>
288 <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li>
289 <li><a href="env-opts.md">Variables and Global Options &mdash; Environment</a></li>
290 <li><a href="whyusefossil.wiki">Version Control &mdash; Benefits Of</a></li>
291 <li><a href="checkin_names.wiki">Version Names &mdash; Check-in And</a></li>
292
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -23,11 +23,13 @@
23 <li><a href="fiveminutes.wiki">5 Minutes as a Single User &mdash; Up and Running in</a></li>
24 <li><a href="fossil-from-msvc.wiki">2010 IDE &mdash; Integrating Fossil in the Microsoft Express</a></li>
25 <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li>
26 <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li>
27 <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li>
28 <li><a href="caps/admin-v-setup.md">Admin Users &mdash; Differences Between Setup and</a></li>
29 <li><a href="caps/login-groups.md">Admin Users &mdash; Differences Between Setup and</a></li>
30 <li><a href="caps/"><b>Administering User Capabilities</b></a></li>
31 <li><a href="copyright-release.html">Agreement &mdash; Contributor License</a></li>
32 <li><a href="alerts.md">Alerts And Notifications &mdash; Email</a></li>
33 <li><a href="delta_encoder_algorithm.wiki">Algorithm &mdash; Fossil Delta Encoding</a></li>
34 <li><a href="blame.wiki">Algorithm Of Fossil &mdash; The Annotate/Blame</a></li>
35 <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil &mdash; The</a></li>
@@ -35,19 +37,21 @@
37 <li><a href="faq.wiki">Asked Questions &mdash; Frequently</a></li>
38 <li><a href="password.wiki">Authentication &mdash; Password Management And</a></li>
39 <li><a href="backoffice.md">Backoffice mechanism of Fossil &mdash; The</a></li>
40 <li><a href="fossil_prompt.wiki">Bash Prompt &mdash; Fossilized</a></li>
41 <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li>
42 <li><a href="caps/admin-v-setup.md">Between Setup and Admin Users &mdash; Differences</a></li>
43 <li><a href="caps/login-groups.md">Between Setup and Admin Users &mdash; Differences</a></li>
44 <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 &mdash; Hash Policy: Choosing</a></li>
 
45 <li><a href="blockchain.md">Blockchain &mdash; Fossil As</a></li>
46 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
47 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
48 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
49 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
50 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
51 <li><a href="caps/">Capabilities &mdash; Administering User</a></li>
52 <li><a href="caps/ref.html">Capability Reference &mdash; User</a></li>
53 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
54 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
55 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
56 <li><a href="aboutcgi.wiki">CGI Works In Fossil &mdash; How</a></li>
57 <li><a href="changes.wiki">Changelog &mdash; Fossil</a></li>
@@ -86,11 +90,12 @@
90 <li><a href="private.wiki">Deleting Private Branches &mdash; Creating, Syncing, and</a></li>
91 <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm &mdash; Fossil</a></li>
92 <li><a href="delta_format.wiki">Delta Format &mdash; Fossil</a></li>
93 <li><a href="tech_overview.wiki">Design And Implementation Of Fossil &mdash; A Technical Overview Of The</a></li>
94 <li><a href="theory1.wiki">Design Of The Fossil DVCS &mdash; Thoughts On The</a></li>
95 <li><a href="caps/admin-v-setup.md"><b>Differences Between Setup and Admin Users</b></a></li>
96 <li><a href="caps/login-groups.md"><b>Differences Between Setup and Admin Users</b></a></li>
97 <li><a href="embeddeddoc.wiki">Documentation &mdash; Embedded Project</a></li>
98 <li><a href="contribute.wiki">Documentation To The Fossil Project &mdash; Contributing Code or</a></li>
99 <li><a href="aboutdownload.wiki">Download Page Works &mdash; How The</a></li>
100 <li><a href="theory1.wiki">DVCS &mdash; Thoughts On The Design Of The Fossil</a></li>
101 <li><a href="quotes.wiki">DVCSes in General &mdash; Quotes: What People Are Saying About Fossil, Git, and</a></li>
@@ -215,10 +220,11 @@
220 <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li>
221 <li><a href="faq.wiki">Questions &mdash; Frequently Asked</a></li>
222 <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li>
223 <li><a href="quickstart.wiki">Quick Start Guide &mdash; Fossil</a></li>
224 <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li>
225 <li><a href="caps/ref.html">Reference &mdash; User Capability</a></li>
226 <li><a href="image-format-vs-repo-size.md">Repo Size &mdash; Image Format vs Fossil</a></li>
227 <li><a href="selfhost.wiki">Repositories &mdash; Fossil Self Hosting</a></li>
228 <li><a href="encryptedrepos.wiki">Repositories &mdash; How To Use Encrypted</a></li>
229 <li><a href="newrepo.wiki">Repository &mdash; How To Create A New Fossil</a></li>
230 <li><a href="selfcheck.wiki">Repository Integrity Self Checks &mdash; Fossil</a></li>
@@ -236,11 +242,12 @@
242 <li><a href="selfhost.wiki">Self Hosting Repositories &mdash; Fossil</a></li>
243 <li><a href="server/">Server &mdash; How To Configure A Fossil</a></li>
244 <li><a href="serverext.wiki">Server Extensions &mdash; CGI</a></li>
245 <li><a href="serverext.wiki">Server Using CGI Scripts &mdash; Adding Extensions To A Fossil</a></li>
246 <li><a href="settings.wiki">Settings &mdash; Fossil</a></li>
247 <li><a href="caps/admin-v-setup.md">Setup and Admin Users &mdash; Differences Between</a></li>
248 <li><a href="caps/login-groups.md">Setup and Admin Users &mdash; Differences Between</a></li>
249 <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 &mdash; Hash Policy: Choosing Between</a></li>
250 <li><a href="hashpolicy.wiki">SHA3-256 &mdash; Hash Policy: Choosing Between SHA1 and</a></li>
251 <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li>
252 <li><a href="fiveminutes.wiki">Single User &mdash; Up and Running in 5 Minutes as a</a></li>
253 <li><a href="../../../sitemap"><b>Site Map</b></a></li>
@@ -263,11 +270,10 @@
270 <li><a href="../test/release-checklist.wiki">Testing Checklist &mdash; Pre-Release</a></li>
271 <li><a href="th1.md">TH1 Scripting Language &mdash; The</a></li>
272 <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li>
273 <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li>
274 <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li>
 
275 <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li>
276 <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li>
277 <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li>
278 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
279 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
@@ -281,11 +287,14 @@
287 <li><a href="bugtheory.wiki">Tracking In Fossil &mdash; Bug</a></li>
288 <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li>
289 <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li>
290 <li><a href="hints.wiki">Usage Hints &mdash; Fossil Tips And</a></li>
291 <li><a href="fiveminutes.wiki">User &mdash; Up and Running in 5 Minutes as a Single</a></li>
292 <li><a href="caps/">User Capabilities &mdash; Administering</a></li>
293 <li><a href="caps/ref.html"><b>User Capability Reference</b></a></li>
294 <li><a href="caps/admin-v-setup.md">Users &mdash; Differences Between Setup and Admin</a></li>
295 <li><a href="caps/login-groups.md">Users &mdash; Differences Between Setup and Admin</a></li>
296 <li><a href="serverext.wiki">Using CGI Scripts &mdash; Adding Extensions To A Fossil Server</a></li>
297 <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li>
298 <li><a href="env-opts.md">Variables and Global Options &mdash; Environment</a></li>
299 <li><a href="whyusefossil.wiki">Version Control &mdash; Benefits Of</a></li>
300 <li><a href="checkin_names.wiki">Version Names &mdash; Check-in And</a></li>
301
M www/server/index.html
+5 -5
--- www/server/index.html
+++ www/server/index.html
@@ -77,11 +77,11 @@
7777
 minimum recommended preparation steps:</p>
7878
7979
 <ol>
8080
 <li><p>Fossil creates only one user in a <a
8181
 href="$ROOT/help?cmd=new">new repository</a> and gives it the <a
82
- href="../admin-v-setup.md">all-powerful Setup capability</a>. (“s”)
82
+ href="../caps/admin-v-setup.md#apsu">all-powerful Setup capability</a>.
8383
 The 10-digit random password generated for that user is fairly strong
8484
 against remote attack, even without explicit password guess rate
8585
 limiting, but because that user has so much power, you may want to
8686
 give it a much stronger password under Admin → Users.</a></li>
8787
@@ -274,14 +274,14 @@
274274
 <p>After the server is up and running, log into it as the Setup user and
275275
 visit the Admin menu to finish configuring that repository for
276276
 service:</p>
277277
278278
 <ol>
279
- <li><p>Add user accounts for your other team members. Use the
280
- pre-defined user capabilities to define access policies rather than
281
- give out those same set of capabilities redundantly to each
282
- user.</p></li>
279
+ <li><p>Add user accounts for your other team members. Use <a
280
+ href="../caps/index.md#ucat">categories</a> to define access policies
281
+ rather than redundantly give each new user the same <a
282
+ href="../caps/index.md#ucap">individual capabilities</a>.</p></li>
283283
284284
 <li><p>Test access to the repository from each category of non-Setup
285285
 user that you created. You may have to give your user categories some
286286
 overlooked capabilities, particularly if you followed <a
287287
 href="#prep">our earlier advice</a> to take the repository private
288288
--- www/server/index.html
+++ www/server/index.html
@@ -77,11 +77,11 @@
77 minimum recommended preparation steps:</p>
78
79 <ol>
80 <li><p>Fossil creates only one user in a <a
81 href="$ROOT/help?cmd=new">new repository</a> and gives it the <a
82 href="../admin-v-setup.md">all-powerful Setup capability</a>. (“s”)
83 The 10-digit random password generated for that user is fairly strong
84 against remote attack, even without explicit password guess rate
85 limiting, but because that user has so much power, you may want to
86 give it a much stronger password under Admin → Users.</a></li>
87
@@ -274,14 +274,14 @@
274 <p>After the server is up and running, log into it as the Setup user and
275 visit the Admin menu to finish configuring that repository for
276 service:</p>
277
278 <ol>
279 <li><p>Add user accounts for your other team members. Use the
280 pre-defined user capabilities to define access policies rather than
281 give out those same set of capabilities redundantly to each
282 user.</p></li>
283
284 <li><p>Test access to the repository from each category of non-Setup
285 user that you created. You may have to give your user categories some
286 overlooked capabilities, particularly if you followed <a
287 href="#prep">our earlier advice</a> to take the repository private
288
--- www/server/index.html
+++ www/server/index.html
@@ -77,11 +77,11 @@
77 minimum recommended preparation steps:</p>
78
79 <ol>
80 <li><p>Fossil creates only one user in a <a
81 href="$ROOT/help?cmd=new">new repository</a> and gives it the <a
82 href="../caps/admin-v-setup.md#apsu">all-powerful Setup capability</a>.
83 The 10-digit random password generated for that user is fairly strong
84 against remote attack, even without explicit password guess rate
85 limiting, but because that user has so much power, you may want to
86 give it a much stronger password under Admin → Users.</a></li>
87
@@ -274,14 +274,14 @@
274 <p>After the server is up and running, log into it as the Setup user and
275 visit the Admin menu to finish configuring that repository for
276 service:</p>
277
278 <ol>
279 <li><p>Add user accounts for your other team members. Use <a
280 href="../caps/index.md#ucat">categories</a> to define access policies
281 rather than redundantly give each new user the same <a
282 href="../caps/index.md#ucap">individual capabilities</a>.</p></li>
283
284 <li><p>Test access to the repository from each category of non-Setup
285 user that you created. You may have to give your user categories some
286 overlooked capabilities, particularly if you followed <a
287 href="#prep">our earlier advice</a> to take the repository private
288
M www/serverext.wiki
+2 -2
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -172,11 +172,11 @@
172172
 * FOSSIL_USER
173173
174174
 The FOSSIL_USER string is the name of the logged-in user. This variable
175175
 is missing or is an empty string if the user is not logged in. The
176176
 FOSSIL_CAPABILITIES string is a list of
177
-[/setup_ulist_notes|Fossil capability letters] that
177
+[./caps/ref.html|Fossil capabilities] that
178178
 indicate what permissions the user has on the Fossil repository.
179179
 The FOSSIL_REPOSITORY environment variable gives the filename of the
180180
 Fossil repository that is running. The FOSSIL_URI variable shows the
181181
 prefix of the REQUEST_URI that is the Fossil CGI script, or is an
182182
 empty string if Fossil is being run by some method other than CGI.
@@ -289,13 +289,13 @@
289289
 have been adjusted accordingly and that all resources needed by the
290290
 CGI program are available within the chroot jail.
291291
292292
 If anything goes wrong while trying to process an /ext page, Fossil
293293
 returns a 404 Not Found error with no details. However, if the requester
294
-is logged in as a user that has Debug privilege (capability letter "D")
294
+is logged in as a user that has <b>[./caps/ref.html#D | Debug]</b> capability
295295
 then additional diagnostic information may be included in the output.
296296
297297
 If the /ext page has a "fossil-ext-debug=1" query parameter and if
298298
 the requester is logged in as a user with Debug privilege, then the
299299
 CGI output is returned verbatim, as text/plain and with the original
300300
 header intact. This is useful for trying diagnosing problems with the
301301
 CGI script.
302302
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -172,11 +172,11 @@
172 * FOSSIL_USER
173
174 The FOSSIL_USER string is the name of the logged-in user. This variable
175 is missing or is an empty string if the user is not logged in. The
176 FOSSIL_CAPABILITIES string is a list of
177 [/setup_ulist_notes|Fossil capability letters] that
178 indicate what permissions the user has on the Fossil repository.
179 The FOSSIL_REPOSITORY environment variable gives the filename of the
180 Fossil repository that is running. The FOSSIL_URI variable shows the
181 prefix of the REQUEST_URI that is the Fossil CGI script, or is an
182 empty string if Fossil is being run by some method other than CGI.
@@ -289,13 +289,13 @@
289 have been adjusted accordingly and that all resources needed by the
290 CGI program are available within the chroot jail.
291
292 If anything goes wrong while trying to process an /ext page, Fossil
293 returns a 404 Not Found error with no details. However, if the requester
294 is logged in as a user that has Debug privilege (capability letter "D")
295 then additional diagnostic information may be included in the output.
296
297 If the /ext page has a "fossil-ext-debug=1" query parameter and if
298 the requester is logged in as a user with Debug privilege, then the
299 CGI output is returned verbatim, as text/plain and with the original
300 header intact. This is useful for trying diagnosing problems with the
301 CGI script.
302
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -172,11 +172,11 @@
172 * FOSSIL_USER
173
174 The FOSSIL_USER string is the name of the logged-in user. This variable
175 is missing or is an empty string if the user is not logged in. The
176 FOSSIL_CAPABILITIES string is a list of
177 [./caps/ref.html|Fossil capabilities] that
178 indicate what permissions the user has on the Fossil repository.
179 The FOSSIL_REPOSITORY environment variable gives the filename of the
180 Fossil repository that is running. The FOSSIL_URI variable shows the
181 prefix of the REQUEST_URI that is the Fossil CGI script, or is an
182 empty string if Fossil is being run by some method other than CGI.
@@ -289,13 +289,13 @@
289 have been adjusted accordingly and that all resources needed by the
290 CGI program are available within the chroot jail.
291
292 If anything goes wrong while trying to process an /ext page, Fossil
293 returns a 404 Not Found error with no details. However, if the requester
294 is logged in as a user that has <b>[./caps/ref.html#D | Debug]</b> capability
295 then additional diagnostic information may be included in the output.
296
297 If the /ext page has a "fossil-ext-debug=1" query parameter and if
298 the requester is logged in as a user with Debug privilege, then the
299 CGI output is returned verbatim, as text/plain and with the original
300 header intact. This is useful for trying diagnosing problems with the
301 CGI script.
302

Keyboard Shortcuts

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