Fossil SCM

Initial cut at better explanation regarding username/password authentication.

brickviking 2024-10-21 11:04 bv-corrections01
Commit 62077d3fd4e3050e1002e64ec53b5cd341433138365536cc77d8889ee3427124
1 file changed +3 -1
--- www/password.wiki
+++ www/password.wiki
@@ -63,11 +63,13 @@
6363
for "anonymous" uses one-time captchas not persistent passwords.
6464
6565
<h2>Web Interface Authentication</h2>
6666
6767
When a user logs into Fossil using the web interface, the login name
68
-and password are sent in the clear to the server. The server then
68
+and password are sent in the clear to the server. For most modern fossil
69
+server setups with redirect-to-https enabled, this will be protected by the
70
+SSL connection over HTTPS so it cannot be easily viewed. The server then
6971
hashes the password and compares it against the value stored in USER.PW.
7072
If they match, the server sets a cookie on the client to record the
7173
login. This cookie contains a large amount of high-quality randomness
7274
and is thus intractable to guess. The value of the cookie and the IP
7375
address of the client is stored in the USER.COOKIE and USER.IPADDR fields
7476
--- www/password.wiki
+++ www/password.wiki
@@ -63,11 +63,13 @@
63 for "anonymous" uses one-time captchas not persistent passwords.
64
65 <h2>Web Interface Authentication</h2>
66
67 When a user logs into Fossil using the web interface, the login name
68 and password are sent in the clear to the server. The server then
 
 
69 hashes the password and compares it against the value stored in USER.PW.
70 If they match, the server sets a cookie on the client to record the
71 login. This cookie contains a large amount of high-quality randomness
72 and is thus intractable to guess. The value of the cookie and the IP
73 address of the client is stored in the USER.COOKIE and USER.IPADDR fields
74
--- www/password.wiki
+++ www/password.wiki
@@ -63,11 +63,13 @@
63 for "anonymous" uses one-time captchas not persistent passwords.
64
65 <h2>Web Interface Authentication</h2>
66
67 When a user logs into Fossil using the web interface, the login name
68 and password are sent in the clear to the server. For most modern fossil
69 server setups with redirect-to-https enabled, this will be protected by the
70 SSL connection over HTTPS so it cannot be easily viewed. The server then
71 hashes the password and compares it against the value stored in USER.PW.
72 If they match, the server sets a cookie on the client to record the
73 login. This cookie contains a large amount of high-quality randomness
74 and is thus intractable to guess. The value of the cookie and the IP
75 address of the client is stored in the USER.COOKIE and USER.IPADDR fields
76

Keyboard Shortcuts

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