Old dependencies with security issues

Running `cargo audit` generates the folowing:

```
Crate: crossbeam-epoch
Version: 0.9.18
Title: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
Date: 2026-07-06
ID: RUSTSEC-2026-0204
URL: https://rustsec.org/advisories/RUSTSEC-2026-0204
Solution: Upgrade to >=0.9.20

Crate: quinn-proto
Version: 0.11.14
Title: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly
Date: 2026-06-22
ID: RUSTSEC-2026-0185
URL: https://rustsec.org/advisories/RUSTSEC-2026-0185
Severity: 7.5 (high)
Solution: Upgrade to >=0.11.15

Crate: ring
Version: 0.16.20
Title: Some AES functions may panic when overflow checking is enabled.
Date: 2025-03-06
ID: RUSTSEC-2025-0009
URL: https://rustsec.org/advisories/RUSTSEC-2025-0009
Solution: Upgrade to >=0.17.12

Crate: rsa
Version: 0.9.10
Title: Marvin Attack: potential key recovery through timing sidechannels
Date: 2023-11-22
ID: RUSTSEC-2023-0071
URL: https://rustsec.org/advisories/RUSTSEC-2023-0071
Severity: 5.9 (medium)
Solution: No fixed upgrade is available!

Crate: rustls
Version: 0.20.9
Title: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input
Date: 2024-04-19
ID: RUSTSEC-2024-0336
URL: https://rustsec.org/advisories/RUSTSEC-2024-0336
Severity: 7.5 (high)
Solution: Upgrade to >=0.23.5 OR >=0.22.4, <0.23.0 OR >=0.21.11, <0.22.0

Crate: rustls-webpki
Version: 0.103.10
Title: Name constraints for URI names were incorrectly accepted
Date: 2026-04-14
ID: RUSTSEC-2026-0098
URL: https://rustsec.org/advisories/RUSTSEC-2026-0098
Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6

Crate: rustls-webpki
Version: 0.103.10
Title: Name constraints were accepted for certificates asserting a wildcard name
Date: 2026-04-14
ID: RUSTSEC-2026-0099
URL: https://rustsec.org/advisories/RUSTSEC-2026-0099
Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6

Crate: rustls-webpki
Version: 0.103.10
Title: Reachable panic in certificate revocation list parsing
Date: 2026-04-22
ID: RUSTSEC-2026-0104
URL: https://rustsec.org/advisories/RUSTSEC-2026-0104
Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7

Crate: async-std
Version: 1.13.2
Warning: unmaintained
Title: async-std has been discontinued
Date: 2025-08-24
ID: RUSTSEC-2025-0052
URL: https://rustsec.org/advisories/RUSTSEC-2025-0052

Crate: core2
Version: 0.4.0
Warning: unmaintained
Title: core2 is unmaintained, all versions yanked
Date: 2026-04-14
ID: RUSTSEC-2026-0105
URL: https://rustsec.org/advisories/RUSTSEC-2026-0105

Crate: ring
Version: 0.16.20
Warning: unmaintained
Title: Versions of *ring* prior to 0.17 are unmaintained.
Date: 2025-03-05
ID: RUSTSEC-2025-0010
URL: https://rustsec.org/advisories/RUSTSEC-2025-0010

Crate: rusoto_credential
Version: 0.48.0
Warning: unmaintained
Title: Rusoto is unmaintained
Date: 2022-04-24
ID: RUSTSEC-2022-0071
URL: https://rustsec.org/advisories/RUSTSEC-2022-0071

Crate: rustls-pemfile
Version: 1.0.4
Warning: unmaintained
Title: rustls-pemfile is unmaintained
Date: 2025-11-28
ID: RUSTSEC-2025-0134
URL: https://rustsec.org/advisories/RUSTSEC-2025-0134

Crate: anyhow
Version: 1.0.100
Warning: unsound
Title: Unsoundness in `Error::downcast_mut()`
Date: 2026-06-25
ID: RUSTSEC-2026-0190
URL: https://rustsec.org/advisories/RUSTSEC-2026-0190

Crate: memmap2
Version: 0.9.9
Warning: unsound
Title: Unchecked pointer offset in crate `memmap2`
Date: 2026-06-20
ID: RUSTSEC-2026-0186
URL: https://rustsec.org/advisories/RUSTSEC-2026-0186

Crate: rand
Version: 0.8.5
Warning: unsound
Title: Rand is unsound with a custom logger using `rand::rng()`
Date: 2026-04-09
ID: RUSTSEC-2026-0097
URL: https://rustsec.org/advisories/RUSTSEC-2026-0097

Crate: rand
Version: 0.9.2
Warning: unsound
Title: Rand is unsound with a custom logger using `rand::rng()`
Date: 2026-04-09
ID: RUSTSEC-2026-0097
URL: https://rustsec.org/advisories/RUSTSEC-2026-0097

Crate: core2
Version: 0.4.0
Warning: yanked

error: 8 vulnerabilities found!
warning: 10 allowed warnings found
```

The dependencies should probably be updated or swapped out in case the crates are discontinued.

Start by running `cargo audit` and reviewing the dependency declarations and lockfile that produce the listed versions. Trace which crates are direct or transitive dependencies, then update or replace the affected packages where feasible. Done means the supported dependency set is chosen, compatibility checks pass, and the reported audit findings are addressed or documented.

Written by the indexing model from the issue text.