Fossil SCM
Removed an incorrect hash result from www/password.wiki, per [forum:3375879e6c3b9d73|forum post 3375879e6c3b9d73].
Commit
2169f323facef6b803b86ecabf5acace4df0c1e3a427ee99ccd756ab4b3b946e
Parent
202cbcf0152c03c…
1 file changed
+4
-5
+4
-5
| --- www/password.wiki | ||
| +++ www/password.wiki | ||
| @@ -26,15 +26,14 @@ | ||
| 26 | 26 | |
| 27 | 27 | <blockquote> |
| 28 | 28 | CE59BB9F186226D80E49D1FA2DB29F935CCA0333/alice/asdfg |
| 29 | 29 | </blockquote> |
| 30 | 30 | |
| 31 | -That hash value is "f1b699cc9af3eeb98e5de244ca7802ae38e77bae". Note | |
| 32 | -that by including the project-code and the login as part of the hash, | |
| 33 | -a different USER.PW value results even if two or more users on the | |
| 34 | -repository select the same "asdfg" password or if user alice reuses the | |
| 35 | -same password on multiple projects. | |
| 31 | +Note that by including the project-code and the login as part of the | |
| 32 | +hash, a different USER.PW value results even if two or more users on | |
| 33 | +the repository select the same "asdfg" password or if user alice | |
| 34 | +reuses the same password on multiple projects. | |
| 36 | 35 | |
| 37 | 36 | Whenever a password is changed using the web interface or using the |
| 38 | 37 | "user" command-line method, the new password is stored using the SHA1 |
| 39 | 38 | encoding. Thus, cleartext passwords will gradually migrate to become |
| 40 | 39 | SHA1 passwords. All remaining cleartext passwords can be converted to |
| 41 | 40 |
| --- www/password.wiki | |
| +++ www/password.wiki | |
| @@ -26,15 +26,14 @@ | |
| 26 | |
| 27 | <blockquote> |
| 28 | CE59BB9F186226D80E49D1FA2DB29F935CCA0333/alice/asdfg |
| 29 | </blockquote> |
| 30 | |
| 31 | That hash value is "f1b699cc9af3eeb98e5de244ca7802ae38e77bae". Note |
| 32 | that by including the project-code and the login as part of the hash, |
| 33 | a different USER.PW value results even if two or more users on the |
| 34 | repository select the same "asdfg" password or if user alice reuses the |
| 35 | same password on multiple projects. |
| 36 | |
| 37 | Whenever a password is changed using the web interface or using the |
| 38 | "user" command-line method, the new password is stored using the SHA1 |
| 39 | encoding. Thus, cleartext passwords will gradually migrate to become |
| 40 | SHA1 passwords. All remaining cleartext passwords can be converted to |
| 41 |
| --- www/password.wiki | |
| +++ www/password.wiki | |
| @@ -26,15 +26,14 @@ | |
| 26 | |
| 27 | <blockquote> |
| 28 | CE59BB9F186226D80E49D1FA2DB29F935CCA0333/alice/asdfg |
| 29 | </blockquote> |
| 30 | |
| 31 | Note that by including the project-code and the login as part of the |
| 32 | hash, a different USER.PW value results even if two or more users on |
| 33 | the repository select the same "asdfg" password or if user alice |
| 34 | reuses the same password on multiple projects. |
| 35 | |
| 36 | Whenever a password is changed using the web interface or using the |
| 37 | "user" command-line method, the new password is stored using the SHA1 |
| 38 | encoding. Thus, cleartext passwords will gradually migrate to become |
| 39 | SHA1 passwords. All remaining cleartext passwords can be converted to |
| 40 |