1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251
// Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
// SPDX-License-Identifier: Apache-2.0
//! Utilities to handle passing Rust code to s2n-tls's C callbacks.
//!
//! s2n-tls uses callbacks to temporarily return control to the application
//! and allow the application to execute custom code.
//!
//! To use a callback in your application, just implement the trait for the
//! target callback type and pass your implementation to the appropriate
//! connection or config method. For example, you can implement
//! [`ClientHelloCallback`] and pass that implementation to
//! [config::Builder::set_client_hello_callback()](`crate::config::Builder::set_client_hello_callback()`)
//! in order to execute custom logic after an s2n-tls server receives a client hello.
//!
//! s2n-tls callbacks come in two flavors:
//! * "sync" callbacks return an immediate result and will block the task
//! performing the handshake until they return success or failure. See
//! [`VerifyHostNameCallback`] as an example.
//! * "async" callbacks return a [`Poll`] and should not block the task performing the handshake.
//! They will be polled until they return [`Poll::Ready`].
//! [Connection::waker()](`crate::connection::Connection::waker()`)
//! can be used to register the task for wakeup. See [`ClientHelloCallback`] as an example.
use crate::{
config::Config,
connection::{Connection, InternalConnectionFuture},
enums::CallbackResult,
error::Error,
};
use core::{mem::ManuallyDrop, ptr::NonNull, task::Poll, time::Duration};
use pin_project_lite::pin_project;
use s2n_tls_sys::s2n_connection;
use std::{future::Future, pin::Pin};
/// Convert the connection pointer provided to a callback into a Connection
/// useable with the Rust bindings.
///
/// # Safety
///
/// This must ONLY be used for connection pointers provided to callbacks,
/// which can be assumed to point to valid Connections because the
/// callbacks were configured through the Rust bindings.
pub(crate) unsafe fn with_connection<F, T>(conn_ptr: *mut s2n_connection, action: F) -> T
where
F: FnOnce(&mut Connection) -> T,
{
let raw = NonNull::new(conn_ptr).expect("connection should not be null");
let mut conn = Connection::from_raw(raw);
let r = action(&mut conn);
// Since this is a callback, it receives a pointer to the connection
// but doesn't own that connection or control its lifecycle.
// Do not drop / free the connection.
let _ = ManuallyDrop::new(conn);
r
}
/// Begins execution of an asyc callback.
///
/// Polls the async callback once, then registers it for later retries if
/// necessary.
///
/// The C-style callback method passed to the underlying s2n-tls implementation
/// should call this method instead of using the Rust callback implementation
/// directly. The C-style callback will only execute once, so the underlying
/// poll implementation should ensures that the Rust callback is polled until
/// it completes.
///
/// Using [`config::set_client_hello_callback`] as an example, the execution
/// roughly looks like:
///
/// Connection::poll_negotiate (Rust)
/// | s2n_negotiate (C)
/// | | s2n_client_hello_cb (C)
/// | | | trigger_async_client_hello_callback (Rust)
/// | | | | on_client_hello_callback (Rust)
/// | | | | | ClientHelloCallback::on_client_hello (Rust)
/// | | | | | +-> return Ok(Some(ConnectionFuture)) (Rust)
/// | | | | +-> return Poll::Pending (Rust)
/// | | | +-> return Callback::Success (Rust)
/// | | +-> return S2N_SUCCESS (C)
/// | +-> return S2N_ERR_T_BLOCKED (C)
/// +-> return Poll::Pending (Rust)
///
/// Connection::poll_negotiate (Rust)
/// | ConnectionFuture::poll (Rust)
/// | +-> return Poll::Pending (Rust)
/// +-> return Poll::Pending (Rust)
///
/// Connection::poll_negotiate (Rust)
/// | ConnectionFuture::poll (Rust)
/// | +-> return Poll::Ready (Rust)
/// | s2n_negotiate (C)
/// |
/// v ...handshake continues.
///
/// Note that "s2n_client_hello_cb" is only called once.
/// After the initial call, the retries are handled by the Rust bindings.
/// s2n_negotiate is not called again until the callback completes.
///
pub(crate) fn trigger_async_client_hello_callback(conn: &mut Connection) -> CallbackResult {
// Try once first.
match on_client_hello_callback(conn) {
// If callback completes, no need for retry.
Poll::Ready(r) => r.into(),
// If callback doesn't complete, prepare connection for retry.
Poll::Pending => CallbackResult::Success,
}
}
/// The Future associated with the async connection callback.
///
/// The calling application can provide an instance of [`ConnectionFuture`]
/// when implementing an async callback, eg. [`ClientHelloCallback`], if it wants
/// to run an asynchronous operation (disk read, network call). The application
/// can return an error ([`Err(error::Error::application())`]), to indicate
/// connection failure.
///
/// [`ConfigResolver`] should be used if the application wants to set a new
/// [`Config`] on the connection.
pub trait ConnectionFuture {
fn poll(
self: Pin<&mut Self>,
connection: &mut Connection,
ctx: &mut core::task::Context,
) -> Poll<Result<(), Error>>;
}
// For more information on projection:
// https://doc.rust-lang.org/std/pin/index.html#projections-and-structural-pinning
pin_project! {
/// An implementation of [`ConnectionFuture`] which resolves the provided
/// future and sets the config on the [`connection::Connection`].
pub struct ConfigResolver<F: Future<Output = Result<Config, Error>>> {
#[pin]
fut: F,
}
}
impl<F: Future<Output = Result<Config, Error>>> ConfigResolver<F> {
pub fn new(fut: F) -> Self {
ConfigResolver { fut }
}
}
// Useful for propagating [`error::Error`] from the ClientHelloCallback
// to the Application
struct ErrorFuture {
error: Option<Error>,
}
impl ConnectionFuture for ErrorFuture {
fn poll(
mut self: Pin<&mut Self>,
_connection: &mut Connection,
_ctx: &mut core::task::Context,
) -> Poll<Result<(), Error>> {
let err = self.error.take().expect(
"ErrorFuture should be initialized with Some(error) and a Future should never
be polled after it returns Poll::Ready",
);
Poll::Ready(Err(err))
}
}
impl<F: Future<Output = Result<Config, Error>>> ConnectionFuture for ConfigResolver<F> {
fn poll(
self: Pin<&mut Self>,
connection: &mut Connection,
ctx: &mut core::task::Context,
) -> Poll<Result<(), Error>> {
let this = self.project();
let config = match this.fut.poll(ctx) {
Poll::Ready(config) => config?,
Poll::Pending => return Poll::Pending,
};
connection.set_config(config)?;
Poll::Ready(Ok(()))
}
}
/// A trait for the callback executed after parsing the TLS Client Hello.
///
/// Use in conjunction with
/// [config::Builder::set_client_hello_callback](`crate::config::Builder::set_client_hello_callback()`).
pub trait ClientHelloCallback {
/// The application can return a `Ok(None)` to resolve the client_hello_callback
/// synchronously or return a `Ok(Some(ConnectionFuture))` if it wants to
/// run some asynchronous task before resolving the callback.
///
/// [`ConfigResolver`], which implements [`ConnectionFuture`] can be
/// returned if the application wants to set a new [`Config`] on the connection.
///
/// If the server_name is used to configure the connection then the application
/// must call [`connection::Connection::server_name_extension_used()`].
fn on_client_hello(
// this method takes an immutable reference to self to prevent the
// Config from being mutated by one connection and then used in another
// connection, leading to undefined behavior
&self,
connection: &mut Connection,
) -> Result<Option<Pin<Box<dyn ConnectionFuture>>>, Error>;
}
// Calls the ClientHelloCallback and sets connection future if the application
// provided one.
fn on_client_hello_callback(conn: &mut Connection) -> Poll<Result<(), Error>> {
let async_future = conn
.config()
.as_mut()
.and_then(|config| config.context_mut().client_hello_callback.as_mut())
.and_then(|callback| callback.on_client_hello(conn).transpose());
match async_future {
Some(fut) => {
// Return a ErrorFuture and propagates the error back up to
// the application.
let fut = fut.unwrap_or_else(|err| Box::pin(ErrorFuture { error: Some(err) }));
// The callback returned a future so store it on the
// connection. This is Asynchronous resolution.
conn.set_connection_future(InternalConnectionFuture::ClientHello(fut));
Poll::Pending
}
None => {
// Done with the client_hello_callback. This is Synchronous resolution.
Poll::Ready(conn.mark_client_hello_cb_done())
}
}
}
/// A trait for the callback used to verify host name(s) during X509
/// verification.
///
/// The implementation should verify the certificate host name and return `true`
/// if the name is valid, `false` otherwise.
pub trait VerifyHostNameCallback {
fn verify_host_name(&self, host_name: &str) -> bool;
}
/// A trait for the callback used to retrieve the system / wall clock time.
pub trait WallClock {
fn get_time_since_epoch(&self) -> Duration;
}
/// A trait for the callback used to retrieve the monotonic time.
pub trait MonotonicClock {
fn get_time(&self) -> Duration;
}