aboutsummaryrefslogtreecommitdiff
path: root/usergen
Commit message (Collapse)AuthorAgeFilesLines
* usergen: Call mkdir(1) before database swapXavier Del Campo Romero2023-10-191-1/+1
| | | | No changes must be committed to the database if mkdir(1) fails.
* usergen: Replace use of non-standard mktemp(1)Xavier Del Campo Romero2023-10-191-1/+8
| | | | | | Despite common use in several POSIX operating systems, mktemp(1) is not defined by POSIX.1-2008, nor even POSIX.1-2017. As long as it is not introduced, m4(1)'s mkstemp can be used with similar effect.
* usergen: Remove dependency against sha256sum(1)Xavier Del Campo Romero2023-09-161-1/+1
| | | | | | sha256sum(1) is a GNU utility that might not be available under some POSIX systems. Since OpenSSL is already a dependency, it makes sense to reuse it to generate SHA256 digests.
* usergen: Remove dependency against xxd(1)Xavier Del Campo Romero2023-09-161-5/+15
| | | | | xxd(1) is closely related to vim(1), might not be available under some POSIX systems.
* usergen: Reject non-numeric, invalid quotaXavier Del Campo Romero2023-09-161-0/+1
|
* usergen: Force newline after password inputXavier Del Campo Romero2023-05-281-0/+2
|
* usergen: Do not print password to ttyXavier Del Campo Romero2023-05-181-0/+5
|
* usergen: Fix wrong password and username usageXavier Del Campo Romero2023-05-011-6/+12
| | | | | | | | | Due to the lack of double quotes, passwords with whitespaces were not passed correctly to printf(1), thus making users not able to log into their account. OTOH, for some reason usernames containing whitespaces made jq(1) complain, so it has been decided not to support them.
* Make usergen a bit more usefulXavier Del Campo Romero2023-03-161-7/+39
| | | | | | So far, usergen printed a JSON object over standard output that had to be manually copied into db.json. Now, this step is done automatically, thanks to jq(1). OTOH, user directory is now also created by usergen.
* Implement user quotaXavier Del Campo Romero2023-03-061-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This feature allows admins to set a specific quota for each user, in MiB. This feature is particularly useful for shared instances, where unlimited user storage might be unfeasible or even dangerous for the server. Also, a nice HTML5 <progress> element has been added to the site that shows how much of the quota has been consumed. If no quota is set, slcl falls back to the default behaviour i.e., assume unlimited storage. Limitations: - While HTTP does specify a Content-Length, which determines the length of the whole request, it does not specify how many files are involved or their individual sizes. - Because of this, if multiple files are uploaded simultaneously, the whole request would be dropped if user quota is exceeded, even if not all files exceeded it. - Also, Content-Length adds the length of some HTTP boilerplate (e.g.: boundaries), but slcl must rely on this before accepting the whole request. In other words, this means some requests might be rejected by slcl because of the extra bytes caused by such boilerplate. - When the quota is exceeded, slcl must close the connection so that the rest of the transfer is cancelled. Unfortunately, this means no HTML can be sent back to the customer to inform about the situation.
* Add usergenXavier Del Campo Romero2023-02-281-0/+29
This script takes a username and password from standard input and generates a JSON object that can be appended to the "users" object in db.json.