Struct aws_sdk_iot::types::CustomCodeSigning

#[non_exhaustive]
pub struct CustomCodeSigning {
    pub signature: Option<CodeSigningSignature>,
    pub certificate_chain: Option<CodeSigningCertificateChain>,
    pub hash_algorithm: Option<String>,
    pub signature_algorithm: Option<String>,
}

Describes a custom method used to code sign a file.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

signature: Option<CodeSigningSignature>

The signature for the file.

certificate_chain: Option<CodeSigningCertificateChain>

The certificate chain.

hash_algorithm: Option<String>

The hash algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses SHA256 or SHA1, so you can pass either of them based on which was used for generating the signature.

signature_algorithm: Option<String>

The signature algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses ECDSA or RSA, so you can pass either of them based on which was used for generating the signature.

Implementations

impl CustomCodeSigning

pub fn signature(&self) -> Option<&CodeSigningSignature>

The signature for the file.

pub fn certificate_chain(&self) -> Option<&CodeSigningCertificateChain>

The certificate chain.

pub fn hash_algorithm(&self) -> Option<&str>

The hash algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses SHA256 or SHA1, so you can pass either of them based on which was used for generating the signature.

pub fn signature_algorithm(&self) -> Option<&str>

The signature algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses ECDSA or RSA, so you can pass either of them based on which was used for generating the signature.

impl CustomCodeSigning

pub fn builder() -> CustomCodeSigningBuilder

Creates a new builder-style object to manufacture CustomCodeSigning.

Trait Implementations

impl Clone for CustomCodeSigning

fn clone(&self) -> CustomCodeSigning

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CustomCodeSigning

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for CustomCodeSigning

fn eq(&self, other: &CustomCodeSigning) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for CustomCodeSigning