Auditing dependencies, handling hostile input and closing the gaps attackers actually use.
Slow clients and oversized requests exhaust connections and memory. Set header and body timeouts, body size limits, concurrency limits and keep-alive bounds at the proxy and in the Axum service with Tower layers.
Treat every upload as hostile: limit the size, sniff the real content type, ignore the client filename, store outside the web root under generated names, scan where needed and serve with safe headers.
cargo yank stops new projects from selecting a version but leaves it downloadable for existing lockfiles. Learn when to yank, why it cannot remove leaked secrets, and the correct fix for a bad release.
cargo-audit checks Cargo.lock against the RustSec advisory database; cargo-deny adds license, source and duplicate-version policy. Learn what each checks, how to run them in CI and how to triage a hit.
Logs leak more secrets than breaches: derived Debug, request headers, URLs, SQL parameters and error chains. Use secrecy, custom Debug, tracing skip and filters to stop it.
Verify webhook signatures in Rust: read the raw body, compute HMAC-SHA256, compare in constant time, check the timestamp against replay and respond fast with a queue.
A review checklist for a Rust service before it faces the internet: dependencies, unsafe, input limits, authentication, secrets, transport, containers and monitoring, each with a pass condition.
Containers run as root by default. Create an unprivileged user in the image, own only what the app writes, handle low ports and volumes, and check that it works.
Set the HTTP response headers that harden a web service: Content-Security-Policy, X-Content-Type-Options, Strict-Transport-Security, Referrer-Policy and more, applied with tower-http in Axum.
Abuse prevention goes beyond a request counter: separate limits per route and identity, login throttling, lockouts without enabling denial of service, enumeration defense and cost-based limits.
Run untrusted plugins or user code from Rust inside WebAssembly with wasmtime: fuel for CPU limits, memory caps, no ambient file or network access, and host functions you choose.
Integer overflow panics in debug builds and wraps in release builds by default. Learn how that becomes a vulnerability, which arithmetic to use for untrusted numbers and how to enable checks in release.
We send one email when a new post is published. No spam.