[santiagomed]

Adds a pair of calls in every binding for a file under a key the app already holds, rather than a file a message carries: a group avatar under the conversation key, as X clients encrypt it, or an app's own files at rest. They write the v0 secretstream file format that 0.5.x encrypt_stream wrote, so files open across both releases, X Android's avatars included.

0.5.x:

encrypted = chat.encrypt_stream(data, key)

Now:

encrypted = chat.encrypt_file_with_key(EncryptFileWithKeyParams(key=key, file=data))

Rust:

// 0.5.x
let encrypted = chat.encrypt_stream(&data, &key)?;
// now
let encrypted = chat.encrypt_file_with_key(&EncryptFileWithKeyParams::new(data, key.to_bytes()))?;

Covers Rust, Python, JS/TS, Go, JVM, .NET and the C ABI, with tests (round trips, released 0.5.0/0.5.2 encrypt_stream fixtures, and a plain-libsodium check), API.md, why.md, every 0.7 migration guide and the CHANGELOG. It also corrects the docs on avatars during key rotation: X clients re-encrypt the avatar on every rotation, so apps should too.

Adds a pair of calls in every binding for a file under a key the app already holds, rather than a file a message carries: a group avatar under the conversation key, as X clients encrypt it, or an app's own files at rest. They write the v0 secretstream file format that 0.5.x encrypt_stream wrote, so files open across both releases, X Android's avatars included.

0.5.x:

encrypted = chat.encrypt_stream(data, key)

Now:

encrypted = chat.encrypt_file_with_key(EncryptFileWithKeyParams(key=key, file=data))

Rust:

// 0.5.x
let encrypted = chat.encrypt_stream(&data, &key)?;
// now
let encrypted = chat.encrypt_file_with_key(&EncryptFileWithKeyParams::new(data, key.to_bytes()))?;

Covers Rust, Python, JS/TS, Go, JVM, .NET and the C ABI, with tests (round trips, released 0.5.0/0.5.2 encrypt_stream fixtures, and a plain-libsodium check), API.md, why.md, every 0.7 migration guide and the CHANGELOG. It also corrects the docs on avatars during key rotation: X clients re-encrypt the avatar on every rotation, so apps should too.

The migration guides, their index and why.md name 0.7.1, the release that carries these calls, in their titles, snippet markers and symbol indexes, and every guide's received-avatar snippet decrypts the image under the change's key version before showing it. decrypt_file_with_key's doc comment, API.md and CRYPTO.md say that an empty file is its 24-byte header alone, which nothing authenticates, so any 24 bytes decrypt to an empty file: a file that can't be empty, such as an avatar, should be rejected when it decrypts to nothing. A test pins that behavior.

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 3 committers have signed the CLA.

✅ santiagomed
❌ cursoragent
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (santiagomed)[https://github.com/santiagomed]
❌ @cursoragent
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}