xavi/slcl, branch v0.3.1Small and lightweight cloud storage written in C99 and POSIX.1-2008.
https://gitea.privatedns.org/xavi/slcl/atom?h=v0.3.12025-01-23T22:41:12+00:00.gitignore: Fix path for Makefile2025-01-23T22:41:12+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-23T22:39:57+00:00urn:sha1:681005b8f62245816c18f7190bb02078037de200main.c: Require paths with leading '/' on sharing2025-01-23T22:41:03+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-23T22:24:22+00:00urn:sha1:3e618c2d0f1d489e13ed1f45b5a9068936c05743
When sharing, paths must be expressed as an absolute path e.g.:
/path/to/file .
main.c: Forbid sharing non-existing files2025-01-23T22:37:39+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-23T22:21:44+00:00urn:sha1:9752843329a257542c34798d65e829a6cff7764b
So far, slcl would allow to share literally any directory or file, even
if they did not exist, as long as valid credentials were given.
Now, directories cannot be shared, since this is already restricted by
the web interface. This is now considered an invalid request.
On the other hand, attempting to share non-existing files shall now
return a 404 Not Found response to the user.
libweb: Add byte serving2024-11-10T23:08:50+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-11-10T23:08:50+00:00urn:sha1:5c4e226ddcd132c0dfa9a9cf096d3b3f8fc3c171
libweb started to support HTTP/1.1 Range Requests [1] so that large
files can be partially retrieved. In the context of slcl, this is
interesting in order to preview large media files, such as videos, PDFs
or audio files.
[1]: https://httpwg.org/specs/rfc7233.html
Implement directory paging2024-08-28T01:57:27+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-28T01:10:06+00:00urn:sha1:6b7acc7eaf401b2d4fdf615543f4364fc77b9255
This allows directories with many files and directories inside them to
be split into pages, in order to limit resource usage.
Bump libweb to v0.4.12024-08-28T01:57:00+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-28T01:28:08+00:00urn:sha1:49d8e4397a80ab373737b8baf4588bef5bfa717fBump to libweb 0.4.02024-08-22T00:28:25+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-22T00:21:15+00:00urn:sha1:78eff0cfa55606ade2ce494258739514c92994ca
Now, libweb (rightfully) forces applications to handle signals and
introduces handler_notify_close(3) to achieve the desired behaviour.
Additionally, libweb 0.4.0 introduces several bugfixes.
main.c: Fix missing O_TRUNC2024-08-22T00:00:11+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-22T00:00:11+00:00urn:sha1:36dec4c1b495cd13542827e7ab98b7938adb1524
Otherwise, uploaded files meant to overwrite an existing file would not
be updated accordingly if their newer size was smaller.
auth.c: Replace sprintf(3) with snprintf(3)2024-08-21T21:47:17+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-21T21:47:17+00:00urn:sha1:d73097dd74625711dd02d5e3a6cb6bdca5ca8150
Even if this specific use of sprintf(3) was safe because sizeof
sha256_str > (sizeof sha256 * 2), some implementations would consider
sprintf(3) unsafe anyway.
auth.c: Reject empty files2024-06-13T06:25:29+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-06-13T06:25:29+00:00urn:sha1:37c4b2967863fe5ba265a7fefad60dbd96a09f17
It makes no sense to attempt to fopen(3) an empty file and malloc(3)
zero bytes so as to dump it, as dump_db is still meant to fail on empty
files.