Skip to main content

SanitizationProtectedDecodeExt

Trait SanitizationProtectedDecodeExt 

Source
pub trait SanitizationProtectedDecodeExt {
    // Required methods
    fn decode_sanitization_protected_bytes<const N: usize>(
        &self,
        input: &SecretInput<'_>,
    ) -> Result<LockedSecretBytes<N>, SanitizationProtectedDecodeError>;
    fn decode_sanitization_protected_vec<const MAX: usize>(
        &self,
        input: &SecretInput<'_>,
    ) -> Result<LockedSecretVec, SanitizationProtectedDecodeError>;
}
Expand description

2.0 decode helpers with separately protected staging and destination.

Both mappings are established under the companion’s required protection request before SecretFrame receives the encoded input. The input, staging, and destination are separate logical ranges. Invalid input wipes both mappings before the error is returned.

For provider-owned quarantine, generation accounting, and single-allocation no-copy finalization, use Base64::decode_assured with base64_ng::assurance::ProtectedSecret instead. A sanitization mapping cannot be claimed as a core assurance allocation because its raw ownership and teardown state are intentionally not exported.

Required Methods§

Source

fn decode_sanitization_protected_bytes<const N: usize>( &self, input: &SecretInput<'_>, ) -> Result<LockedSecretBytes<N>, SanitizationProtectedDecodeError>

Decode exactly N bytes through protected staging into protected final storage.

§Errors

Returns a redacted protection, integrity, decode, or exact-length failure. Protection failures occur before decoder work.

Source

fn decode_sanitization_protected_vec<const MAX: usize>( &self, input: &SecretInput<'_>, ) -> Result<LockedSecretVec, SanitizationProtectedDecodeError>

Decode into a protected dynamic destination with public capacity MAX.

Both mappings allocate MAX bytes before decoder work. This makes the Base64-owned allocation shape independent of frame validity while bounding memory use to two protected mappings of MAX bytes.

§Errors

Returns a redacted protection, integrity, decode, or protected-length failure.

Dyn Compatibility§

This trait is not dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementations on Foreign Types§

Source§

impl<S: Codec> SanitizationProtectedDecodeExt for Base64<S>

Implementors§