API documentation for the Rust `ConfigTls` enum in crate `dropshot`.

Light

Light

this is my http/3 server code [package] name = "http3_server" version = "0.1.0" edition = "2024" [dependencies] bytes = "1.10.1" h3 = "0.0.6" h3-quinn = "0.0.7" http = "1.2.0" quinn = "0.11.6" rustls = "0.23.23" rustls-pemfile = "2.2.0" tokio = { version = "1.43.0", features = ["full"] } use std::{error::Error, fs::File, io::BufReader}; use h3::server::Connection; use quinn::{Endpoint, ServerConfig}; use rustls::pki_types::{PrivateKeyDer, pem::PemObject}; use rustls_pemfile::certs; #[tokio::main] async fn main() -> Result<(), Box<dyn Error>> { let addr = "[::1]:3000".parse()?; let server_config = load_server_config()?; let server = Endpoint::server(server_config, addr)?; while let Some(incoming) = server.accept().await { let incoming = incoming.await?; println!("{:#?}", incoming.remote_address()); // 处理 QUIC 连接 let task = async move { let h3_conn = h3_quinn::Connection::new(incoming); let mut h3_conn = Connection::new(h3_conn).await.unwrap(); while let Some((_req, mut stream)) = h3_conn.accept().await.unwrap() { let response = http::Response::builder().status(200).body(()).unwrap(); stream.send_response(response).await.unwrap(); let data = bytes::Bytes::from_static(&b"Hello from HTTP/3!"[..]); stream.send_data(data).await.unwrap(); stream.finish().await.unwrap(); } }; tokio::spawn(task); } Ok(()) } fn load_server_config() -> Result<ServerConfig, Box<dyn Error>> { let mut cert_file = BufReader::new(File::open("cert.pem")?); let key_file = BufReader::new(File::open("key.pem")?); let cert_chain: Vec<_> = certs(&mut cert_file).collect::<Result<Vec<_>, _>>()?; let key = PrivateKeyDer::from_pem_reader(key_file)?; Ok(ServerConfig::with_single_cert(cert_chain, key)?) }

Hello Rust Community! I am new to async Rust and have moderate experience of writing sync code in Rust. I am writing a TCP server with TLS support for learning purpose. I want to choose certificates based on the hostname specified in **ClientHello**. Certificates will be fetched from other key store making it perfect usecase for async. I have read several options, but none provides a concrete example on how to do it. 1. I came to know about `cert_resolver` in `rustls::server::ServerConfig`. But from my understanding it is not async, and as mentioned in rustls documentation: > For applications that use async I/O and need to do I/O to choose a certificate (for instance, fetching a certificate from a data store), the `Acceptor` interface is more suitable. Ok, good.But if I go to `Acceptor` documentaion, I go blank on how to use it with async runtime like tokio? I could not get clear idea of how to use this struct when working with tokio as `tokio_rustls::TlsAcceptor` does not have similar methods like `read_tls` in `rustls`. 2. I also referred to alternatives like `tokio_native_tls`. But again same issue, not a single example available or I could not find it. What is recommended way of achieving this functionality when using tokio? An minimal example is very much appreciated. Thank you!

Website Media Files Displaying a Recurring Issue A recent review of media files on a local news website has revealed a consistent and concerning problem: all images are displaying as the same, small, transparent placeholder image. This widespread issue indicates a likely malfunction in the website's image handling process, rather than simply a few missing images. The affected media spans a wide range of events and topics, including coverage of local fairs (Lake County and Montana State), government meetings (Missoula County Commissioners, Montana Fish and Wildlife Commissioners), community events (Missoula Pride), and news stories (measles exposure warning, Travis Decker murder case). Specific events documented, such as demolition derbies, livestock auctions, queen contests, and various fair competitions (horse show, BBQ competition, arts & crafts), are all affected by the placeholder image problem. Similarly, videos covering political figures (JD Vance, Trump), hospital groundbreaking ceremonies, and other news items also show this same recurring media issue. This isn’t merely a case of isolated broken links; the uniformity of the placeholder image points to a more systemic problem. Possible causes include incorrect image URLs in the website's database, errors in how the website manages image uploads, a faulty plugin or theme if the site uses a content management system, or potentially an issue with the website's server configuration. Troubleshooting this requires a thorough investigation of the website’s backend. This should involve examining server logs for image-related errors, verifying the accuracy of image file names in the database, and scrutinizing the website’s code responsible for generating image tags. Ultimately, the website administrator or a developer will need to address this problem to ensure accurate and complete media coverage.

A remote attacker with user privileges can exploit a stack buffer overflow in gdv-serverconfig to gain full system access as root.

Light

A remote attacker with user privileges can exploit a stack buffer overflow in gdv-serverconfig to gain full system access as root.

Learn how to fix Dovecot's Diffie-Hellman key exchange requested SSL error by generating DH parameters with OpenSSL and configuring ssl_dh properly.