mirror/libsignal
0
0
Fork 0
mirror of https://github.com/signalapp/libsignal.git synced 2024-09-20 12:02:18 +02:00
Code
ef542e3b9f
libsignal/Cargo.lock

2896 lines
69 KiB
Plaintext
Raw Normal View History

Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
Bump version to v0.8.2
2021-06-28 21:52:57 +02:00
version = 3
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "addr2line"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.20.0"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "f4fa78e18c64fce05e902adecd7a5eed15a5e0a3439f7b0e169f0252214865e3"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
dependencies = [
"gimli",
]
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "aead"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.4.3"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "0b613b8e1e3cf911a086f53f03bf286f52fd7a7258e4fa606f0ef220d39d8877"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
"generic-array",
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "aead"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d122413f284cf2d62fb1b7db97e02edb8cda96d769b16e443a4f6195e35662b0"
dependencies = [
"crypto-common",
"generic-array",
]
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "aes"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.7.5"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "9e8b47f52ea9bae42228d07ec09eb676433d7c4ed1ebdf0f1d1c29ed446f1ab8"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"cipher 0.3.0",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
"cpufeatures",
"opaque-debug",
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "aes"
version = "0.8.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac1f845298e95f983ff1944b728ae08b8cebab80d684f0a832ed0fc74dfa27e2"
dependencies = [
"cfg-if",
"cipher 0.4.4",
"cpufeatures",
"zeroize",
]
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
[[package]]
name = "aes-gcm"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.9.2"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "bc3be92e19a7ef47457b8e6f90707e12b6ac5d20c6f3866584fa3be0787d839f"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"aead 0.4.3",
"aes 0.7.5",
"cipher 0.3.0",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"ctr 0.7.0",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"ghash 0.4.4",
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
"subtle",
]
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "aes-gcm-siv"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
version = "0.11.1"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
checksum = "ae0784134ba9375416d469ec31e7c5f9fa94405049cf08c5ce5b4698be673e0d"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"aead 0.5.2",
"aes 0.8.3",
"cipher 0.4.4",
"ctr 0.9.2",
"polyval 0.6.1",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
"subtle",
"zeroize",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update to prost 0.9
2021-11-28 17:32:32 +01:00
[[package]]
name = "aho-corasick"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.2"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "43f6cb1bf222025340178f382c426f13757b2960e89779dfcb319c32542a5a41"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
dependencies = [
"memchr",
]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "android_system_properties"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
dependencies = [
"libc",
]
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
[[package]]
name = "anes"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b46cbb362ab8752921c97e041f5e366ee6297bd428a31275b9fcf1e380f7299"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
[[package]]
name = "anstyle"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a30da5c5f2d5e72842e00bcb57657162cdabef0931f40e2deb9b4140440cecd"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "anyhow"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.72"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "3b13c32d80ecc7ab747b80c3784bce54ee8a7a0cc4fbda9bf4cda2cf6fe90854"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "argon2"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.5.1"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b2e554a8638bdc1e4eae9984845306cc95f8a9208ba8d49c3859fd958b46774d"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
dependencies = [
"base64ct",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"blake2",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"cpufeatures",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"password-hash",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"zeroize",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "arrayref"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.7"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "6b4930d2cb77ce62f89ee5d5289b4ac049559b1c45539271f5ed4fdc7db34545"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
[[package]]
name = "asn1"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.15.4"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "de594fb2adce376d7955c41e273e1ba22b0476b8763c383362b99c3d78fee593"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
dependencies = [
"asn1_derive",
]
[[package]]
name = "asn1_derive"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.15.4"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "fc6da21a2122ddd982cab7a7a73b961d12398e96c2faae5cd4d62593a5e7342f"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
]
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "async-trait"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.1.72"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "cc6dde6e4ed435a4c1ee4e73592f5ba9da2151af10076cc04858746af9352d09"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
]
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
[[package]]
name = "attest"
version = "0.1.0"
dependencies = [
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"asn1",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 2.3.3",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"boring",
Update boring to restore Android 19 compatibility
2022-08-22 23:20:41 +02:00
"boring-sys",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"chacha20poly1305 0.10.1",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"chrono",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"displaydoc",
"hex",
"hex-literal",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"lazy_static",
"libc",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"log",
"num_enum",
"prost",
"prost-build",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_core",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"serde",
"serde_json",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"snow",
"static_assertions",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"uuid",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"variant_count",
"x25519-dalek",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "autocfg"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
version = "1.1.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "backtrace"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.68"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "4319208da049c43661739c5fade2ba182f09d1dc2299b32298d3a31692b17e12"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
dependencies = [
"addr2line",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"cc",
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
"libc",
"miniz_oxide",
"object",
"rustc-demangle",
]
zkgroup: Add a generate-server-params binary generate-server-params takes existing server params through stdin (base64-encoded) and generates randomness for any new keys have been added since last time. As long as new keys are always added to the end of ServerSecretParams and ServerPublicParams, this allows updating zkgroup without breaking existing credentials.
2021-11-17 22:10:34 +01:00
[[package]]
name = "base64"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.21.2"
zkgroup: Add a generate-server-params binary generate-server-params takes existing server params through stdin (base64-encoded) and generates randomness for any new keys have been added since last time. As long as new keys are always added to the end of ServerSecretParams and ServerPublicParams, this allows updating zkgroup without breaking existing credentials.
2021-11-17 22:10:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "604178f6c5c21f02dc555784810edfb88d34ac2c73b2eae109655649ee73ce3d"
zkgroup: Add a generate-server-params binary generate-server-params takes existing server params through stdin (base64-encoded) and generates randomness for any new keys have been added since last time. As long as new keys are always added to the end of ServerSecretParams and ServerPublicParams, this allows updating zkgroup without breaking existing credentials.
2021-11-17 22:10:34 +01:00
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "base64ct"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c3c1a368f70d6cf7302d78f8f7093da241fb8e8807c05cc9e51a125895a6d5b"
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
[[package]]
name = "bincode"
version = "1.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1f45e9417d87227c7a56d22e471c6206462cba514c7590c09aff4cf6d1ddcad"
dependencies = [
"serde",
]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "bindgen"
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
version = "0.62.0"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
checksum = "c6720a8b7b2d39dd533285ed438d458f65b31b5c257e6ac7bb3d7e82844dd722"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 1.3.2",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"cexpr",
"clang-sys",
"lazy_static",
"lazycell",
"peeking_take_while",
"proc-macro2",
"quote",
"regex",
"rustc-hash",
"shlex",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
]
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "bit-set"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0700ddab506f33b20a03b13996eccd309a48e5ff77d0d95926aa0210fb4e95f1"
dependencies = [
"bit-vec",
]
[[package]]
name = "bit-vec"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349f9b6a179ed607305526ca489b34ad0a41aed5f7980fa90eb03160b69598fb"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "bitflags"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "1.3.2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "bitflags"
version = "2.3.3"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "630be753d4e58660abd17930c71b647fe46c27ea6b63cc59e1e3851406972e42"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "blake2"
version = "0.10.6"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "46502ad458c9a52b69d4d4d32775c788b7a1b85e8bc9d482d92250fc0e3f8efe"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"digest",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "block-buffer"
version = "0.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
dependencies = [
"generic-array",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
name = "block-padding"
version = "0.3.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
checksum = "a8894febbff9f758034a5b8e12d87918f56dfc64a8e1fe757d65e29041538d93"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"generic-array",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "boring"
Update boring This includes - a handful of fixes from upstream - support for building for ARMv7 Linux (thanks, morph027!)
2022-11-09 21:16:28 +01:00
version = "2.1.0"
Update boring for a newer version of BoringSSL
2023-05-12 00:33:56 +02:00
source = "git+https://github.com/signalapp/boring?branch=libsignal#3809a7e1ca2f60a9495620da514f8432f148cde7"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 1.3.2",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"boring-sys",
"foreign-types",
"lazy_static",
"libc",
]
[[package]]
name = "boring-sys"
Update boring This includes - a handful of fixes from upstream - support for building for ARMv7 Linux (thanks, morph027!)
2022-11-09 21:16:28 +01:00
version = "2.1.0"
Update boring for a newer version of BoringSSL
2023-05-12 00:33:56 +02:00
source = "git+https://github.com/signalapp/boring?branch=libsignal#3809a7e1ca2f60a9495620da514f8432f148cde7"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
"bindgen",
"cmake",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "bumpalo"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "3.13.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "a3e2c3daef883ecc1b5d58c15adae93470a91d425f3532ba1695849656af3fc1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "bytemuck"
version = "1.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17febce684fd15d89027105661fec94afb475cb995fbc59d2865198446ba2eea"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "byteorder"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "1.4.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "bytes"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
version = "1.4.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
checksum = "89b2fd2a0dcf38d7971e2194b6b6eebab45ae01067456a7fd93d5547a61b70be"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "cast"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
version = "0.3.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "cbc"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "26b52a9543ae338f279b96b0b9fed9c8093744685043739079ce85cd58f289a6"
dependencies = [
"cipher 0.4.4",
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "cc"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.81"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "6c6b2562119bf28c3439f7f02db99faf0aa1a8cdfe5772a2ee155d32227239f0"
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
dependencies = [
"jobserver",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"libc",
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "cesu8"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d43a04d8753f35258c91f8ec639f792891f748a1edbd759cf1dcea3382ad83c"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "cexpr"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6fac387a98bb7c37292057cffc56d62ecb629900026402633ae9160df93a8766"
dependencies = [
"nom",
]
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "chacha20"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c80e5460aa66fe3b91d40bcbdab953a597b60053e34d684ac6903f863b680a6"
dependencies = [
"cfg-if",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"cipher 0.3.0",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"cpufeatures",
"zeroize",
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "chacha20"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3613f74bd2eac03dad61bd53dbe620703d4371614fe0bc3b9f04dd36fe4e818"
dependencies = [
"cfg-if",
"cipher 0.4.4",
"cpufeatures",
]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "chacha20poly1305"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a18446b09be63d457bbec447509e85f662f32952b035ce892290396bc0b0cff5"
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"aead 0.4.3",
"chacha20 0.8.2",
"cipher 0.3.0",
"poly1305 0.7.2",
"zeroize",
]
[[package]]
name = "chacha20poly1305"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10cd79432192d1c0f4e1a0fef9527696cc039165d729fb41b3f4f4f354c2dc35"
dependencies = [
"aead 0.5.2",
"chacha20 0.9.1",
"cipher 0.4.4",
"poly1305 0.8.0",
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
"zeroize",
]
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
[[package]]
name = "chrono"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.4.26"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "ec837a71355b28f6556dbd569b37b3f363091c0bd4b2e735674521b4c5fd9bc5"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"android-tzdata",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"iana-time-zone",
"js-sys",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"num-traits",
"serde",
"time",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"wasm-bindgen",
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
"winapi",
]
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
[[package]]
name = "ciborium"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.1"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "effd91f6c78e5a4ace8a5d3c0b6bfaec9e2baaef55f3efc00e45fb2e477ee926"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
dependencies = [
"ciborium-io",
"ciborium-ll",
"serde",
]
[[package]]
name = "ciborium-io"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.1"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "cdf919175532b369853f5d5e20b26b43112613fd6fe7aee757e35f7a44642656"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
[[package]]
name = "ciborium-ll"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.1"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "defaa24ecc093c77630e6c15e17c51f5e187bf35ee514f4e2d67baaa96dae22b"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
dependencies = [
"ciborium-io",
"half",
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "cipher"
version = "0.3.0"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
checksum = "7ee52072ec15386f770805afd189a01c8841be8696bed250fa2f13c4c0d6dfb7"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
dependencies = [
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"generic-array",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "cipher"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "773f3b9af64447d2ce9850330c473515014aa235e6a783b02db81ff39e4a3dad"
dependencies = [
"crypto-common",
"inout",
"zeroize",
]
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "clang-sys"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.6.1"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "c688fc74432808e3eb684cae8830a86be1d66a2bd58e1f248ed0960a590baf6f"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"glob",
"libc",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"libloading 0.7.4",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "clap"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "4.3.19"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "5fd304a20bff958a57f04c4e96a2e7594cc4490a0e809cbd48bb6437edaa452d"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"clap_builder",
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
]
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "clap_builder"
version = "4.3.19"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "01c6a3f08f1fe5662a35cfe393aec09c4df95f60ee93b7556505260f75eee9e1"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"anstyle",
"clap_lex",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
[[package]]
name = "clap_lex"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2da6da31387c7e4ef160ffab6d5e7f00c42626fe39aea70a7b0f1773f7dd6c1b"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "cmake"
Downgrade cmake crate to 0.1.48 0.1.49 includes some changes to "improve" cross-compilation that interfere with the "implicit" cross-compilation happening for Windows (using Visual Studio on an "AMD64" host to compile for "ARM64") and for Mac Catalyst (using a macOS SDK to compile for an "ios-macabi" target).
2023-05-31 21:25:58 +02:00
version = "0.1.48"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Downgrade cmake crate to 0.1.48 0.1.49 includes some changes to "improve" cross-compilation that interfere with the "implicit" cross-compilation happening for Windows (using Visual Studio on an "AMD64" host to compile for "ARM64") and for Mac Catalyst (using a macOS SDK to compile for an "ios-macabi" target).
2023-05-31 21:25:58 +02:00
checksum = "e8ad8cef104ac57b68b89df3208164d228503abbdce70f6880ffa3d970e7443a"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
"cc",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "combine"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "4.6.6"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "35ed6e9d84f0b51a7f52daf1c7d71dd136fd7a3f41a8462b8cdb8c78d920fad4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"bytes",
"memchr",
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "convert_case"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6245d59a3e82a7fc217c5828a6692dbc6dfb63a0c8c90495621f7b9d79704a0e"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "core-foundation-sys"
version = "0.8.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e496a50fda8aacccc86d7529e2c1e0892dbd0f898a6b5645b5561b89c3210efa"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "cpufeatures"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.9"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "a17b76ff3a4162b0b27f354a0c87015ddad39d35f9c0c36607a3bdd175dde1f1"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
"libc",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "criterion"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.5.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "f2b12d017a929603d80db1831cd3a24082f8137ce19c69e6447f54f5fc8d692f"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
"anes",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"cast",
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
"ciborium",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"clap",
"criterion-plot",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"is-terminal",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"itertools",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"num-traits",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"once_cell",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"oorandom",
"plotters",
"rayon",
"regex",
"serde",
"serde_derive",
"serde_json",
"tinytemplate",
"walkdir",
]
[[package]]
name = "criterion-plot"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
version = "0.5.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
checksum = "6b50826342786a51a89e2da3a28f1c32b06e387201bc2d19791f622c673706b1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"cast",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"itertools",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "crossbeam-channel"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.5.8"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"crossbeam-utils",
]
[[package]]
name = "crossbeam-deque"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.8.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "ce6fd6f855243022dcecf8702fef0c297d4338e226845fe067f6341ad9fa0cef"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"crossbeam-epoch",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-epoch"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.9.15"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "ae211234986c545741a7dc064309f67ee1e5ad243d0e48335adc0484d960bcc7"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
"autocfg",
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"crossbeam-utils",
"memoffset",
"scopeguard",
]
[[package]]
name = "crossbeam-utils"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.8.16"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "5a22b2d63d4d1dc0b7f1b6b2747dd0088008a9be28b6ddf0b1e7d335e3037294"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"rand_core",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"typenum",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "ctr"
version = "0.7.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "a232f92a03f37dd7d7dd2adc67166c77e9cd88de5b019b9a9eecfaeaf7bfd481"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"cipher 0.3.0",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "ctr"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
version = "0.9.2"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
checksum = "0369ee1ad671834580515889b80f2ea915f23b8be8d0daa4bbaf2ac5c7590835"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"cipher 0.4.4",
SealedSessionCipher encrypt
2020-11-17 22:32:25 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "curve25519-dalek"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "4.0.0"
source = "git+https://github.com/signalapp/curve25519-dalek?tag=signal-curve25519-4.0.0#463e5c7cba32561ffee8a281c4455ff3c25660d4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"cfg-if",
"cpufeatures",
"curve25519-dalek-derive",
"digest",
"fiat-crypto",
"platforms",
"rustc_version",
Update both poksho and protocol to use lizard2 3.0.0
2021-02-19 21:37:35 +01:00
"serde",
Update hash traits
2021-02-19 19:36:16 +01:00
"subtle",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"zeroize",
]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "curve25519-dalek-derive"
version = "0.1.0"
source = "git+https://github.com/signalapp/curve25519-dalek?tag=signal-curve25519-4.0.0#463e5c7cba32561ffee8a281c4455ff3c25660d4"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"proc-macro2",
"quote",
"syn 2.0.28",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "darling"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b750cb3417fd1b327431a470f388520309479ab0bf5e323505daf0290cd3850"
dependencies = [
"darling_core",
"darling_macro",
]
[[package]]
name = "darling_core"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "109c1ca6e6b7f82cc233a97004ea8ed7ca123a9af07a8230878fcfda9b158bf0"
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
"strsim",
"syn 1.0.109",
]
[[package]]
name = "darling_macro"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a4aab4dbc9f7611d8b55048a3a16d2d010c2c8334e46304b40ac1cc14bf3b48e"
dependencies = [
"darling_core",
"quote",
"syn 1.0.109",
]
[[package]]
name = "derive-where"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5bc1955a640c4464859ae700fbe48e666da6fdce99ce5fe1acd08dd295889d10"
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
]
[[package]]
name = "derive_builder"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8d67778784b508018359cbc8696edb3db78160bab2c2a28ba7f56ef6932997f8"
dependencies = [
"derive_builder_macro",
]
[[package]]
name = "derive_builder_core"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c11bdc11a0c47bc7d37d582b5285da6849c96681023680b906673c5707af7b0f"
dependencies = [
"darling",
"proc-macro2",
"quote",
"syn 1.0.109",
]
[[package]]
name = "derive_builder_macro"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ebcda35c7a396850a55ffeac740804b40ffec779b98fffbb1738f4033f0ee79e"
dependencies = [
"derive_builder_core",
"syn 1.0.109",
]
[[package]]
name = "derive_more"
version = "0.99.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb810d30a7c1953f91334de7244731fc3f3c10d7fe163338a35b9f640960321"
dependencies = [
"convert_case",
"proc-macro2",
"quote",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"rustc_version",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"syn 1.0.109",
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
name = "device-transfer"
version = "0.1.0"
dependencies = [
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"boring",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
"hex",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"libc",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
]
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "digest"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.7"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"block-buffer",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"crypto-common",
"subtle",
]
convert the Display impl to use `displaydoc` - remove thiserror for now until we can derive UnwindSafe
2021-05-09 02:40:22 +02:00
[[package]]
name = "displaydoc"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.4"
convert the Display impl to use `displaydoc` - remove thiserror for now until we can derive UnwindSafe
2021-05-09 02:40:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "487585f4d0c6655fe74905e2504d8ad6908e4db67f744eb140876906c2f3175d"
convert the Display impl to use `displaydoc` - remove thiserror for now until we can derive UnwindSafe
2021-05-09 02:40:22 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
convert the Display impl to use `displaydoc` - remove thiserror for now until we can derive UnwindSafe
2021-05-09 02:40:22 +02:00
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "downcast-rs"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ea835d29036a4087793836fa931b08837ad5e957da9e23886b29586fb9b6650"
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
[[package]]
name = "dunce"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.0.4"
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "56ce8c6da7551ec6c462cbaf3bfbc75131ebbfa1c944aeaa9dab51ca1c5f0c3b"
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "dyn-clonable"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4e9232f0e607a262ceb9bd5141a3dfb3e4db6994b31989bbfd845878cba59fd4"
dependencies = [
"dyn-clonable-impl",
"dyn-clone",
]
[[package]]
name = "dyn-clonable-impl"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "558e40ea573c374cf53507fd240b7ee2f5477df7cfebdb97323ec61c719399c5"
dependencies = [
"proc-macro2",
"quote",
"syn 1.0.109",
]
[[package]]
name = "dyn-clone"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.12"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "304e6508efa593091e97a9abbc10f90aa7ca635b6d2784feff3c89d41dd12272"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "either"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "a26ae43d7bcc3b814de94796a5e736d4029efb0ee900c12e2d54c993ad1a1e07"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Add PQXDH tests
2023-05-24 01:14:44 +02:00
[[package]]
name = "env_logger"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.10.0"
Add PQXDH tests
2023-05-24 01:14:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "85cdab6a89accf66733ad5a1693a4dcced6aeff64602b634530dd73c1f3ee9f0"
Add PQXDH tests
2023-05-24 01:14:44 +02:00
dependencies = [
"humantime",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"is-terminal",
Add PQXDH tests
2023-05-24 01:14:44 +02:00
"log",
"regex",
"termcolor",
]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
[[package]]
name = "equivalent"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "errno"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.2"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "6b30f669a7961ef1631673d2766cc92f52d64f7ef354d4fe0ddfd30ed52f0f4f"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
"errno-dragonfly",
"libc",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-sys 0.48.0",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
[[package]]
name = "errno-dragonfly"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf"
dependencies = [
"cc",
"libc",
]
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
[[package]]
name = "fastrand"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "2.0.0"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "6999dc1837253364c2ebb0704ba97994bd874e8f195d665c50b7548f6ea92764"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "fiat-crypto"
version = "0.1.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e825f6987101665dea6ec934c09ec6d721de7bc1bf92248e1d5810c8cd636b77"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "fixedbitset"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.4.2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "0ce7134b9999ecaf8bcd65542e436736ef32ddca1b3e06094cb6ec5755203b80"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
name = "foreign-types"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
version = "0.5.0"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
checksum = "d737d9aa519fb7b749cbc3b962edcf310a8dd1f4b67c91c4f83975dbdd17d965"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
dependencies = [
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"foreign-types-macros",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
"foreign-types-shared",
]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "foreign-types-macros"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.3"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "1a5c6c585bc94aaf2c7b51dd4c2ba22680844aba4c687be581871a6f518c5742"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
name = "foreign-types-shared"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
version = "0.3.1"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
checksum = "aa9a19cbb55df58761df49b23516a86d432839add4af60fc256da840f66ed35b"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "futures-core"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.28"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "4bca583b7e26f571124fe5b7561d49cb2868d79116cfa0eefce955557c6fee8c"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "futures-io"
version = "0.3.28"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fff74096e71ed47f8e023204cfd0aa1289cd54ae5430a9523be060cdb849964"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "futures-macro"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.28"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "89ca545a94061b6365f2c7355b4b32bd20df3ff95f02da9329b34ccc3bd6ee72"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
]
[[package]]
name = "futures-task"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.28"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "76d3d132be6c0e6aa1534069c705a74a5997a356c0dc2f86a47765e5617c5b65"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "futures-util"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.28"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "26b01e40b772d54cf6c6d721c1d1abd0647a0106a12ecaa1c186273392a69533"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
dependencies = [
"futures-core",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"futures-io",
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
"futures-macro",
"futures-task",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"memchr",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
"pin-project-lite",
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
"pin-utils",
"slab",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "generic-array"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.14.7"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"typenum",
"version_check",
]
[[package]]
name = "getrandom"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.10"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "be4136b2a15dd319360be1c07d9933517ccf0be8f16bf62a3bee4f0d618df427"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
"libc",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"wasi 0.11.0+wasi-snapshot-preview1",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
crypto: Use RustCrypto's GHash as well
2021-06-22 03:36:31 +02:00
[[package]]
name = "ghash"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.4.4"
crypto: Use RustCrypto's GHash as well
2021-06-22 03:36:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "1583cc1656d7839fd3732b80cf4f38850336cdb9b8ded1cd399ca62958de3c99"
crypto: Use RustCrypto's GHash as well
2021-06-22 03:36:31 +02:00
dependencies = [
"opaque-debug",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"polyval 0.5.3",
]
[[package]]
name = "ghash"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d930750de5717d2dd0b8c0d42c076c0e884c81a73e6cab859bbd2339c71e3e40"
dependencies = [
"opaque-debug",
"polyval 0.6.1",
"zeroize",
crypto: Use RustCrypto's GHash as well
2021-06-22 03:36:31 +02:00
]
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "gimli"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.27.3"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b6c80984affa11d98d1b88b66ac8853f143217b399d3c74116778ff8fdb4ed2e"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "glob"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.1"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "d2fabcfbdc87f4758337ca535fb41a6d701b65693ce38287d856d1674551ec9b"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "half"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
version = "1.8.2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
checksum = "eabb4a44450da02c90444cf74558da904edde8fb4e9035a9a6a4e15445af0bd7"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "hashbrown"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.12.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
[[package]]
name = "hashbrown"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2c6201b9ff9fd90a5a3bac2e56a830d0caa509576f0e503818ee82c181b3437a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "heck"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.3.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "6d621efb26863f0e9924c6ac577e8275e5e6b77455db64ffa6c65c904e9e132c"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"unicode-segmentation",
]
[[package]]
name = "hermit-abi"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "443144c8cdadd93ebf52ddb4056d257f5b52c04d3c804e657d19eb73fc33668b"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "hex"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.4.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
dependencies = [
"serde",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
[[package]]
name = "hex-literal"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.4.1"
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "6fe2267d4ed49bc07b63801559be28c718ea06c4738b7a03c94df7386d2cde46"
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
Remove support for HKDF "versions" Previously, we had HKDF-for-session-version-3, which matches RFC 5869, and HKDF-for-session-version-2, which produced slightly different results. However, nothing in the current versions of Signal uses anything but the RFC-compliant version. Therefore, this commit removes support for version 2 and deprecates the entry points that take a version: - Java: The HKDFv3 class is deprecated in favor of static methods on the HKDF class. - Swift: The hkdf function that takes a 'version' parameter is deprecated in favor of a new overload that does not. - TypeScript: The HKDF class is deprecated in favor of a top-level hkdf function. - Rust: The libsignal-protocol implementation of HKDF has been removed entirely in favor of the hkdf crate. There are no significant benchmark deltas from this change, and a minimal code size increase that's the cost for removing our own implementation of HKDF. The deprecations can be removed as a later breaking change.
2021-10-09 03:17:45 +02:00
[[package]]
name = "hkdf"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.12.3"
Remove support for HKDF "versions" Previously, we had HKDF-for-session-version-3, which matches RFC 5869, and HKDF-for-session-version-2, which produced slightly different results. However, nothing in the current versions of Signal uses anything but the RFC-compliant version. Therefore, this commit removes support for version 2 and deprecates the entry points that take a version: - Java: The HKDFv3 class is deprecated in favor of static methods on the HKDF class. - Swift: The hkdf function that takes a 'version' parameter is deprecated in favor of a new overload that does not. - TypeScript: The HKDF class is deprecated in favor of a top-level hkdf function. - Rust: The libsignal-protocol implementation of HKDF has been removed entirely in favor of the hkdf crate. There are no significant benchmark deltas from this change, and a minimal code size increase that's the cost for removing our own implementation of HKDF. The deprecations can be removed as a later breaking change.
2021-10-09 03:17:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "791a029f6b9fc27657f6f188ec6e5e43f6911f6f878e0dc5501396e09809d437"
Remove support for HKDF "versions" Previously, we had HKDF-for-session-version-3, which matches RFC 5869, and HKDF-for-session-version-2, which produced slightly different results. However, nothing in the current versions of Signal uses anything but the RFC-compliant version. Therefore, this commit removes support for version 2 and deprecates the entry points that take a version: - Java: The HKDFv3 class is deprecated in favor of static methods on the HKDF class. - Swift: The hkdf function that takes a 'version' parameter is deprecated in favor of a new overload that does not. - TypeScript: The HKDF class is deprecated in favor of a top-level hkdf function. - Rust: The libsignal-protocol implementation of HKDF has been removed entirely in favor of the hkdf crate. There are no significant benchmark deltas from this change, and a minimal code size increase that's the cost for removing our own implementation of HKDF. The deprecations can be removed as a later breaking change.
2021-10-09 03:17:45 +02:00
dependencies = [
"hmac",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "hmac"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.12.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "6c49c37c09c17a53d937dfbb742eb3a961d65a994e6bcdcf37e7399d0cc8ab5e"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"digest",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Add PQXDH tests
2023-05-24 01:14:44 +02:00
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "iana-time-zone"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.1.57"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "2fad5b825842d2b38bd206f3e81d6957625fd7f0a361e345c30e01a0ae2dd613"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
"android_system_properties",
"core-foundation-sys",
"iana-time-zone-haiku",
"js-sys",
"wasm-bindgen",
"windows",
]
[[package]]
name = "iana-time-zone-haiku"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
dependencies = [
"cc",
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "indexmap"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.9.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "bd070e393353796e801d209ad339e89596eb4c8d430d18ede6a1cced8fafbd99"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"autocfg",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"hashbrown 0.12.3",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "indexmap"
version = "2.0.0"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "d5477fe2230a79769d8dc68e0eabf5437907c0457a5614a9e8dddb67f65eb65d"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"equivalent",
"hashbrown 0.14.0",
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "inout"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a0c10553d664a4d0bcff9f4215d0aac67a639cc68ef660840afe309b807bc9f5"
dependencies = [
"block-padding",
"generic-array",
]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
name = "is-terminal"
version = "0.4.9"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "cb0889898416213fab133e1d33a0e5858a48177452750691bde3666d0fdbaf8b"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"hermit-abi",
"rustix",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-sys 0.48.0",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "itertools"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"either",
]
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
[[package]]
name = "itoa"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.9"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "af150ab688ff2122fcef229be89cb50dd66af9e01a4ff320cc137eecc9bacc38"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "jni"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
version = "0.21.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
checksum = "1a87aa2bb7d2af34197c04845522473242e1aa17c12f4935d5856491a7fb8c97"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"cesu8",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"combine",
"jni-sys",
"log",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
"thiserror",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"walkdir",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-sys 0.45.0",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "jni-sys"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8eaf4bc02d17cbdd7ff4c7438cafcdf7fb9a4613313ad11b4f8fefe7d3fa0130"
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
[[package]]
name = "jobserver"
version = "0.1.26"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "936cfd212a0155903bcbc060e316fb6cc7cbf2e1907329391ebadc1fe0ce77c2"
dependencies = [
"libc",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "js-sys"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.64"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "c5f195fe497f702db0f318b07fdd68edb16955aed830df8363d837542f8f935a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"wasm-bindgen",
]
device transfer: replace `picky` with `boring` Upcoming work in `attest` requires additional X509 support, and swapping these libraries is a negligible impact on binary size. This uses a fork of `cloudflare/boring`, as we have some additions that haven’t yet been contributed upstream.
2022-06-16 22:14:17 +02:00
[[package]]
Revert "device transfer: replace `picky` with `boring`" We need to work out more kinks cross-compiling boring-sys, so revert this for now. (But keep the fix to use the correct Android NDK.)
2022-06-23 00:06:14 +02:00
name = "lazy_static"
version = "1.4.0"
device transfer: replace `picky` with `boring` Upcoming work in `attest` requires additional X509 support, and swapping these libraries is a negligible impact on binary size. This uses a fork of `cloudflare/boring`, as we have some additions that haven’t yet been contributed upstream.
2022-06-16 22:14:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "device transfer: replace `picky` with `boring`" We need to work out more kinks cross-compiling boring-sys, so revert this for now. (But keep the fix to use the correct Android NDK.)
2022-06-23 00:06:14 +02:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "lazycell"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "libc"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.147"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
[[package]]
name = "libloading"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
version = "0.6.7"
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
checksum = "351a32417a12d5f7e82c368a66781e307834dae04c6ce0cd4456d52989229883"
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
"winapi",
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "libloading"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.7.4"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "b67380fd3b2fbe7527a606e18729d21c6f3951633d0500574c4dc22d2d638b9f"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
dependencies = [
"cfg-if",
"winapi",
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "libm"
version = "0.2.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7012b1bbb0719e1097c47611d3898568c546d597c2e74d66f6087edd5233ff4"
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
[[package]]
name = "libsignal-bridge"
version = "0.1.0"
dependencies = [
Bridge: expose RustCrypto's AES-GCM-SIV instead of our own Same as before, but for the wrapper exposed to the app languages.
2021-06-17 03:36:36 +02:00
"aes-gcm-siv",
Port SenderKeyStore to async bridge_fn
2021-02-19 03:52:35 +01:00
"async-trait",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"attest",
bridge: Add support for bincode-serialized args and results This will be used by zkgroup. Note that in order to print the type correctly in C, a type `Serialized<FooBar>` will be translated to `[u8; FOO_BAR_LEN]`, where 'FOO_BAR_LEN' has to be a constant that's in scope.
2021-10-28 23:53:42 +02:00
"bincode",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"bytemuck",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
"device-transfer",
Replace block_on and expect_ready with FutureExt::now_or_never Both futures::executor::block_on and our own expect_ready were being used to resolve futures that were, in practice, known to be non-blocking. FutureExt::now_or_never handles that case more lightly than block_on and more uniformly than expect_ready. This lets us drop the dependency on the full 'futures' crate down to just futures_util, which should help with compile time.
2021-07-03 02:55:30 +02:00
"futures-util",
Remove support for HKDF "versions" Previously, we had HKDF-for-session-version-3, which matches RFC 5869, and HKDF-for-session-version-2, which produced slightly different results. However, nothing in the current versions of Signal uses anything but the RFC-compliant version. Therefore, this commit removes support for version 2 and deprecates the entry points that take a version: - Java: The HKDFv3 class is deprecated in favor of static methods on the HKDF class. - Swift: The hkdf function that takes a 'version' parameter is deprecated in favor of a new overload that does not. - TypeScript: The HKDF class is deprecated in favor of a top-level hkdf function. - Rust: The libsignal-protocol implementation of HKDF has been removed entirely in favor of the hkdf crate. There are no significant benchmark deltas from this change, and a minimal code size increase that's the cost for removing our own implementation of HKDF. The deprecations can be removed as a later breaking change.
2021-10-09 03:17:45 +02:00
"hkdf",
Implement incremental MAC
2023-05-09 21:29:25 +02:00
"hmac",
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
"jni",
Move deserialization into bridge/shared as well
2020-11-19 03:33:24 +01:00
"libc",
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
"libsignal-bridge-macros",
Drop the "-rust" from the "libsignal-protocol" crate The project corresponds to libsignal-protocol-java and the others, but /within/ the language we don't need to tag with the language name.
2021-02-04 19:26:36 +01:00
"libsignal-protocol",
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
"linkme",
JNI: Rethrow callback exceptions instead of wrapping them
2020-12-08 19:47:30 +01:00
"log",
Begin adding Node support to libsignal-bridge with bridge_deserialize
2021-01-20 02:05:09 +01:00
"neon",
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
"paste",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Bridge: initial support for async bridge_fns For FFI and JNI, these use expect_ready to force the function to completion, since all FFI and JNI callbacks are (currently) synchronous. For Node, this uses the newly-landed signal-neon-futures support crate to return a JavaScript Promise. A new AsyncArgTypeInfo trait is added for Node types as well.
2021-02-10 00:06:22 +01:00
"scopeguard",
bridge: Add support for bincode-serialized args and results This will be used by zkgroup. Note that in order to print the type correctly in C, a type `Serialized<FooBar>` will be translated to `[u8; FOO_BAR_LEN]`, where 'FOO_BAR_LEN' has to be a constant that's in scope.
2021-10-28 23:53:42 +02:00
"serde",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
"signal-crypto",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"signal-media",
Bridge: initial support for async bridge_fns For FFI and JNI, these use expect_ready to force the function to completion, since all FFI and JNI callbacks are (currently) synchronous. For Node, this uses the newly-landed signal-neon-futures support crate to return a JavaScript Promise. A new AsyncArgTypeInfo trait is added for Node types as well.
2021-02-10 00:06:22 +01:00
"signal-neon-futures",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"signal-pin",
Move remaining FFI accessors into bridge/shared
2021-02-04 01:35:46 +01:00
"static_assertions",
Bridge username hashing APIs to all client platforms
2023-02-01 18:36:49 +01:00
"usernames",
Use uuid crate instead of our own Uuid type This lets us parse UUIDs as well (needed in next commit)
2021-03-26 23:23:38 +01:00
"uuid",
bridge: Add zkgroup APIs These APIs are designed to match the generated "simpleapi" entry points in the original zkgroup repository, to make it easier to adapt the existing Java, Swift, and TypeScript code to libsignal-client. The cbindgen-generated signal_ffi.h now includes constants, so that the fixed-size arrays used to serialize zkgroup types can use named constants in Rust. This meant filtering out some constants that were getting picked up but that should not be included. Note that this commit makes references to Java exception types that will be added in a later commit.
2021-10-29 01:48:02 +02:00
"zkgroup",
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
]
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
[[package]]
name = "libsignal-bridge-macros"
version = "0.1.0"
dependencies = [
Use Java names for bridge_fns The Java names can usually be mapped to the C names but not vice versa, since the C names use snake case for both the type and the operation.
2020-11-24 22:07:18 +01:00
"heck",
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
"proc-macro2",
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
Speed up libsignal-bridge-macros by not parsing the function bodies syn-mid is a syn-author-endorsed crate that allows parsing a function signature while treating the body as opaque. This is faster as an action /and/ faster to build because we don't need all of syn.
2021-01-06 02:35:29 +01:00
"syn-mid",
Bridge: break up bridge_fn implementation by FFI/JNI/Node Also, revert back to the simpler unzip3 crate instead of unzip-n.
2021-02-22 20:46:33 +01:00
"unzip3",
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "libsignal-ffi"
Bump to version v0.32.0
2023-09-01 22:12:57 +02:00
version = "0.32.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
"async-trait",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
"attest",
FFI: Depend on cpufeatures 0.1.5 to ensure iOS gets optimized crypto
2021-06-22 19:45:47 +02:00
"cpufeatures",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
"device-transfer",
Replace block_on and expect_ready with FutureExt::now_or_never Both futures::executor::block_on and our own expect_ready were being used to resolve futures that were, in practice, known to be non-blocking. FutureExt::now_or_never handles that case more lightly than block_on and more uniformly than expect_ready. This lets us drop the dependency on the full 'futures' crate down to just futures_util, which should help with compile time.
2021-07-03 02:55:30 +02:00
"futures-util",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"libc",
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
"libsignal-bridge",
Drop the "-rust" from the "libsignal-protocol" crate The project corresponds to libsignal-protocol-java and the others, but /within/ the language we don't need to tag with the language name.
2021-02-04 19:26:36 +01:00
"libsignal-protocol",
Swift: connect Rust's 'log' to SignalCoreKit's OWSLogger We're not actually logging anything yet, but this will let us do so. The logging is initialized using a static constructor so that clients of SignalCoreKit don't have to do any additional setup. This requires an ObjC file instead of a Swift one. (When running as a Swift package, logs will just go to stderr via NSLog.)
2020-12-01 19:26:00 +01:00
"log",
Revert "Replace log-panics with an equivalent without symbolicated backtraces" This reverts commit 99aabcf2032e19904bdedef1fbbeaf0a4a70d961.
2022-07-18 20:43:05 +02:00
"log-panics",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
"signal-crypto",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
"signal-media",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"signal-pin",
Bridge username hashing APIs to all client platforms
2023-02-01 18:36:49 +01:00
"usernames",
bridge: Add zkgroup APIs These APIs are designed to match the generated "simpleapi" entry points in the original zkgroup repository, to make it easier to adapt the existing Java, Swift, and TypeScript code to libsignal-client. The cbindgen-generated signal_ffi.h now includes constants, so that the fixed-size arrays used to serialize zkgroup types can use named constants in Rust. This meant filtering out some constants that were getting picked up but that should not be included. Note that this commit makes references to Java exception types that will be added in a later commit.
2021-10-29 01:48:02 +02:00
"zkgroup",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "libsignal-jni"
Bump to version v0.32.0
2023-09-01 22:12:57 +02:00
version = "0.32.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
"async-trait",
Update log-panics to 2.1.0 to print unresolved backtraces on mobile Symbols are stripped on both iOS and Android by the time the app gets to a user's device, so spending time (and code size) trying to symbolicate backtraces is wasted. It's still useful for Desktop and Server, though.
2022-07-18 20:50:16 +02:00
"cfg-if",
Update cpufeatures to 0.2.2, for 64-bit Android hardware crypto Code using cpufeatures to check for hardware support for cryptographic operations will now be able to do so on 64-bit Android as well.
2022-03-19 01:38:21 +01:00
"cpufeatures",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"jni",
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
"libsignal-bridge",
Drop the "-rust" from the "libsignal-protocol" crate The project corresponds to libsignal-protocol-java and the others, but /within/ the language we don't need to tag with the language name.
2021-02-04 19:26:36 +01:00
"libsignal-protocol",
Java: Hook up the 'log' crate to SignalProtocolLogger
2021-01-21 03:26:02 +01:00
"log",
Revert "Replace log-panics with an equivalent without symbolicated backtraces" This reverts commit 99aabcf2032e19904bdedef1fbbeaf0a4a70d961.
2022-07-18 20:43:05 +02:00
"log-panics",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Move AES-GCM-SIV implementation into rust/crypto
2021-03-15 18:24:08 +01:00
"signal-crypto",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update Cargo.lock
2020-11-12 17:10:55 +01:00
[[package]]
name = "libsignal-node"
Bump to version v0.32.0
2023-09-01 22:12:57 +02:00
version = "0.32.0"
Update Cargo.lock
2020-11-12 17:10:55 +01:00
dependencies = [
Add support for SenderKeyStore in TypeScript API
2021-02-08 20:35:40 +01:00
"async-trait",
Downgrade cmake crate to 0.1.48 0.1.49 includes some changes to "improve" cross-compilation that interfere with the "implicit" cross-compilation happening for Windows (using Visual Studio on an "AMD64" host to compile for "ARM64") and for Mac Catalyst (using a macOS SDK to compile for an "ios-macabi" target).
2023-05-31 21:25:58 +02:00
"cmake",
Begin adding Node support to libsignal-bridge with bridge_deserialize
2021-01-20 02:05:09 +01:00
"libsignal-bridge",
Drop the "-rust" from the "libsignal-protocol" crate The project corresponds to libsignal-protocol-java and the others, but /within/ the language we don't need to tag with the language name.
2021-02-04 19:26:36 +01:00
"libsignal-protocol",
Node: Add an entry point for logging
2021-01-26 03:13:54 +01:00
"log",
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
"log-panics",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
"neon",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
"signal-neon-futures",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
Drop the "-rust" from the "libsignal-protocol" crate The project corresponds to libsignal-protocol-java and the others, but /within/ the language we don't need to tag with the language name.
2021-02-04 19:26:36 +01:00
name = "libsignal-protocol"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
version = "0.1.0"
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"aes 0.8.3",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
"aes-gcm-siv",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"arrayref",
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
"async-trait",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"criterion",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"ctr 0.9.2",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
convert the Display impl to use `displaydoc` - remove thiserror for now until we can derive UnwindSafe
2021-05-09 02:40:22 +02:00
"displaydoc",
Add PQXDH tests
2023-05-24 01:14:44 +02:00
"env_logger",
Replace block_on and expect_ready with FutureExt::now_or_never Both futures::executor::block_on and our own expect_ready were being used to resolve futures that were, in practice, known to be non-blocking. FutureExt::now_or_never handles that case more lightly than block_on and more uniformly than expect_ready. This lets us drop the dependency on the full 'futures' crate down to just futures_util, which should help with compile time.
2021-07-03 02:55:30 +02:00
"futures-util",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"hex",
protocol: Add the ServiceId, Aci, and Pni types Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-07-13 22:54:53 +02:00
"hex-literal",
Remove support for HKDF "versions" Previously, we had HKDF-for-session-version-3, which matches RFC 5869, and HKDF-for-session-version-2, which produced slightly different results. However, nothing in the current versions of Signal uses anything but the RFC-compliant version. Therefore, this commit removes support for version 2 and deprecates the entry points that take a version: - Java: The HKDFv3 class is deprecated in favor of static methods on the HKDF class. - Swift: The hkdf function that takes a 'version' parameter is deprecated in favor of a new overload that does not. - TypeScript: The HKDF class is deprecated in favor of a top-level hkdf function. - Rust: The libsignal-protocol implementation of HKDF has been removed entirely in favor of the hkdf crate. There are no significant benchmark deltas from this change, and a minimal code size increase that's the cost for removing our own implementation of HKDF. The deprecations can be removed as a later breaking change.
2021-10-09 03:17:45 +02:00
"hkdf",
Update hash traits
2021-02-19 19:36:16 +01:00
"hmac",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"itertools",
Add logging that matches SignalProtocolKit (the ObjC library)
2021-02-05 00:21:05 +01:00
"log",
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
"num_enum",
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
"pqcrypto-kyber",
"pqcrypto-traits",
Implement incremental MAC
2023-05-09 21:29:25 +02:00
"proptest",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"prost",
"prost-build",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
"sha2",
Adding support for username links
2023-07-01 01:45:37 +02:00
"signal-crypto",
protocol: Simplify key derivation for multi-recipient sealed sender
2023-08-22 23:21:04 +02:00
"static_assertions",
Update hash traits
2021-02-19 19:36:16 +01:00
"subtle",
use thiserror to remove error.rs boilerplate
2021-10-09 08:11:46 +02:00
"thiserror",
Use uuid crate instead of our own Uuid type This lets us parse UUIDs as well (needed in next commit)
2021-03-26 23:23:38 +01:00
"uuid",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"x25519-dalek",
]
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
[[package]]
name = "linkme"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.14"
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "a6c7bb4dcb6a456ffd750601c389889a58daff6857125b75ee6e5edabf6388c8"
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
dependencies = [
"linkme-impl",
]
[[package]]
name = "linkme-impl"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.14"
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "1d5adefdb2c04ca9173223070228ff26a04667003619257b8442f192d9986218"
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Use the linkme crate to avoid registering Node functions manually This only works on functions using the macros in libsignal-bridge; for anything else we'll keep using neon::ModuleContext::export_function manually, at least for now.
2021-01-21 01:11:40 +01:00
]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "linux-raw-sys"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.4.5"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "57bcfdad1b858c2db7c38303a6d2ad4dfaf5eb53dfeb0910128b2c26d6158503"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "log"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.4.19"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b06a4cde4c0f271a446782e3eff8de789548ce57dbc8eca9292c27f4a42004b4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "log-panics"
Update log-panics to 2.1.0 to print unresolved backtraces on mobile Symbols are stripped on both iOS and Android by the time the app gets to a user's device, so spending time (and code size) trying to symbolicate backtraces is wasted. It's still useful for Desktop and Server, though.
2022-07-18 20:50:16 +02:00
version = "2.1.0"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update log-panics to 2.1.0 to print unresolved backtraces on mobile Symbols are stripped on both iOS and Android by the time the app gets to a user's device, so spending time (and code size) trying to symbolicate backtraces is wasted. It's still useful for Desktop and Server, though.
2022-07-18 20:50:16 +02:00
checksum = "68f9dd8546191c1850ecf67d22f5ff00a935b890d0e84713159a55495cc2ac5f"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
dependencies = [
"backtrace",
"log",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "memchr"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "2.5.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "memoffset"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "5a634b1c61a95585bd15607c6ab0c4e5b226e695ff2800ba0cdccddf208c406c"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"autocfg",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "minimal-lexical"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "miniz_oxide"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.7.1"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "e7810e0be55b428ada41041c41f32c9f1a42817901b4ccf45fa3d4b6561e74c7"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
dependencies = [
"adler",
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "mp4san"
update mp4san to eliminate error-stack This reduces code size by 62kB, according to `java/check_code_size.py`.
2023-05-16 22:42:18 +02:00
version = "0.3.1"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update mp4san to eliminate error-stack This reduces code size by 62kB, according to `java/check_code_size.py`.
2023-05-16 22:42:18 +02:00
checksum = "08f5a9d33916d7d0afbbdec30dbceabe84640cf354f4f612f25d4a25e0ce9f07"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
dependencies = [
"bytes",
"derive-where",
"derive_builder",
"derive_more",
"downcast-rs",
"dyn-clonable",
"futures-util",
"log",
"thiserror",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "multimap"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.8.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "e5ce46fe64a9d73be07dcbe690a38ce1b293be448fd8ce1e6c1b8062c9f72c6a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Update Cargo.lock
2020-11-12 17:10:55 +01:00
[[package]]
name = "neon"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.1"
Update to Neon 0.9.0 - Drop our fork of Neon now that our changes have been integrated - Adopt rename of EventQueue to Channel - Add a napi-6 feature to signal-neon-futures to make it easier to test under the configuration we're actually shipping
2021-07-26 21:36:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "28e15415261d880aed48122e917a45e87bb82cf0260bb6db48bbab44b7464373"
Update Cargo.lock
2020-11-12 17:10:55 +01:00
dependencies = [
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
"neon-build",
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
"neon-macros",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
"neon-runtime",
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
"semver 0.9.0",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
"smallvec",
]
Bump Neon to 0.7.0 and use feature napi-1 Neon by default requires N-API 6 and the version of Electron that is used in Desktop only supports N-API 5. Without this feature, some weird hacks are required to build on Windows.
2021-01-21 19:09:07 +01:00
[[package]]
name = "neon-build"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.1"
Update to Neon 0.9.0 - Drop our fork of Neon now that our changes have been integrated - Adopt rename of EventQueue to Channel - Add a napi-6 feature to signal-neon-futures to make it easier to test under the configuration we're actually shipping
2021-07-26 21:36:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "8bac98a702e71804af3dacfde41edde4a16076a7bbe889ae61e56e18c5b1c811"
Bump Neon to 0.7.0 and use feature napi-1 Neon by default requires N-API 6 and the version of Electron that is used in Desktop only supports N-API 5. Without this feature, some weird hacks are required to build on Windows.
2021-01-21 19:09:07 +01:00
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
[[package]]
name = "neon-macros"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.1"
Update to Neon 0.9.0 - Drop our fork of Neon now that our changes have been integrated - Adopt rename of EventQueue to Channel - Add a napi-6 feature to signal-neon-futures to make it easier to test under the configuration we're actually shipping
2021-07-26 21:36:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "b7288eac8b54af7913c60e0eb0e2a7683020dffa342ab3fd15e28f035ba897cf"
Node: Switch to Neon's napi-runtime and JsBox We lose the ability to define classes in Rust, but we probably want to be doing that in TypeScript anyway.
2020-12-04 03:01:59 +01:00
dependencies = [
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
Node: update to Neon 0.10
2021-09-21 21:52:18 +02:00
"syn-mid",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
]
[[package]]
name = "neon-runtime"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.10.1"
Update to Neon 0.9.0 - Drop our fork of Neon now that our changes have been integrated - Adopt rename of EventQueue to Channel - Add a napi-6 feature to signal-neon-futures to make it easier to test under the configuration we're actually shipping
2021-07-26 21:36:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "4676720fa8bb32c64c3d9f49c47a47289239ec46b4bdb66d0913cc512cb0daca"
Update Cargo.lock
2020-11-12 17:10:55 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"libloading 0.6.7",
Bump Neon to 0.7.0 and use feature napi-1 Neon by default requires N-API 6 and the version of Electron that is used in Desktop only supports N-API 5. Without this feature, some weird hacks are required to build on Windows.
2021-01-21 19:09:07 +01:00
"smallvec",
Update Cargo.lock
2020-11-12 17:10:55 +01:00
]
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "nom"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "7.1.3"
Revert "device transfer: replace `picky` with `boring`" We need to work out more kinks cross-compiling boring-sys, so revert this for now. (But keep the fix to use the correct Android NDK.)
2022-06-23 00:06:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "d273983c5a657a70a3e8f2a01329822f3b8c8172b73826411a55751e404a0a4a"
Revert "device transfer: replace `picky` with `boring`" We need to work out more kinks cross-compiling boring-sys, so revert this for now. (But keep the fix to use the correct Android NDK.)
2022-06-23 00:06:14 +02:00
dependencies = [
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
"memchr",
"minimal-lexical",
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "num-traits"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.16"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "f30b0abd723be7e2ffca1272140fac1a2f084c77ec3e123c192b66af1ee9e6c2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"autocfg",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"libm",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "num_cpus"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.16.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "4161fcb6d602d4d2081af7c3a45852d875a03dd337a6bfdd6e06407b61342a43"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"hermit-abi",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"libc",
]
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
[[package]]
name = "num_enum"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.6.1"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "7a015b430d3c108a207fd776d2e2196aaf8b1cf8cf93253e3a097ff3085076a1"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
dependencies = [
"num_enum_derive",
]
[[package]]
name = "num_enum_derive"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.6.1"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "96667db765a921f7b295ffee8b60472b686a51d4f21c2ee4ffdb94c7013b65a6"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
]
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
[[package]]
name = "object"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.31.1"
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "8bda667d9f2b5051b8833f59f3bf748b28ef54f850f4fcb389a252aa383866d1"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
dependencies = [
"memchr",
]
Log panics in all three bridges
2021-03-02 22:19:04 +01:00
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "once_cell"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.18.0"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "dd8b5dd2ae5ed71462c540258bedcb51965123ad7e7ccf4b9a8cafaa4a63576d"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "oorandom"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
version = "11.1.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
checksum = "0ab1bc2a289d34bd04a330323ac98a1b4bc82c9d9fcb1e66b63caa84da26b575"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "opaque-debug"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "password-hash"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "346f04948ba92c43e8469c1ee6736c7563d71012b17d40745260fe106aac2166"
dependencies = [
"base64ct",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_core",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"subtle",
]
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
[[package]]
name = "paste"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.14"
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "de3145af08024dea9fa9914f381a17b8fc6034dfb00f3a84013f7ff43f29ed4c"
Start factoring out common parts of the FFI and JNI libraries
2020-11-19 02:08:32 +01:00
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "peeking_take_while"
version = "0.1.2"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
checksum = "19b17cddbe7ec3f8bc800887bab5e717348c95ea2ca0b1bf0837fb964dc67099"
Device Sender Utilities - Generate Key + Self-Signed Certificate
2021-03-03 23:23:22 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "petgraph"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.6.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "4dd7d28ee937e54fe3080c91faa1c3a46c06de6252988a7f4592ba2310ef22a4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"fixedbitset",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"indexmap 1.9.3",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "pin-project-lite"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.10"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "4c40d25201921e5ff0c862a505c6557ea88568a4e3ace775ab55e93f2f4f9d57"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "platforms"
version = "3.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3d7ddaed09e0eb771a79ab0fd64609ba0afb0a8366421957936ad14cbd13630"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "plotters"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "d2c224ba00d7cadd4d5c660deaf2098e5e80e07846537c51f9cfa4be50c1fd45"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"num-traits",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
"plotters-backend",
"plotters-svg",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"wasm-bindgen",
"web-sys",
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "plotters-backend"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.5"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "9e76628b4d3a7581389a35d5b6e2139607ad7c75b17aed325f210aa91f4a9609"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "plotters-svg"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.5"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "38f6d39893cca0701371e3c27294f09797214b86f1fb951b89ade8ec04e2abab"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
"plotters-backend",
]
Update Cargo.lock
2021-02-19 17:58:06 +01:00
[[package]]
name = "poksho"
version = "0.7.0"
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
Update hash traits
2021-02-19 19:36:16 +01:00
"hex",
"hmac",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
"subtle",
Update Cargo.lock
2021-02-19 17:58:06 +01:00
]
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
[[package]]
name = "poly1305"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.7.2"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "048aeb476be11a4b6ca432ca569e375810de9294ae78f4774e78ea98a9246ede"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
dependencies = [
"cpufeatures",
"opaque-debug",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"universal-hash 0.4.0",
]
[[package]]
name = "poly1305"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8159bd90725d2df49889a078b54f4f79e87f1f8a8444194cdca81d38f5393abf"
dependencies = [
"cpufeatures",
"opaque-debug",
"universal-hash 0.5.1",
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
]
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
[[package]]
name = "polyval"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.5.3"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "8419d2b623c7c0896ff2d5d96e2cb4ede590fed28fcc34934f4c33c036e620a1"
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
"cpufeatures",
"opaque-debug",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"universal-hash 0.4.0",
]
[[package]]
name = "polyval"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d52cff9d1d4dee5fe6d03729099f4a310a41179e0a10dbf542039873f2e826fb"
dependencies = [
"cfg-if",
"cpufeatures",
"opaque-debug",
"universal-hash 0.5.1",
protocol: Use RustCrypto's AES-GCM-SIV instead of our own Now that RustCrypto aes-gcm-siv supports runtime-detected ARMv8 and x86_64 crypto intrinsics, we don't need our own implementation, which will be removed from signal-crypto in a later commit.
2021-06-17 02:53:21 +02:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "ppv-lite86"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.2.17"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
[[package]]
name = "pqcrypto-internals"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0127cbc0239f585139a56effd7867921eae3425a000a72dde2b0a156062346b2"
dependencies = [
"cc",
"dunce",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"getrandom",
Add Kyber KEM and implement PQXDH protocol Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Max Moiseev <moiseev@signal.org>
2023-05-10 01:41:29 +02:00
"libc",
]
[[package]]
name = "pqcrypto-kyber"
version = "0.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fe9d9695c19e525d5366c913562a331fbeef9a2ad801d9a9ded61a0e4c2fe0fb"
dependencies = [
"cc",
"glob",
"libc",
"pqcrypto-internals",
"pqcrypto-traits",
]
[[package]]
name = "pqcrypto-traits"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "97e91cb6af081c6daad5fa705f8adb0634c027662052cb3174bdf2957bf07e25"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
[[package]]
name = "proc-macro-crate"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.3.1"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "7f4c021e1093a56626774e81216a4ce732a735e5bad4868a03f3ed65ca0c3919"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
dependencies = [
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"once_cell",
"toml_edit",
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "proc-macro2"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.66"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "18fb31db3f9bddb2ea821cde30a9f70117e3f119938b5ee630b7403aa6e2ead9"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
"unicode-ident",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "proptest"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.2.0"
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "4e35c06b98bf36aba164cc17cb25f7e232f5c4aeea73baa14b8a9f0d92dbfa65"
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
dependencies = [
"bit-set",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 1.3.2",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"byteorder",
"lazy_static",
"num-traits",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
"rand_chacha",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"rand_xorshift",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"regex-syntax 0.6.29",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"rusty-fork",
"tempfile",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"unarray",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "prost"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
version = "0.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
checksum = "444879275cb4fd84958b1a1d5420d15e6fcf7c235fe47f053c9c2a80aceb6001"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"bytes",
"prost-derive",
]
[[package]]
name = "prost-build"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
version = "0.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
checksum = "62941722fb675d463659e49c4f3fe1fe792ff24fe5bbaa9c08cd3b98a1c354f5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"bytes",
"heck",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"itertools",
Update to prost 0.9
2021-11-28 17:32:32 +01:00
"lazy_static",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"log",
"multimap",
"petgraph",
"prost",
"prost-types",
Update to prost 0.9
2021-11-28 17:32:32 +01:00
"regex",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"tempfile",
"which",
]
[[package]]
name = "prost-derive"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
version = "0.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
checksum = "f9cc1a3263e07e0bf68e96268f37665207b49560d98739662cdfaae215c720fe"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"anyhow",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"itertools",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"proc-macro2",
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "prost-types"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
version = "0.9.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to prost 0.9
2021-11-28 17:32:32 +01:00
checksum = "534b7a0e836e3c482d2693070f982e39e7611da9695d4d1f5a4b186b51faef0a"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"bytes",
"prost",
]
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "quick-error"
version = "1.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "quote"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.32"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "50f3b39ccfb720540debaa0164757101c08ecb8d326b15358ce76a62c7e85965"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"proc-macro2",
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "rand"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
version = "0.8.5"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"libc",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_chacha",
"rand_core",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
[[package]]
name = "rand_chacha"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "0.3.1"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
"ppv-lite86",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_core",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
[[package]]
name = "rand_core"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
version = "0.6.4"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"getrandom",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "rand_xorshift"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d25bf25ec5ae4a3f1b92f929810509a2f53d7dca2f50b794ff57e3face536c8f"
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_core",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "rayon"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.7.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "1d2df5196e37bcc87abebc0053e20787d73847bb33134a69841207dd0a47f03b"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"either",
"rayon-core",
]
[[package]]
name = "rayon-core"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.11.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "4b8f95bd6966f5c87776639160a66bd8ab9895d9d4ab01ddba9fc60661aebe8d"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-utils",
"num_cpus",
]
[[package]]
name = "redox_syscall"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.3.5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "567664f262709473930a4bf9e51bf2ebf3348f2e748ccc50dea20646858f8f29"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 1.3.2",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "regex"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.9.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b2eae68fc220f7cf2532e4494aded17545fce192d59cd996e0fe7887f4ceb575"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update to prost 0.9
2021-11-28 17:32:32 +01:00
"aho-corasick",
"memchr",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"regex-automata",
"regex-syntax 0.7.4",
]
[[package]]
name = "regex-automata"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b7b6d6190b7594385f61bd3911cd1be99dfddcfc365a4160cc2ab5bff4aed294"
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax 0.7.4",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "regex-syntax"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.6.29"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "f162c6dd7b008981e4d40210aca20b4bd0f9b60ca9271061b07f78537722f2e1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
name = "regex-syntax"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.7.4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "e5ea92a5b6195c6ef2a0295ea818b312502c6fc94dde986c5553242e18fd4ce2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
device transfer: replace `picky` with `boring` Upcoming work in `attest` requires additional X509 support, and swapping these libraries is a negligible impact on binary size. This uses a fork of `cloudflare/boring`, as we have some additions that haven’t yet been contributed upstream.
2022-06-16 22:14:17 +02:00
[[package]]
Revert "device transfer: replace `picky` with `boring`" We need to work out more kinks cross-compiling boring-sys, so revert this for now. (But keep the fix to use the correct Android NDK.)
2022-06-23 00:06:14 +02:00
name = "rustc-demangle"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.1.23"
device transfer: replace `picky` with `boring` Upcoming work in `attest` requires additional X509 support, and swapping these libraries is a negligible impact on binary size. This uses a fork of `cloudflare/boring`, as we have some additions that haven’t yet been contributed upstream.
2022-06-16 22:14:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
device transfer: replace `picky` with `boring` Upcoming work in `attest` requires additional X509 support, and swapping these libraries is a negligible impact on binary size. This uses a fork of `cloudflare/boring`, as we have some additions that haven’t yet been contributed upstream.
2022-06-16 22:14:17 +02:00
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
[[package]]
name = "rustc_version"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.4.0"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"semver 1.0.18",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
name = "rustix"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.38.6"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "1ee020b1716f0a80e2ace9b03441a749e402e86712f15f16fe8a8f75afac732f"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"bitflags 2.3.3",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"errno",
"libc",
"linux-raw-sys",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-sys 0.48.0",
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
]
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "rusty-fork"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cb3dcc6e454c328bb824492db107ab7c0ae8fcffe4ad210136ef014458c1bc4f"
dependencies = [
"fnv",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"quick-error",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"tempfile",
"wait-timeout",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "ryu"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.15"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "1ad4cc8da4ef723ed60bced201181d83791ad433213d8c24efffda1eec85d741"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
[[package]]
name = "scopeguard"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.2.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
dependencies = [
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"semver-parser",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "semver"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.18"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "b0293b4b29daaf487284529cc2f5675b8e57c61f70167ba415a463651fd6a918"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
[[package]]
name = "serde"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.180"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "0ea67f183f058fe88a4e3ec6e2788e003840893b91bac4559cabedd00863b3ed"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.180"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "24e744d7782b686ab3b73267ef05697159cc0e5abbed3f47f9933165e5219036"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "serde_json"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.104"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "076066c5f1078eac5b722a31827a8832fe108bed65dfa75e233c89f8206e976c"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
benchmarks: Update to criterion 0.4.0 criterion 0.3.x had started warning about features being removed in criterion 0.4 by default, such as automatically generating HTML reports. That particular one did happen, but other planned removals did not, so 0.4 ended up being an easy upgrade for us.
2022-09-12 19:36:24 +02:00
"itoa",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"ryu",
"serde",
]
Switch to using picky crate for forming PKCS8 and X.509 data
2021-03-08 21:41:16 +01:00
[[package]]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
name = "sha1"
version = "0.10.5"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
checksum = "f04293dc80c3993519f2d7f6f511707ee7094fe0c6d3406feb330cdb3540eba3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"cpufeatures",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"digest",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "sha2"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.10.7"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "479fb9d862239e610720565ca91403019f2f00410f1864c5aa7479b950a76ed8"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
"cfg-if",
"cpufeatures",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"digest",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
Switch to using picky crate for forming PKCS8 and X.509 data
2021-03-08 21:41:16 +01:00
[[package]]
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
name = "shlex"
version = "1.1.0"
Switch to using picky crate for forming PKCS8 and X.509 data
2021-03-08 21:41:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Re-apply "device transfer: replace `picky` with `boring`" This reverts commit 09c043c54af34c8765961d49c07243c3923ec7cb.
2022-06-23 01:33:21 +02:00
checksum = "43b2853a4d09f215c24cc5489c992ce46052d359b5109343cbafbf26bc62f8a3"
Switch to using picky crate for forming PKCS8 and X.509 data
2021-03-08 21:41:16 +01:00
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
[[package]]
name = "signal-crypto"
version = "0.1.0"
dependencies = [
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"aes 0.8.3",
"cbc",
Move AES-GCM-SIV implementation into rust/crypto
2021-03-15 18:24:08 +01:00
"criterion",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"ctr 0.9.2",
Adding support for username links
2023-07-01 01:45:37 +02:00
"displaydoc",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"ghash 0.5.0",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
"hex",
Use hex! macro in more tests, rather than hex::decode + expect
2023-09-01 21:59:17 +02:00
"hex-literal",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
"hmac",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Move AES-GCM-SIV implementation into rust/crypto
2021-03-15 18:24:08 +01:00
"serde",
"serde_json",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"sha1",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
"subtle",
Adding support for username links
2023-07-01 01:45:37 +02:00
"thiserror",
Add hashes and HMAC for Java
2021-03-10 20:37:40 +01:00
]
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "signal-media"
version = "0.1.0"
dependencies = [
"futures-util",
"mp4san",
"thiserror",
]
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
[[package]]
name = "signal-neon-futures"
version = "0.1.0"
dependencies = [
Replace block_on and expect_ready with FutureExt::now_or_never Both futures::executor::block_on and our own expect_ready were being used to resolve futures that were, in practice, known to be non-blocking. FutureExt::now_or_never handles that case more lightly than block_on and more uniformly than expect_ready. This lets us drop the dependency on the full 'futures' crate down to just futures_util, which should help with compile time.
2021-07-03 02:55:30 +02:00
"futures-util",
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
"neon",
"signal-neon-futures-tests",
]
[[package]]
name = "signal-neon-futures-tests"
version = "0.1.0"
dependencies = [
Replace block_on and expect_ready with FutureExt::now_or_never Both futures::executor::block_on and our own expect_ready were being used to resolve futures that were, in practice, known to be non-blocking. FutureExt::now_or_never handles that case more lightly than block_on and more uniformly than expect_ready. This lets us drop the dependency on the full 'futures' crate down to just futures_util, which should help with compile time.
2021-07-03 02:55:30 +02:00
"futures-util",
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
"neon",
"signal-neon-futures",
]
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
[[package]]
name = "signal-pin"
version = "0.1.0"
dependencies = [
"argon2",
"criterion",
"displaydoc",
"hex-literal",
"hkdf",
"hmac",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand_core",
"sha2",
pin: Add pin hashing and an svr2 client - Add a new SGX client that can be used for testing svr2 - Add pin hashing that can be used with svr1 and svr2
2023-02-14 16:41:51 +01:00
"static_assertions",
]
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
[[package]]
name = "slab"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.4.8"
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "6528351c9bc8ab22353f9d776db39a20288e8d6c37ef8cfe3317cf875eecfc2d"
dependencies = [
"autocfg",
]
Update Cargo.lock PRs #34 and #27 happened concurrently so async crates are not listed
2020-11-05 23:34:05 +01:00
Update Cargo.lock
2020-11-12 17:10:55 +01:00
[[package]]
name = "smallvec"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.11.0"
Update Cargo.lock
2020-11-12 17:10:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "62bb4feee49fdd9f707ef802e22365a35de4b7b299de4763d44bfea899442ff9"
Update Cargo.lock
2020-11-12 17:10:55 +01:00
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
[[package]]
name = "snow"
Update snow to 0.9.3
2023-08-23 23:02:43 +02:00
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c9d1425eb528a21de2755c75af4c9b5d57f50a0d4c3b7f1828a4cd03f8ba155"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
dependencies = [
"aes-gcm",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"blake2",
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
"chacha20poly1305 0.9.1",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
"rand_core",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"rustc_version",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
"subtle",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
Add MP4 format sanitizer This MP4 format "sanitizer" currently only transforms (when necessary) outgoing media on iOS, Android, or Desktop to make it suitable for streaming playback by the recepient. In the future, it will validate and be able to either repair or reject outbound AND inbound media, to prevent malformed media from being fed to third party or OS media players. An generic io module was added to the libsignal rust bridge containing the InputStream trait, modeled loosely after Java's InputStream, which calls back into the client language to perform reads or skips. This infrastructure could potentially also be for any other future large data inputs to libsignal functions.
2023-03-13 21:53:06 +01:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "subtle"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "2.5.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "81cdd64d312baedb58e21336b31bc043b77e01cc99033ce76ef539f78e965ebc"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "syn"
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
version = "1.0.109"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"proc-macro2",
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"unicode-ident",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
[[package]]
name = "syn"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "2.0.28"
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "04361975b3f5e348b2189d8dc55bc942f278b2d482a6a0365de5bdd62d351567"
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
Speed up libsignal-bridge-macros by not parsing the function bodies syn-mid is a syn-author-endorsed crate that allows parsing a function signature while treating the body as opaque. This is faster as an action /and/ faster to build because we don't need all of syn.
2021-01-06 02:35:29 +01:00
[[package]]
name = "syn-mid"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.5.4"
Speed up libsignal-bridge-macros by not parsing the function bodies syn-mid is a syn-author-endorsed crate that allows parsing a function signature while treating the body as opaque. This is faster as an action /and/ faster to build because we don't need all of syn.
2021-01-06 02:35:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "fea305d57546cc8cd04feb14b62ec84bf17f50e3f7b12560d7bfa9265f39d9ed"
Speed up libsignal-bridge-macros by not parsing the function bodies syn-mid is a syn-author-endorsed crate that allows parsing a function signature while treating the body as opaque. This is faster as an action /and/ faster to build because we don't need all of syn.
2021-01-06 02:35:29 +01:00
dependencies = [
"proc-macro2",
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
Speed up libsignal-bridge-macros by not parsing the function bodies syn-mid is a syn-author-endorsed crate that allows parsing a function signature while treating the body as opaque. This is faster as an action /and/ faster to build because we don't need all of syn.
2021-01-06 02:35:29 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "tempfile"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "3.7.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "5486094ee78b2e5038a6382ed7645bc084dc2ec433426ca4c3cb61e2007b8998"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
"fastrand",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"redox_syscall",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"rustix",
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-sys 0.48.0",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Add PQXDH tests
2023-05-24 01:14:44 +02:00
[[package]]
name = "termcolor"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be55cf8942feac5c765c2c993422806843c9a9a45d4d5c407ad6dd2ea95eb9b6"
dependencies = [
"winapi-util",
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "thiserror"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.44"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "611040a08a0439f8248d1990b111c95baa9c704c805fa1f62104b39655fd7f90"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.44"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "090198534930841fab3a5d1bb637cde49e339654e606195f8d9c76eeb081dc96"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
]
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
[[package]]
name = "time"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "0.1.45"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "1b797afad3f312d1c66a56d11d0316f916356d11bd158fbc6ca6389ff6bf805a"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
dependencies = [
"libc",
"wasi 0.10.0+wasi-snapshot-preview1",
"winapi",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "tinytemplate"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
version = "1.2.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
checksum = "be4d6b5f19ff7664e8c98d03e2139cb510db9b0a60b55f8e8709b689d939b6bc"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"serde",
"serde_json",
]
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
[[package]]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
name = "toml_datetime"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.6.3"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "7cda73e2f1397b1262d6dfdcef8aafae14d1de7748d66822d3bfeeb6d03e5e4b"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "toml_edit"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.19.14"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "f8123f27e969974a3dfba720fdb560be359f57b44302d280ba72e76a74480e8a"
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"indexmap 2.0.0",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"toml_datetime",
"winnow",
Expose Sealed Sender v2 to clients - Add a new "multi-recipient encrypt" entry point - Add an "encrypt v1 sealed sender from UnidentifiedSenderMessage- Content" entry point - Add a public constructor for UnidentifiedSenderMessageContent - Change group_encrypt to return a CiphertextMessage instead of bytes, so it can be used with the above - Java: add SenderKeyStore to SignalProtocolStore requirements
2021-03-25 23:16:34 +01:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "typenum"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.16.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "497961ef93d974e23eb6f433eb5fe1b7930b659f06d12dec6fc44a8f554c0bba"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
[[package]]
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
name = "unarray"
version = "0.1.4"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "eaea85b334db583fe3274d12b4cd1880032beab409c0d774be044d4480ab9a94"
Client-side rust-only HSM enclave library.
2021-07-15 23:04:30 +02:00
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
[[package]]
name = "unicode-ident"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.0.11"
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "301abaae475aa91687eb82514b328ab47a211a533026cb25fc3e519b86adfc3c"
Update linkme for more reliable Node builds libsignal-bridge uses linkme to make a big list of all functions it's going to expose to Node. More recent linkme versions fix issues where that list wasn't being preserved by linkers. This manifested as a CI failure on Windows.
2023-04-19 08:05:37 +02:00
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "unicode-segmentation"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.10.1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "1dd624098567895118886609431a7c3b8f516e41d30e0643f03d94592a147e36"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "universal-hash"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.4.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "8326b2c654932e3e4f9196e69d08fdf7cfd718e1dc6f66b347e6024a0c961402"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update both poksho and protocol to use lizard2 3.0.0
2021-02-19 21:37:35 +01:00
"generic-array",
Update hash traits
2021-02-19 19:36:16 +01:00
"subtle",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Update all the RustCrypto crates
2023-08-25 20:28:49 +02:00
[[package]]
name = "universal-hash"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fc1de2c688dc15305988b563c3854064043356019f97a4b46276fe734c4f07ea"
dependencies = [
"crypto-common",
"subtle",
]
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
[[package]]
Bridge: break up bridge_fn implementation by FFI/JNI/Node Also, revert back to the simpler unzip3 crate instead of unzip-n.
2021-02-22 20:46:33 +01:00
name = "unzip3"
version = "1.0.0"
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bridge: break up bridge_fn implementation by FFI/JNI/Node Also, revert back to the simpler unzip3 crate instead of unzip-n.
2021-02-22 20:46:33 +01:00
checksum = "99c0ec316ab08201476c032feb2f94a5c8ece5b209765c1fbc4430dd6e931ad6"
Use a proc_macro to generate arbitrary FFI/JNI bridging
2020-11-24 02:23:34 +01:00
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "usernames"
version = "0.1.0"
dependencies = [
Implement benchmarks for usernames API
2023-02-08 20:22:21 +01:00
"criterion",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
Bridge username hashing APIs to all client platforms
2023-02-01 18:36:49 +01:00
"displaydoc",
Adding support for username links
2023-07-01 01:45:37 +02:00
"hkdf",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"lazy_static",
"poksho",
"proptest",
Adding support for username links
2023-07-01 01:45:37 +02:00
"prost",
"prost-build",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
"sha2",
Adding support for username links
2023-07-01 01:45:37 +02:00
"signal-crypto",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"subtle",
Adding support for username links
2023-07-01 01:45:37 +02:00
"thiserror",
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
"zkgroup",
]
Use uuid crate instead of our own Uuid type This lets us parse UUIDs as well (needed in next commit)
2021-03-26 23:23:38 +01:00
[[package]]
name = "uuid"
Update to a newer 'uuid' crate for increased inlining
2023-07-20 21:37:23 +02:00
version = "1.4.1"
Use uuid crate instead of our own Uuid type This lets us parse UUIDs as well (needed in next commit)
2021-03-26 23:23:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to a newer 'uuid' crate for increased inlining
2023-07-20 21:37:23 +02:00
checksum = "79daa5ed5740825c40b389c5e50312b9c86df53fccd33f281df655642b43869d"
Use uuid crate instead of our own Uuid type This lets us parse UUIDs as well (needed in next commit)
2021-03-26 23:23:38 +01:00
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
[[package]]
name = "variant_count"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aae2faf80ac463422992abf4de234731279c058aaf33171ca70277c98406b124"
dependencies = [
"quote",
Update boring to require a newer version of bindgen Necessary for certain targets on newer Rust.
2023-04-24 21:39:18 +02:00
"syn 1.0.109",
CDS2: add initial, not-for-production, client bindings
2022-05-13 22:39:26 +02:00
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "version_check"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
version = "0.9.4"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update other Rust dependencies This was done by `cargo update`, followed by reverting to earlier versions of specific crates that have trouble on our current pinned nightly.
2022-03-19 02:09:51 +01:00
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
Implement username generation, hashing, and proofs
2023-01-26 03:06:39 +01:00
[[package]]
name = "wait-timeout"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f200f5b12eb75f8c1ed65abd4b2db8a6e1b138a20de009dacee265a2498f3f6"
dependencies = [
"libc",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "walkdir"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "2.3.3"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "36df944cda56c7d8d8b7496af378e6b16de9284591917d307c9b4d313c44e698"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"same-file",
"winapi-util",
]
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
[[package]]
name = "wasi"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
version = "0.10.0+wasi-snapshot-preview1"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[feature] CDS2 attestation Implements (a subset of) Intel's DCAP attestation, making heavy use of 'boring' for X509 and ECDSA. Cds2Client is now ready for use! Co-authored-by: Jordan Rose <jrose@signal.org> Co-authored-by: Ravi Khadiwala <ravi@signal.org>
2022-07-22 21:23:57 +02:00
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
Update dependencies This is `cargo update` along with manually upgrading jni to 0.19 and prost to 0.7 This isn't a complete cargo update as it avoids updating polyval as there is a duplicate dependency issue there in cpuid-bool between the newest version of polyval crate and the current latest version of the sha2 crate. The bytes dependency in protocol that was causing duplicate dependencies was a red herring - actually bytes was not used with the protocol crate! Supplants #164 update prost Fixes #221 update jni
2021-02-24 17:08:46 +01:00
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "wasm-bindgen"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.87"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "7706a72ab36d8cb1f80ffbf0e071533974a60d0a308d01a5d0375bf60499a342"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Simplify curve25519-dalek dependency Signal has a fork of curve25519-dalek to add some features that are used by zkgroup. However, libsignal-protocol and poksho don't use those features directly, and thus they don't depend on our fork specifically. Anyone outside of Signal using libsignal-protocol can thus use the standard curve25519-dalek and avoid building it twice. Signal will continue using our fork thanks to the workspace patch in the root Cargo.toml. Additionally, remove all the passthrough features for customizing curve25519-dalek; we don't use any of them, and clients can always specify them directly.
2021-08-18 02:27:24 +02:00
"cfg-if",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.87"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "5ef2b6d3c510e9625e5fe6f509ab07d66a760f0885d858736483c32ed7809abd"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"bumpalo",
"log",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"once_cell",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-macro"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.87"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "dee495e55982a3bd48105a7b947fd2a9b4a8ae3010041b9e0faab3f9cd028f1d"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.87"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "54681b18a46765f095758388f2d0cf16eb8d4169b639ab575a8f5693af210c7b"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.2.87"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "ca6ad05a4870b2bf5fe995117d3728437bd27d7cd5f06f13c17443ef369775a1"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "web-sys"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.3.64"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "9b85cbef8c220a6abc02aefd892dfc0fc23afb1c6a426316ec33253a3877249b"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
[[package]]
name = "which"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "4.4.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "2441c784c52b289a054b7201fc93253e288f094e2f4be9058343127c4226a269"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies - cargo update - But stay on our fork of curve25519-dalek (pinned at 3.0.0) - Update x25519-dalek from 1.0 to 1.1 (instead of 1.2) to stay compatible with curve25519-dalek - Update cpufeatures to 2.1 to match our dependencies - Note that updating picky* resulted in more duplicate crates (rand*) - Pin num-bigint-dig to a build that supports Cargo's -Zbuild-std, because xargo + autocfg has stopped working with the new toolchain - Remove xargo in favor of -Zbuild-std
2021-10-06 01:32:42 +02:00
"either",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"libc",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
"once_cell",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
"winapi",
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e686886bc078bc1b0b600cac0147aadb815089b6e4da64016cbd754b6342700f"
dependencies = [
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-targets 0.48.1",
]
[[package]]
name = "windows-sys"
version = "0.45.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75283be5efb2831d37ea142365f009c02ec203cd29a3ebecbc093d52315b66d0"
dependencies = [
"windows-targets 0.42.2",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows-targets 0.48.1",
]
[[package]]
name = "windows-targets"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8e5180c00cd44c9b1c88adb3693291f1cd93605ded80c250a75d472756b4d071"
dependencies = [
"windows_aarch64_gnullvm 0.42.2",
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
"windows_x86_64_gnullvm 0.42.2",
"windows_x86_64_msvc 0.42.2",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
[[package]]
name = "windows-targets"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.48.1"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "05d4b17490f70499f20b9e791dcf6a299785ce8af4d709018206dc5b4953e95f"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
"windows_aarch64_gnullvm 0.48.0",
"windows_aarch64_msvc 0.48.0",
"windows_i686_gnu 0.48.0",
"windows_i686_msvc 0.48.0",
"windows_x86_64_gnu 0.48.0",
"windows_x86_64_gnullvm 0.48.0",
"windows_x86_64_msvc 0.48.0",
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
]
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "597a5118570b68bc08d8d59125332c54f1ba9d9adeedeef5b99b02ba2b0698f8"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "91ae572e1b79dba883e0d315474df7305d12f569b400fcf90581b06062f7e1bc"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e08e8864a60f06ef0d0ff4ba04124db8b0fb3be5776a5cd47641e942e58c4d43"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2ef27e0d7bdfcfc7b868b317c1d32c641a6fe4629c171b8928c7b08d98d7cf3"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_i686_gnu"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c61d927d8da41da96a81f029489353e68739737d3beca43145c8afec9a31a84f"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_i686_gnu"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "622a1962a7db830d6fd0a69683c80a18fda201879f0f447f065a3b7467daa241"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_i686_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44d840b6ec649f480a41c8d80f9c65108b92d89345dd94027bfe06ac444d1060"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_i686_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4542c6e364ce21bf45d69fdd2a8e455fa38d316158cfd43b3ac1c5b1b19f8e00"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8de912b8b8feb55c064867cf047dda097f92d51efad5b491dfb98f6bbb70cb36"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca2b8a661f7628cbd23440e50b05d705db3686f894fc9580820623656af974b1"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "26d41b46a36d453748aedef1486d5c7a85db22e56aff34643984ea85514e94a3"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7896dbc1f41e08872e9d5e8f8baa8fdd2677f29468c4e156210174edc7f7b953"
bridge: Update to jni crate 0.21 Major changes: - JNIEnv now requires &mut for most operations - "Store" objects capturing JNIEnv have to use `unsafe_clone` and promise not to persist any local references - JObjects and JValueOwneds can be used as return values now, with correct lifetimes. - Many JNIEnv APIs take &JObject instead of JObject now. - The wrapper function synthesived by #[bridge_fn] declares a 'local lifetime that can be used in arguments and return types. - Handling of arrays is much nicer - JNIEnv::with_local_frame works with any result type. For returning a newly-created object, we would use with_local_frame_returning_local, but we don't have any such cases in libsignal.
2023-08-30 02:20:06 +02:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a515f5799fe4961cb532f983ce2b23082366b898e52ffbce459c86f67c8378a"
[[package]]
name = "winnow"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "0.5.3"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "f46aab759304e4d7b2075a9aecba26228bb073ee8c50db796b2c72c676b5d807"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
dependencies = [
"memchr",
]
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
[[package]]
name = "x25519-dalek"
Update x25519-dalek to v2.0.0
2023-08-15 21:02:37 +02:00
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb66477291e7e8d2b0ff1bcb900bf29489a9692816d79874bea351e7a8b6de96"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
"rand_core",
"serde",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
"zeroize",
]
[[package]]
name = "zeroize"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
version = "1.6.0"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
checksum = "2a0956f1ba7c7909bfb66c2e9e4124ab6f6482560f6628b5aaeba39207c9aad9"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"zeroize_derive",
]
[[package]]
name = "zeroize_derive"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
version = "1.4.2"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and fix the fallout (upgrade snow to 0.9.2)
2023-05-26 03:17:16 +02:00
checksum = "ce36e65b0d2999d2aafac989fb249189a141aee1f53c612c1f37d72631959f69"
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
dependencies = [
"proc-macro2",
"quote",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"syn 2.0.28",
Track Cargo.lock for more consistent builds Normally library repositories wouldn't commit their Cargo.lock, but these libraries are built into staticlibs or cdylibs and thus escape the crates.io ecosystem for versioning. In particular, recording exact dependencies keeps us from having multiple versions of the same crate unexpectedly.
2020-11-05 19:41:57 +01:00
]
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
Introduce zkcredential crate zkcredential provides APIs for a generic form of the sort of credentials zkgroup supports
2023-04-17 20:10:02 +02:00
[[package]]
name = "zkcredential"
version = "0.1.0"
dependencies = [
"bincode",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
Introduce zkcredential crate zkcredential provides APIs for a generic form of the sort of credentials zkgroup supports
2023-04-17 20:10:02 +02:00
"displaydoc",
"hex",
"lazy_static",
"poksho",
"serde",
]
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
[[package]]
name = "zkgroup"
version = "0.9.0"
dependencies = [
"aes-gcm-siv",
zkgroup: Add a generate-server-params binary generate-server-params takes existing server params through stdin (base64-encoded) and generates randomness for any new keys have been added since last time. As long as new keys are always added to the end of ServerSecretParams and ServerPublicParams, this allows updating zkgroup without breaking existing credentials.
2021-11-17 22:10:34 +01:00
"base64",
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
"bincode",
"criterion",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"curve25519-dalek",
zkgroup: Tidy up error handling - Use displaydoc to stringify the errors, using the comments that were already there. These go into the string descriptions for errors exposed to the apps, which can be useful. - Split PointDecodeError into its own type so that it's not exposed generally.
2021-10-23 03:11:15 +02:00
"displaydoc",
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
"hex",
zkgroup: Optimize credential presentation and FFI cleanup Optimize presentation of credentials (AuthCredentialPresentationV2, ProfileKeyCredentialPresentationV2, PniCredentialPresentationV2). Server will accept V1 or V2 presentations. Clients will produce V2. Various improvements to FFI to support this, and some minor optimizations (in particular "lazy statics" to avoid redundant loading of SystemParams).
2022-04-06 20:07:08 +02:00
"lazy_static",
zkgroup: Add support for encoding ServiceIds in UidStructs This does mean that the 'bytes' field in a UidStruct isn't as useful anymore, because it can't distinguish different kinds of ServiceIds without extra work. Unfortunately, it was serialized inside a client-stored AuthCredential, so we can't just change it or take it out. Fortunately, nothing actually reads this field anyway except when decrypting, so it's okay to change how decryption works and ignore the 'bytes' field going forward.
2023-07-12 02:46:57 +02:00
"libsignal-protocol",
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
"poksho",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"rand",
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
"serde",
Update dependencies following curve25519-dalek 4.0.0 release Co-authored-by: Jordan Rose <jrose@signal.org>
2023-08-10 00:04:41 +02:00
"sha2",
Add unidentified access key derivation method
2023-02-08 11:42:42 +01:00
"signal-crypto",
zkgroup: Add a "Create Call Link" credential This will allow a user to request to create a call link from the chat server without revealing anything about the room, and then later actually create it by giving the room ID to the calling server without identifying themself. This involves a new, stripped-down GenericServer{Secret,Public}Params, which currently only contains a generic "zkcredential" key. Apart from the calling server not needing to handle all the credentials that the group storage server supports, the structure of zkcredential means it is safe to use the same key for multiple kinds of credentials. Similarly, CallLink{Secret,Public}Params plays the same role as Group{Secret,Public}Params for encrypting user IDs when talking to the calling server. Following from that, the APIs for CreateCallLinkCredentials are located on the individual types (RequestContext, Request, Response, Credential, Presentation) rather than all being on the Server*Params types; adding a new credential type won't change the API of the Server*Params types at all. The main Server*Params may make use of zkcredential in the future as well, but for now it's only for new Signal servers that want to use zero-knowledge credentials.
2023-04-26 01:53:42 +02:00
"subtle",
zkgroup: Add support for encoding ServiceIds in UidStructs This does mean that the 'bytes' field in a UidStruct isn't as useful anymore, because it can't distinguish different kinds of ServiceIds without extra work. Unfortunately, it was serialized inside a client-stored AuthCredential, so we can't just change it or take it out. Fortunately, nothing actually reads this field anyway except when decrypting, so it's okay to change how decryption works and ignore the 'bytes' field going forward.
2023-07-12 02:46:57 +02:00
"uuid",
Introduce zkcredential crate zkcredential provides APIs for a generic form of the sort of credentials zkgroup supports
2023-04-17 20:10:02 +02:00
"zkcredential",
Add zkgroup to the Rust workspace - Bump the version to 0.9.0, mainly so it doesn't get confused with the original repo. - Use the poksho in this repo and our custom 3.0.0-lizard2 branch of curve25519-dalek (instead of a 2.0.0-based one). - Bump the sha2 dependency to match curve25519-dalek 3.0. - Remove the reference to the crate's ffi module. With this, the tests pass and the benchmarks run.
2021-10-22 01:56:31 +02:00
]
Copy Permalink