paraslash/crypt_common.c, branch nextparaslash - network audio streaming toolshttps://git.tue.mpg.de/cgit/paraslash/atom?h=next2026-03-17T22:45:43ZSwitch to SPDX identifiers.2026-03-17T22:45:43ZAndre Nollmaan@tuebingen.mpg.de2026-03-15T14:57:29Zurn: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.
Remove support for PEM private keys.2026-01-28T17:09:22ZAndre Nollmaan@tuebingen.mpg.de2025-11-22T22:59:55Zurn:sha1:097d3f307f44be27b7c3031661fe1a31a00b84e1
This gets us rid of a couple of hand-written parsers, which can only be a
good thing. The shortstat says it all...
crypt_common.c: Remove pointless check in decode_public_key().2025-12-17T23:19:58ZAndre Nollmaan@tuebingen.mpg.de2025-11-22T22:46:49Zurn:sha1:a177598eb4698c122c3ff360cc2ddec511f39dcb
This goto is a no-op.
crypt_common.c: Simplify base64_decode().2025-10-11T19:15:55ZAndre Nollmaan@tuebingen.mpg.de2025-09-21T09:43:55Zurn:sha1:b2c8d558ef84c6308feda45c0f8c8fa139f22b38
Neither of the two callers makes use of the "-1 means check for length"
feature of this function. Drop the feature.
Move base64.c into crypt_common.c.2025-10-11T19:15:45ZAndre Nollmaan@tuebingen.mpg.de2025-09-20T20:30:49Zurn:sha1:9245bca803c22a11195d261ce942fa0c788aeff3
Both public functions of base64.c, uudecode() and base64_decode(), are only
called from crypt_common.c. Now they can be made static.
Rename hash2 -> hash.2025-05-22T17:08:23ZAndre Nollmaan@tuebingen.mpg.de2025-05-18T18:31:33Zurn:sha1:cb041d0305b8aeda8130f1febd7c31dd269ea83a
Now that sha1 is no longer supported, the hash2 naming has become meaningless.
Rename it back to "hash".
Remove sha1.2025-05-22T17:08:00ZAndre Nollmaan@tuebingen.mpg.de2025-05-18T18:17:12Zurn: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.
Include regex.h from para.h.2025-05-19T17:35:58ZAndre Nollmaan@tuebingen.mpg.de2025-05-18T20:05:45Zurn:sha1:67388cd4fae0cfd1674aada937f4f4d2faeeee1f
Every .c file includes it anyway.
crypt: Deprecate PEM keys.2023-05-14T14:51:16ZAndre Nollmaan@tuebingen.mpg.de2023-04-29T21:23:32Zurn:sha1:7c014017708662edf612cbc6e153a6246453ba69
Users have been advised since 2018 to create RFC4716 keys (see
commit 9e2b093bed5d), and this has been the default key format for
ssh-keygen(1) for a long time as well. Upgrade the severity of the
existing log message from info to warning to encourage users at
runtime to replace their old keys.
string: Rename para_malloc() -> alloc().2022-07-29T17:22:09ZAndre Nollmaan@tuebingen.mpg.de2021-10-26T18:22:49Zurn:sha1:610cb53b94af8e95326cd44b7845f35cffdb6bf3
Just because it's shorter and matches the naming of the new allocators
we are about to introduce. The bulk of this patch was created with
sed -i 's/para_malloc/alloc/g' *.c *.h yy/mp.y