mirror/libsignal
0
0
Fork 0
mirror of https://github.com/signalapp/libsignal.git synced 2024-09-19 19:42:19 +02:00
Code
5b4570625b
libsignal/acknowledgments
History
Alex Konradi 5b4570625b
Split types out of libsignal-bridge crate 
Separate `libsignal-bridge` into two crates:
- `libsignal-bridge-types`, which contains types and methods for bridging,
  declares conversion traits, and implements those traits
- `libsignal-bridge`, which defines `extern "C"` functions that get exported
  into the app-language libraries

This will allow creating a second test-only crate, parallel to
`libsignal-bridge`, that can use the same types and macros for exporting
functions.
2024-06-21 16:39:14 -04:00
..
about.toml net: Replace rustls-native-certs with rustls-platform-verifier 2024-04-24 13:14:05 -07:00
acknowledgments.html Split types out of libsignal-bridge crate 2024-06-21 16:39:14 -04:00
acknowledgments.html.hbs acknowledgments: Manually mention NIST's Kyber patent license PDF 2024-02-23 16:56:43 -08:00
acknowledgments.md Split types out of libsignal-bridge crate 2024-06-21 16:39:14 -04:00
acknowledgments.md.hbs acknowledgments: Manually mention NIST's Kyber patent license PDF 2024-02-23 16:56:43 -08:00
acknowledgments.plist Split types out of libsignal-bridge crate 2024-06-21 16:39:14 -04:00
acknowledgments.plist.hbs acknowledgments: Manually mention NIST's Kyber patent license PDF 2024-02-23 16:56:43 -08:00
cargo-about-version Update cargo-about 2024-06-20 12:04:44 -07:00
README.md CI: Include the cargo-about version in the local tools cache key 2023-12-20 14:03:04 -08:00

README.md

This directory contains pre-generated acknowledgments for the Rust dependencies of libsignal. CI enforces that they are kept up to date.

Updating

If you update libsignal's dependencies, you'll need to update this listing. Install cargo-about if you haven't already:

cargo +stable install --locked cargo-about --version $(cat acknowledgments/cargo-about-version)

Then:

  1. Run bin/regenerate_acknowledgments.sh.
  2. Check the HTML output for new "synthesized" entries. This can indicate that the license for a particular dependency was not properly detected.
  3. If there are any unaccounted-for "synthesized" entries, add new "clarify" entries to about.toml.

Apart from the projects in this very repo, there are a few other crates that unavoidably have "synthesized" licenses based on their Cargo manifests:

  • cesu8: Very old crate whose repository contains a license file for the Rust project itself, rather than the crate.
  • curve25519-dalek-derive: Uploaded without a license file, though a license is listed in the Cargo.toml. Not the same as the license of curve25519-dalek.
  • half: Not actually synthesized! Their license file just matches the synthesized text perfectly. A bug in cargo-about, presumably.
  • pqcrypto-*: Uploaded without a license file, though a license is listed in the Cargo.toml for each crate. The Kyber implementations we use are released as Public Domain, so no acknowledgment is necessary.