v0.2.24

Release notes

This release focuses on bug fixes and stability, with some usability sprinkled on top.

We changed how long NGC announces are stored on nodes (x2) and the announce frequency now scales inversely proportional to number of group peers. This makes them more discoverable and at the same time reduces strain on the network.

Bug fixes where applied all around, but love was given especially to the toxav subsystem.

Digital sovereignty, here to stay.

Bug Fixes

• missing memzero on failure path (968b33f7)
• Don't print strings that can lack \0 without length. (93bde3ea)
• Improve conference teardown memory management. (69e3e4f6)
• e2e fuzzing was setup wrongly and no pkgs where consumed This is because toxcore creates it own new socket/node, not the one created for toxcore. (89c30b01)
• Align group announcement interval with cleanup interval. (9696e90d)
• We now make sure to validate signature keys during handshake (76b90299)
• disable nrvo clang warning for osx ci (efb938b1)
• handle_gc_mod_list() return values in docs (1d79022f)
• LAN_discovery: use interface IP and bitwise masking on Windows (b940c22a)
• crypto: correct assertion message in pack_extended_public_key (d07f10bf)
• events: memory leak when event field alloc fails (daddc7fb)
• msi: invoke error callback on init and push failure paths (39bd5c6d)
• network: check buffer length before reading family in unpack_ip_port (02daf255)
• ngc:
  • don't log bad nicks (82b7a5c4)
  • stale gconn ptr after realloc (ea4bab5c)
• rtp: wrong slot used check could lead to oob Header only frames, with no payload can still occupy a slot. (56a8d289)
• toxav:
  • doubly linked list corruption in call_new when reusing friend numbers (fc4d8629)
  • hold lock during queue destruction (13f5dd88)