Wes 98c9c33ea0 fix: correct zeroize annotation placement and avoid secret cloning in protected.rs (#108) ...

S3Credentials had #[zeroize(skip)] on secret_access_key instead of
access_key_id. The comment said "access_key_id is not sensitive" but
the annotation was on the adjacent field. In practice ProtectedString
has its own #[zeroize(drop)] so the secret was still zeroed on drop,
but the annotation contradicted its own comment and would silently
break if ProtectedString's drop behavior ever changed.

ProtectedString::into_inner() cloned self.inner instead of moving it
out. Use std::mem::take to swap the value out directly, avoiding the
unnecessary heap allocation of the clone.

// ticktockbent

2026-04-06 15:30:18 +03:00

..

env.rs

quality: MSRV, tarpaulin config, proptest for parsers (#84)

2026-04-05 10:01:50 +03:00

mod.rs

quality: MSRV, tarpaulin config, proptest for parsers (#84)

2026-04-05 10:01:50 +03:00

protected.rs

fix: correct zeroize annotation placement and avoid secret cloning in protected.rs (#108)

2026-04-06 15:30:18 +03:00