xmppftw/xmpp-rs
Watch
1
0
Fork
You've already forked xmpp-rs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
xmpp-rs/tokio-xmpp/Cargo.toml

96 lines
3.3 KiB
TOML
Raw Permalink Normal View History

this ain't work
2017-06-02 00:42:57 +02:00
[package]
name = "tokio-xmpp"
Release all crates Since we tie the versions rather tightly, we have to release the entire bunch in order to allow people to upgrade to rxml 0.14.
2026-06-10 17:48:26 +02:00
version = "6.0.0"
tokio-xmpp: extend authors in Cargo.toml
2021-01-13 17:21:49 +01:00
authors = ["Astro <astro@spaceboyz.net>", "Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>", "pep <pep+code@bouah.net>", "O01eg <o01eg@yandex.ru>", "SonnyX <randy@vonderweide.nl>", "Paul Fariello <paul@fariello.eu>"]
tokio-xmpp 0.1.1
2018-08-01 00:28:24 +02:00
description = "Asynchronous XMPP for Rust with tokio"
license = "MPL-2.0"
Update repo and homepage in Cargo.toml files Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-10-20 01:04:22 +02:00
homepage = "https://gitlab.com/xmpp-rs/xmpp-rs"
repository = "https://gitlab.com/xmpp-rs/xmpp-rs"
tokio-xmpp 0.1.1
2018-08-01 00:28:24 +02:00
documentation = "https://docs.rs/tokio-xmpp"
tokio-xmpp 0.1.2
2018-08-03 01:16:42 +02:00
categories = ["asynchronous", "network-programming"]
keywords = ["xmpp", "tokio"]
Update edition to 2021 - Remove TryFrom/Into and FromIterator imports - Prevent impl_validator_using_provider macro in sasl crate from constructing trait object Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2023-11-11 14:52:55 +01:00
edition = "2021"
this ain't work
2017-06-02 00:42:57 +02:00
[dependencies]
tokio-xmpp: Bump tokio to 1.0 and replace tokio-tls with tokio-native-tls
2020-12-04 17:33:55 +01:00
bytes = "1"
tokio-xmpp: rewrite for futures-0.3
2020-03-05 01:25:24 +01:00
futures = "0.3"
tokio-xmpp: Add some ugly premature logging useful for debugging Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2019-12-09 03:34:28 +01:00
log = "0.4"
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
tokio = { version = "1", features = ["net", "rt", "rt-multi-thread", "macros", "io-util"] }
tokio_xmpp: implement IQ tracking
2025-01-26 11:10:44 +01:00
tokio-stream = { version = "0.1", features = ["sync"] }
tokio-xmpp: Bump rustls-native-certs and webpki-roots skip-changelog: This is just a dependency bump.
2025-07-28 15:06:01 +02:00
webpki-roots = { version = "1", optional = true }
rustls-native-certs = { version = "0.8", optional = true }
Bump rxml to 0.14.0
2025-09-28 09:40:44 +02:00
rxml = { version = "0.14.0", features = ["compact_str", "tokio"] }
Bump all outdated dependencies skip-changelog: This isn’t a user-facing change.
2026-05-17 20:38:20 +02:00
rand = "0.10"
tokio-xmpp: Add syntax highlighting to debug logs This uses syntect, and has been checked to have zero overhead when it is disabled.
2023-06-18 14:21:49 +02:00
syntect = { version = "5", optional = true }
tokio_xmpp: introduce xmlstream module This module provides XSO-based parsing, proper typestates and will soon replace the proto module.
2024-08-07 15:52:55 +02:00
pin-project-lite = { version = "0.2" }
use thiserror in tokio-xmpp and minidom
2025-10-12 00:31:48 +02:00
thiserror = "2.0"
Use relative cargo paths when using local copy
2023-12-18 13:06:22 +01:00
# same repository dependencies
Relative dependencies
2024-08-12 10:16:15 +02:00
sasl = { version = "0.5", path = "../sasl" }
Release all crates Since we tie the versions rather tightly, we have to release the entire bunch in order to allow people to upgrade to rxml 0.14.
2026-06-10 17:48:26 +02:00
xmpp-parsers = { version = "0.23", path = "../parsers", features = [ "log" ] }
xso = { version = "0.4", path = "../xso" }
jid: Add serde support behind feature Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2020-04-30 23:19:06 +02:00
DNS/TLS deps are now optional, component now also uses ServerConnector
2023-12-30 22:08:37 -05:00
# these are only needed for starttls ServerConnector support
tokio-xmpp: update hickory-dns to 0.26
2026-05-14 20:45:37 +02:00
hickory-resolver = { version = "0.26", optional = true}
tokio-xmpp: Update dependencies Update tokio_rustls, idna, webpki_roots. https://github.com/rustls/rustls/releases/tag/v%2F0.22.0 > ConfigBuilder::with_safe_defaults - calls to this can simply be deleted since safe defaults are now implicit. > OwnedTrustAnchor - use rustls_pki_types::TrustAnchor instead, and replace from_subject_spki_name_constraints with direct assignment to the struct fields. `RootCertStore::add_trust_anchors` seems to be removed too. Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2024-07-25 20:51:20 +02:00
idna = { version = "1.0", optional = true}
DNS/TLS deps are now optional, component now also uses ServerConnector
2023-12-30 22:08:37 -05:00
native-tls = { version = "0.2", optional = true }
tokio-native-tls = { version = "0.3", optional = true }
Avoid enabling multiple rustls backends by accident For this, we had to: - Make the choice(s) of backend explicit in tokio-xmpp features - Avoid picking a backend through transitive dependencies in xmpp (reqwest->hyper->rustls). In addition, we choose the default rustls backend by default and adapt the examples so that they can cope with either situation.
2025-05-10 09:54:01 +02:00
tokio-rustls = { version = "0.26", optional = true, default-features = false, features = ["logging", "tls12"] }
tokio-xmpp: Add support for kernel TLS This drastically improve the debuggability of the network parts, by moving the task of encrypting/decrypting TLS packets from userland to the kernel. This makes them appear in clear in strace as sendto() and recvfrom(). I introduced a new tls-rust-ktls feature which depends on both rustls and ktls, but isn’t enabled by default since it probably isn’t available on every computer. It requires the tls kernel module to be loaded, which then can offload encryption/decryption to dedicated hardware if available. I have tested this change on Linux 6.11 on a rk3588.
2024-09-11 20:34:38 +02:00
ktls = { version = "6", optional = true }
DNS/TLS deps are now optional, component now also uses ServerConnector
2023-12-30 22:08:37 -05:00
RUST_LOG=debug can now be used in tokio-xmpp examples to see XMPP network traffic
2023-06-05 13:06:52 +02:00
[dev-dependencies]
Bump all dependencies but rustls and webpki-roots The latter have changed their API a bit, while everything else is still compatible.
2024-04-25 21:01:29 +02:00
env_logger = { version = "0.11", default-features = false, features = ["auto-color", "humantime"] }
Add disabled-by-default insecure-tcp feature to tokio-xmpp for use by component connections
2024-01-01 01:13:51 -05:00
# this is needed for echo-component example
tokio_xmpp: add example to demonstrate stream management
2024-08-29 12:55:29 +02:00
tokio = { version = "1", features = ["signal", "test-util"] }
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
tokio-xmpp = { path = ".", default-features = false, features = ["rustls-native-certs"]}
[[example]]
name = "contact_addr"
tokio-xmpp: simplify examples by requiring specific TLS features
2025-05-10 16:41:35 +02:00
required-features = ["starttls", "aws_lc_rs"]
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
[[example]]
name = "download_avatars"
tokio-xmpp: simplify examples by requiring specific TLS features
2025-05-10 16:41:35 +02:00
required-features = ["starttls", "aws_lc_rs"]
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
[[example]]
name = "echo_bot"
tokio-xmpp: simplify examples by requiring specific TLS features
2025-05-10 16:41:35 +02:00
required-features = ["starttls", "aws_lc_rs"]
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
[[example]]
name = "echo_component"
required-features = ["starttls", "insecure-tcp"]
[[example]]
name = "echo_server"
tokio-xmpp: simplify examples by requiring specific TLS features
2025-05-10 16:41:35 +02:00
required-features = ["starttls", "aws_lc_rs"]
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
[[example]]
name = "keep_connection"
required-features = ["starttls"]
RUST_LOG=debug can now be used in tokio-xmpp examples to see XMPP network traffic
2023-06-05 13:06:52 +02:00
jid: Add serde support behind feature Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2020-04-30 23:19:06 +02:00
[features]
tokio-xmpp/client: add directTLS connection method
2025-05-30 14:05:28 +02:00
default = ["direct-tls", "starttls", "aws_lc_rs", "rustls-native-certs"]
Add `dns` feature for DNS stuff (not just in starttls)
2024-08-05 15:09:59 +02:00
starttls = ["dns"]
tokio-xmpp/client: add directTLS connection method
2025-05-30 14:05:28 +02:00
direct-tls = ["dns"]
Clean up tls-related feature flags This provides a clear and consistent interface for selecting TLS-related features on both (xmpp and tokio-xmpp) crates. All feature checks have been revamped. All working combinations have been tested (including a connectivity test + --all-features docs build) using: ``` set -xeuo pipefail features=(aws_lc_rs ring ktls,aws_lc_rs ktls,ring aws_lc_rs,ring aws_lc_rs,ring,ktls native-tls rustls-any-backend) export RUSTFLAGS=" -D warnings" cargo test --no-default-features cargo test for feature in ${features[@]}; do echo ">>> BUILDING with $feature" 2>&1 # Running code or building examples cannot succeed with rustls-any-backend. features="starttls,$feature" if [ "$feature" != 'rustls-any-backend' ]; then if ! cargo test --no-default-features --features="$features"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi set +e timeout -sINT -p -k 2 3 cargo run --no-default-features --features="$features" --example keep_connection -- test@hub.sotecware.net "$(pass xmpp/test@hub.sotecware.net)" status="$?" set -e if [ $status -ne 0 ]; then echo ">>> keep_connection did not shut down cleanly! (status: $status)" >&2 exit 1 fi else if ! cargo build --no-default-features --features="$feature"; then echo ">>> BUILD FAILED for tls feature set: $features" >&2 exit 1 fi fi done RUSTDOCFLAGS="--cfg docsrs" RUSTFLAGS="--cfg xmpprs_doc_build" cargo +nightly doc -Zrustdoc-map --all-features ```
2025-05-10 10:45:43 +02:00
aws_lc_rs = ["rustls-any-backend", "tokio-rustls/aws_lc_rs"]
ring = ["rustls-any-backend", "tokio-rustls/ring"]
native-tls = ["dep:tokio-native-tls", "dep:native-tls"]
ktls = ["rustls-any-backend", "dep:ktls"]
rustls-any-backend = ["dep:tokio-rustls"]
rustls-native-certs = ["dep:rustls-native-certs"]
webpki-roots = ["dep:webpki-roots"]
insecure-tcp = []
tokio-xmpp: Add syntax highlighting to debug logs This uses syntect, and has been checked to have zero overhead when it is disabled.
2023-06-18 14:21:49 +02:00
syntax-highlighting = ["syntect"]
Add serde feature for xmpp crate
2024-06-05 11:13:29 +02:00
# Enable serde support in jid crate
serde = [ "xmpp-parsers/serde" ]
Add `dns` feature for DNS stuff (not just in starttls)
2024-08-05 15:09:59 +02:00
# Required by starttls, and used by insecure-tcp by default
dns = [ "hickory-resolver", "idna" ]
tokio-xmpp: Add 'component' feature Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
2024-11-09 17:36:11 +01:00
component = ["xmpp-parsers/component", "insecure-tcp"]
Fix build with nightly rust Nightly rust complains about `cfg(..)` tests against undeclared features and other unknown cfgs. They need to be explicitly declared now. The nightly/stable features don't exist, so I removed them and substitutes the currently correct number for the single test where they were used. The `xmpprs_doc_build` cfg flag is now declared as expectable.
2024-06-16 10:45:09 +02:00
Stop being pedantic by default Up to now, the xmpp-rs projects have been very strict about incoming data. This has served us, as developers of the libraries, well, uncovering bugs in our and remote implementations which we could then get fixed. However, this behaviour is unexpected to users of the library. In the XMPP world, unexpected child elements and attributes are generally expected to be ignored. While this could be opted-into previously, the feature flag for that sounded more dangerous than it was ("disable-validation"). In addition, the tribal knowledge needed to know about that feature flag may not have reached some people who tried the library and gave up because of that. With this change, we make the non-pedantic behaviour the default. For development and debugging purposes, users can always opt into the pedantic behaviour as needed, using the newly-introduced `pedantic` feature flags on all affected crates.
2026-03-27 12:07:53 +01:00
pedantic = ["xmpp-parsers/pedantic"]
tokio-xmpp: add option to disable xmpp_parsers validation
2026-02-16 21:38:55 +01:00
Fix build with nightly rust Nightly rust complains about `cfg(..)` tests against undeclared features and other unknown cfgs. They need to be explicitly declared now. The nightly/stable features don't exist, so I removed them and substitutes the currently correct number for the single test where they were used. The `xmpprs_doc_build` cfg flag is now declared as expectable.
2024-06-16 10:45:09 +02:00
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(xmpprs_doc_build)'] }
Reference in a new issue Copy permalink