Struct webrtc_dtls::state::State
source · pub struct State {
pub peer_certificates: Vec<Vec<u8>>,
pub identity_hint: Vec<u8>,
/* private fields */
}
Fields§
§peer_certificates: Vec<Vec<u8>>
§identity_hint: Vec<u8>
Implementations§
Trait Implementations§
source§impl KeyingMaterialExporter for State
impl KeyingMaterialExporter for State
source§fn export_keying_material<'life0, 'life1, 'life2, 'async_trait>(
&'life0 self,
label: &'life1 str,
context: &'life2 [u8],
length: usize
) -> Pin<Box<dyn Future<Output = Result<Vec<u8>, KeyingMaterialExporterError>> + Send + 'async_trait>>where
Self: 'async_trait,
'life0: 'async_trait,
'life1: 'async_trait,
'life2: 'async_trait,
fn export_keying_material<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, label: &'life1 str, context: &'life2 [u8], length: usize ) -> Pin<Box<dyn Future<Output = Result<Vec<u8>, KeyingMaterialExporterError>> + Send + 'async_trait>>where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,
export_keying_material returns length bytes of exported key material in a new slice as defined in RFC 5705. This allows protocols to use DTLS for key establishment, but then use some of the keying material for their own purposes