rustfmt

Author: ounsworth

crypto/base64/src/lib.rs

@@ -102,7 +102,7 @@ pub enum Base64Error {
     /// The [Base64Decoder::do_update] method must not be called on a block that contains padding.
     /// If this error is returned, then the provided input has not been processed and the caller must instead
     /// pass the same input to [Base64Decoder::do_final]. Note that do_final() is tolerant of incomplete padding blocks,
-    /// so even if an additional padding character is contained in the next chunk of input, do_final() 
+    /// so even if an additional padding character is contained in the next chunk of input, do_final()
     /// will still produce the correct output -- ie any additional chunks held by the caller can be discarded.
     PaddingEnconteredDuringDoUpdate,
 

crypto/core/src/traits.rs

@@ -267,7 +267,6 @@ pub trait StreamCipher<const KEY_LEN: usize, const INIT_DATA_LEN: usize>:
     ) -> Result<usize, SymmetricCipherError>;
 }
 
-
 /// A hash function is a cryptographic primitive that takes an input of any length and produces a fixed-size output.
 /// Formally: `H: {0,1}^* -> {0,1}^n`.
 /// A cryptographic hash function will typically satisfy several security properties, including:

crypto/factory/src/lib.rs

@@ -24,7 +24,7 @@
 //! get the either the default algorithm or the default algorithm at the 128-bit or 256-bit security level.
 //! It also exposes [AlgorithmFactory::new] which can be used to create an instance of the algorithm
 //! by string name according to the string constants associated with the respective factory type.
-//! 
+//!
 //! This crate compiles with STD; ie it is explicitly not tagged as `no_std` and it makes use of `Vec` and other
 //! dynamically-sized nice things.
 

crypto/hkdf/tests/hkdf_tests.rs

@@ -732,8 +732,7 @@ mod hkdf_tests {
         use bouncycastle_hkdf::{SUSPENDED_HKDF_SHA256_STATE_LEN, SUSPENDED_HKDF_SHA512_STATE_LEN};
 
         // HKDF is keyed by its salt: the salt is NOT serialized and is re-supplied on resume.
-        let salt =
-            KeyMaterial128::from_bytes_as_type(&DUMMY_SEED[..16], KeyType::MACKey).unwrap();
+        let salt = KeyMaterial128::from_bytes_as_type(&DUMMY_SEED[..16], KeyType::MACKey).unwrap();
         let ikm = &DUMMY_SEED[16..64];
         let (part1, part2) = ikm.split_at(20);
 

crypto/hmac/src/lib.rs

@@ -633,7 +633,7 @@ impl<
 macro_rules! impl_hmac_keygen {
     ($hash:ty, $block_len:literal, $n:literal, $drbg:ty) => {
         impl HMAC<$hash, $block_len> {
-        /// Generate a key of the appropriate length for the given HMAC
+            /// Generate a key of the appropriate length for the given HMAC
             pub fn keygen() -> Result<KeyMaterial<$n>, RNGError> {
                 let mut key = KeyMaterial::<$n>::new();
                 let mut os_rng = <$drbg>::new_from_os();

crypto/hmac/tests/hmac_tests.rs

@@ -609,8 +609,7 @@ mod hmac_tests {
         use bouncycastle_core::traits::SuspendableKeyed;
         use bouncycastle_core_test_framework::suspendable_state::TestFrameworkSuspendableKeyedState;
 
-        let key =
-            KeyMaterial256::from_bytes_as_type(&DUMMY_SEED[..32], KeyType::MACKey).unwrap();
+        let key = KeyMaterial256::from_bytes_as_type(&DUMMY_SEED[..32], KeyType::MACKey).unwrap();
         let msg = b"Colorless green ideas sleep furiously";
 
         // A helper that exercises the full round-trip for one HMAC variant. HMAC is keyed, so the
@@ -662,8 +661,7 @@ mod hmac_tests {
 
         // test suspend / resume with a key larger than block size
         let long_key =
-            KeyMaterial::<200>::from_bytes_as_type(&DUMMY_SEED[..200], KeyType::MACKey)
-                .unwrap();
+            KeyMaterial::<200>::from_bytes_as_type(&DUMMY_SEED[..200], KeyType::MACKey).unwrap();
         round_trip(HMAC_SHA256::new(&long_key).unwrap(), &long_key, msg);
     }
 

crypto/utils/src/lib.rs

@@ -2,7 +2,7 @@
 //!
 //! The functions contained here are not really intended to be used by end users, but you
 //! are welcome to do so if you wish.
-//! 
+//!
 //! That said, beware that this crate is not necessarily documented to the same standard as other crates.
 //! Since many of the contained helpers are security-critical (such as the constant time module),
 //! we will prioritize fixing security bugs over maintaining a stable API for this crate.