Safer group updates and messages
Decrypted group secrets could leave extra copies in memory or diagnostics. Bad ciphertext, Welcome messages, proposals, update paths, missing local keys, random-number failures, unusual system time, and epoch limits could close the app instead of returning a safe error. Some tree integrity and path-length checks were also not guaranteed in every release path.
For example, a broken group update received from the network must be rejected without closing the messenger, skipping an integrity check, or exposing message bytes in a crash report.
Local fix prepared, verification in progress.
Technical details: openmls 0.8.1 | UMB-117, UMB-118, UMB-120, UMB-121, UMB-125, UMB-128, UMB-129, UMB-130, UMB-131, UMB-132, UMB-133, UMB-134, UMB-135, UMB-136, UMB-137, UMB-138, UMB-139

