Small and lightweight cloud storage written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/slcl/atom?h=decode-url 2023-10-19T15:35:39+00:00 2023-10-19T15:35:39+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-19T13:44:06+00:00 urn:sha1:fc3db3927747fc98fb1378f46f232ef932b773e0 No changes must be committed to the database if mkdir(1) fails. 2023-10-19T15:35:38+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-19T13:34:24+00:00 urn:sha1:8b24f8dcbbee5e888a32044c9c06eb4eff690a0e 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. 2023-09-15T23:00:14+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-15T22:57:34+00:00 urn:sha1:bec528a979ccadbd6687ee6679cf4b43771db586 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. 2023-09-15T23:00:05+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-15T22:28:19+00:00 urn:sha1:18bd0d83bec9fe636446b994553dc2fa99dd0530 xxd(1) is closely related to vim(1), might not be available under some POSIX systems. 2023-09-15T22:59:46+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-15T22:40:22+00:00 urn:sha1:d8f683d9ca604f6a0cd04a42738e55f77a89f06e 2023-05-28T10:07:37+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-05-28T10:07:22+00:00 urn:sha1:20afa79038ec04e8a222d384410efec74ac40931 2023-05-18T18:02:55+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-05-18T18:02:55+00:00 urn:sha1:83b00b2cda355744fa7d7faac4440198e9f33fad 2023-05-01T02:13:25+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-04-30T21:25:43+00:00 urn:sha1:291d951ee1428955179a5f3ed4435c1538045651 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. 2023-03-16T00:55:22+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-03-16T00:53:33+00:00 urn:sha1:f6fd20fdc4def2406614eebb958ef15f6085bb0e 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. 2023-03-06T04:51:49+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-03-06T04:09:56+00:00 urn:sha1:ff8da797a143cb1dfbeb4ce2d2c3e4a1d0c2e56a 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.