change unified the key-management aspect within MinIO.

The unified KMS-based approach has several advantages:

- Key management is now centralized. There is one way to change or rotate encryption keys.
   There used to be two different mechanisms - one for regular S3 objects and one for IAM data.
- Reduced server startup time. For IAM encryption with the root credentials, MinIO had

  }

  @GwtIncompatible // different overflow behavior; could probably be made to work by using ~~
  public void testConcat_overflow_negative() {
    int dim1 = 1 << 16;
    int dim2 = 1 << 15;
    assertThat(dim1 * dim2).isLessThan(0);
    testConcatOverflow(dim1, dim2);
  }

  @GwtIncompatible // different overflow behavior; could probably be made to work by using ~~

         * original, identical JDK TypeVariable. By doing so, we sidestep the problem entirely.
         *
         * 2b. If the resolved types are different from the original types, things are trickier. The
         * only way to get a TypeVariable instance for the resolved types is to create our own. The

               Licensed Rights under the terms and conditions of this
               Public License.

            b. No downstream restrictions. You may not offer or impose
               any additional or different terms or conditions on, or
               apply any Effective Technological Measures to, the
               Licensed Material if doing so restricts exercise of the
               Licensed Rights by any recipient of the Licensed

        buffer.add(e);
        added++;
      }
    }
    return added;
  }

  /**
   * Drains the queue as {@linkplain #drain(BlockingQueue, Collection, int, Duration)}, but with a
   * different behavior in case it is interrupted while waiting. In that case, the operation will
   * continue as usual, and in the end the thread's interruption status will be set (no {@code
   * InterruptedException} is thrown).
   *

        assertThrows(ArrayIndexOutOfBoundsException.class, () -> {
            response.readDataWireFormat(buffer, 0, buffer.length);
        });
    }

    @DisplayName("Test readDataWireFormat with different buffer offsets")
    @ParameterizedTest
    @ValueSource(ints = { 0, 10, 50, 100 })
    void testReadDataWireFormatWithDifferentOffsets(int offset) throws Exception {
        // Create a buffer large enough for offset + data

            // Verify reserved field is zeros (4 bytes)
            assertEquals(0, SMBUtil.readInt4(buffer, 20));
        }

        @Test
        @DisplayName("Should encode at different buffer positions")
        void testEncodingAtDifferentPositions() {
            long offset = 1000L;
            long length = 2000L;
            int flags = Smb2Lock.SMB2_LOCKFLAG_UNLOCK;

import jcifs.util.Crypto;

/**
 * SMB2/SMB3 message signing digest implementation.
 *
 * This class handles cryptographic signing of SMB2/SMB3 messages to ensure
 * message integrity and authenticity. It supports different signing algorithms
 * used in various SMB2/SMB3 dialect versions.
 *
 * @author mbechler
 */
public class Smb2SigningDigest implements SMBSigningDigest, AutoCloseable {

            };
        });
    }

    @Test
    @DisplayName("Complex scenario with multiple filter conditions")
    void complexFilterScenario() throws Exception {
        // Setup: three entries with different filter results
        FileEntry entry1 = mock(FileEntry.class);
        FileEntry entry2 = mock(FileEntry.class);
        FileEntry entry3 = mock(FileEntry.class);

        assertNotNull(newHash);
        assertEquals(64, newHash.length); // SHA-512 produces 64 bytes
        assertNotEquals(oldHash, newHash); // Should be different instance
    }

    /**
     * Test pre-auth integrity with non-SMB3.1.1 should throw exception
     */
    @Test
    @DisplayName("Pre-auth integrity should fail with non-SMB3.1.1")