README.md: Fix broken link to usergen
This commit is contained in:
parent
4cd577afa9
commit
3e95727e27
|
@ -42,7 +42,7 @@ to `slcl`. If required, encryption should be done before uploading e.g.: using
|
|||
- cJSON >= 1.7.15.
|
||||
- [`dynstr`](https://gitea.privatedns.org/xavi92/dynstr)
|
||||
(provided as a `git` submodule).
|
||||
- `xxd` (for [`usergen`](/usergen) only).
|
||||
- `xxd` (for [`usergen`](usergen) only).
|
||||
- CMake (optional).
|
||||
|
||||
### Ubuntu / Debian
|
||||
|
@ -133,16 +133,16 @@ schema:
|
|||
}
|
||||
```
|
||||
|
||||
[`usergen`](/usergen) is an interactive script that consumes a username and
|
||||
[`usergen`](usergen) is an interactive script that consumes a username and
|
||||
password, and writes a JSON object that can be appended to the `users` JSON
|
||||
array in `db.json`. A salt is randomly generated using `openssl` and passwords
|
||||
are hashed multiple times beforehand - see [`usergen`](/usergen) and
|
||||
are hashed multiple times beforehand - see [`usergen`](usergen) and
|
||||
[`auth.c`](/auth.c) for further reference. Also, a random key is generated
|
||||
that is later used to sign HTTP cookies.
|
||||
|
||||
When users authenticate from a web browser, `slcl` sends a SHA256HMAC-signed
|
||||
[JSON Web Token](https://jwt.io), using the random key generated by
|
||||
[`usergen`](/usergen). No session data is kept on the server.
|
||||
[`usergen`](usergen). No session data is kept on the server.
|
||||
|
||||
### Running
|
||||
|
||||
|
|
Loading…
Reference in New Issue