Small and lightweight cloud storage written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/slcl/atom?h=libweb-configure 2026-02-13T06:55:08+00:00 2026-02-13T06:55:08+00:00 Xavier Del Campo Romero xavi92@disroot.org 2026-02-12T22:02:08+00:00 urn:sha1:568eaa63cf3b7a8a7fa2caf126f103f1c63493dd 2026-02-13T06:55:08+00:00 Xavier Del Campo Romero xavi92@disroot.org 2026-02-12T21:49:08+00:00 urn:sha1:712c762bec81ef56d83f2a7ab05f7dba1ecf9021 2025-10-10T23:20:02+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-10T23:20:02+00:00 urn:sha1:a53f6b3975026aeb9f7e0a524f4dfd1cd81dff25 This was a leftover from the following commit: commit 10e42591ac72285736d5cc4ee5e7c2f68dbf1e4b Author: Xavier Del Campo Romero Date: Wed Oct 8 13:50:52 2025 +0200 Replace OpenSSL with libsodium and argon2id 2025-10-09T21:03:17+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-09T21:03:17+00:00 urn:sha1:f15d534796129c53f2c24bf8eb9b69d686b957b0 2025-10-09T21:03:03+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-09T21:03:03+00:00 urn:sha1:8f21b3e034b65fa82fbd7da8fe841fece21df357 2025-10-08T20:57:00+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-08T20:54:47+00:00 urn:sha1:8d8179d3b412cdd2c1af60539b9aec89631f3fe6 2025-10-08T20:55:44+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-08T11:50:52+00:00 urn:sha1:10e42591ac72285736d5cc4ee5e7c2f68dbf1e4b The SHA256-based password hashing algorithm used by slcl(1) and usergen(1) is considered insecure against several kinds of attacks, including brute force attacks. [1] Therefore, a stronger password hashing algorithm based on the Argon2id key derivation function is now used by default. While OpenSSL does support Argon2id, it is only supported by very recent versions [2], which are still not packaged by most distributions as of the time of this writing. [3] As an alternative to OpenSSL, libsodium [4] had several benefits: - It provides easy-to-use functions for password hashing, base64 encoding/decoding and other cryptographic primitives used by slcl(1) and usergen(1). - It is packaged by most distributions [5], and most often only the patch version differs, which ensures good compatibility across distributions. Unfortunately, and as opposed to OpenSSL, libsodium does not come with command-line tools. Therefore, usergen(1) had to be rewritten in C. In order to maintain backwards compatiblity with existing databases, slcl(1) and usergen(1) shall support the insecure, SHA256-based password hashing algorithm. However, Argon2id shall now be the default choice for usergen(1). [1]: https://security.stackexchange.com/questions/195563/why-is-sha-256-not-good-for-passwords [2]: https://docs.openssl.org/3.3/man7/EVP_KDF-ARGON2/ [3]: https://repology.org/project/openssl/versions [4]: https://www.libsodium.org/ [5]: https://repology.org/project/libsodium/versions 2025-10-08T00:03:05+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-06T21:02:51+00:00 urn:sha1:00dd37604d50cbf3fb27ec0631b4d4b6d2ee893a Thanks to the fdzipstream library [1] and zlib [2], it is possible to generate ZIP files on-the-fly, therefore requiring no extra disk space usage and only a small amount of memory. Unfortunately, as of the time of this writing fdzipstream is not packaged by any distributions yet [3], so it had to be imported as a git submodule as a workaround. While libarchive [4] could be an interesting alternative, writing ZIP files is only supported by very recent versions (>= 3.8.0), which are still not packaged by many distributions [5], either. Moreover, libarchive is a package with several dependencies other than zlib and is significantly larger compared to fdzipstreams, so fdzipstreams was ultimately considered a better fit for this purpose. [1]: https://github.com/CTrabant/fdzipstream.git [2]: http://zlib.net/ [3]: https://repology.org/projects/?search=fdzipstream [4]: https://www.libarchive.org/ [5]: https://repology.org/project/libarchive/versions 2025-09-24T09:03:39+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-22T02:14:41+00:00 urn:sha1:ebb825d3c622f74f0c47a84e1e388b709dd06c7d 2024-05-04T23:07:01+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2024-05-04T23:00:01+00:00 urn:sha1:32af8ddd3d63fe0936f9ae5b6ca09285bed1baff The previous instructions were simply wrong because `cmake ..` would attempt to configure the project from the parent directory, instead of the build directory.