paraslash - network audio streaming tools https://git.tue.mpg.de/cgit/paraslash/atom?h=master 2026-03-17T22:45:43Z 2026-03-17T22:45:43Z Andre Noll maan@tuebingen.mpg.de 2026-03-15T14:57:29Z urn:sha1:ea0cecf96e08c489fdcc94d046019f4ce46f58e2 Generated with sed -i 's|Copyright.*Andre Noll.*|SPDX-License-Identifier: GPL-2.0 */|g' *.c *.h followed by manually tweaking the result a bit. No license change intended. 2025-10-08T18:58:23Z Andre Noll maan@tuebingen.mpg.de 2025-06-16T18:04:22Z urn:sha1:0be024717a52a0514a18053d635e7600a39410b9 The new file commend for crypt.h, and a few minor improvements in the same file. No changes to openssl.c and gcrypt.c because those do not contain any doxygen comments. Also crypt_common.c is left untouched because this file received its dose of dedox earlier. 2025-05-22T17:08:23Z Andre Noll maan@tuebingen.mpg.de 2025-05-18T18:31:33Z urn:sha1:cb041d0305b8aeda8130f1febd7c31dd269ea83a Now that sha1 is no longer supported, the hash2 naming has become meaningless. Rename it back to "hash". 2025-05-22T17:08:00Z Andre Noll maan@tuebingen.mpg.de 2025-05-18T18:17:12Z urn:sha1:d39156c0e5a6a90fb163cc3fa27d33dbacf6f20e Server and client prefer sha256 in the authentication protocol since paraslash-0.7.0, while 0.6.x clients and servers only know about sha1. This patch drops the compatibility code which enabled old clients to connect to new servers and vice versa. Now the client code no longer checks whether the sha256 feature is supported, but requests and uses the feature unconditionally. The server still announces the sha256 feature and accepts the corresponding feature request, but uses sha256 unconditionally. With this approach older 0.7.x clients are still compatible to current server versions and current clients can still talk to servers running older 0.7.x versions. 2024-05-16T23:36:55Z Andre Noll maan@tuebingen.mpg.de 2023-05-07T16:01:43Z urn:sha1:e15f70f41d691fc1e6cc82fb398429cdb3444342 This complements the previous commit which made the analogous change for public encryption. Passing char ** instead of char * to apc_priv_decrypt() allows us to get rid of the magic 1024 constant in client_common.c. 2024-05-16T23:36:55Z Andre Noll maan@tuebingen.mpg.de 2023-05-02T21:56:26Z urn:sha1:84b145f3783f4740c7aa4e223e39aad51e3dec33 Change the encryption routine of the apc API to allocate a suitably sized buffer itself. Currently, the caller has to guess the size of the buffer to pass to the function and we reuse our 4k handshake buffer for that. While 4k is is plenty at the moment, that may change, and it's always better to use the exact size if it is readily available. This is the case here because the required buffer size is just the number of bits of the modulus of the key. 2023-05-11T17:50:22Z Andre Noll maan@tuebingen.mpg.de 2023-05-11T17:50:22Z urn:sha1:ac03b19b1693fbb7b1d558989ac81c79ed1284ae Two fixes for gcc-12 warnings, and another fix for a benign but embarrassing braino in gcrypt.c. * maint: gcrypt: Fix return value of apc_get_pubkey(). error.h: Be more careful with error code masking. mp3_afh: Drop unused fields from struct mp3header. 2023-05-11T17:43:09Z Andre Noll maan@tuebingen.mpg.de 2023-05-08T19:25:30Z urn:sha1:ac2b74b691bd19544660df8b69f89cd6f5323735 The function is supposed to return the key size in bytes, but it returns the number of *bits*. A consequence of this bug is that RSA keys which are too short to encrypt our 128 byte buffer are not rejected as they should be. This is not too serious because we'll fail later during the encryption step. Fix the bug anyway and clarify the documentation of apc_get_pubkey(). 2021-10-21T17:52:40Z Andre Noll maan@tuebingen.mpg.de 2020-03-12T15:06:12Z urn:sha1:e74113b0e1a6ca1c047667218b089362372aa0f0 This adds a second hash function which will replace sha1. Both openssl and libgcrypt support sha256, so it is easy to do. There are no users of the new functions so far, so this patch has no effect yet. 2020-07-11T17:26:31Z Andre Noll maan@tuebingen.mpg.de 2020-03-12T14:32:20Z urn:sha1:df0826fceedf79b2bd4a90561acdf79bcc578ba8 This way, we get a warning when the name of the function changes but the comment is left unmodified.