// Assert
        assertEquals(DialectVersion.SMB202, dialect);
        verify(negotiationResponse).getSelectedDialect();
    }

    @Test
    @DisplayName("Test getSelectedDialect returns SMB3")
    void testGetSelectedDialectSMB3() {
        // Arrange
        when(negotiationResponse.getSelectedDialect()).thenReturn(DialectVersion.SMB311);

        // Act

# Persistent Handles Feature - Detailed Design Document

## 1. Overview

Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST

            assertThrows(SmbUnsupportedOperationException.class, () -> transport.createEncryptionContext(new byte[] { 1 }, null));
        }

        @Test
        @DisplayName("createEncryptionContext rejects pre-SMB3 dialect")
        void createEncryptionContext_rejects_oldDialect() throws Exception {
            setField(transport, "smb2", true);
            Smb2NegotiateResponse nego = new Smb2NegotiateResponse(cfg);

    private static final Logger log = LoggerFactory.getLogger(ServerResponseValidator.class);

    // Protocol limits
    private static final int MAX_SMB_MESSAGE_SIZE = 16 * 1024 * 1024; // 16MB max for SMB3
    private static final int MAX_SMB1_MESSAGE_SIZE = 65535; // 64KB for SMB1
    private static final int MIN_SMB_HEADER_SIZE = 32;
    private static final int MAX_PATH_COMPONENT_SIZE = 255;

import org.junit.jupiter.api.Test;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;

/**
 * Test class for Smb3KeyDerivation.
 * Tests the SMB3 SP800-108 Counter Mode Key Derivation implementation.
 */
@DisplayName("Smb3KeyDerivation Tests")
class Smb3KeyDerivationTest {

    private byte[] sessionKey;
    private byte[] preauthIntegrity;

    @BeforeEach

import jcifs.internal.smb2.ioctl.QueryNetworkInterfaceInfoResponse;
import jcifs.internal.smb2.ioctl.Smb2IoctlRequest;
import jcifs.internal.smb2.session.Smb2SessionSetupRequest;

/**
 * Manages SMB3 Multi-Channel connections
 */
public class ChannelManager {

    private static final Logger log = LoggerFactory.getLogger(ChannelManager.class);

    private final CIFSContext context;

        }
    }
    
    public void validateRemoteAccess(long remoteAddress, int length, int remoteKey) {
        // Validate that remote memory access is authorized
        // This would integrate with SMB3 encryption/signing
        if (!isAuthorizedAccess(remoteAddress, length, remoteKey)) {
            throw new SecurityException("Unauthorized RDMA remote access");
        }
    }
    

# Multi-Channel Feature - Detailed Design Document

## 1. Overview

SMB3 Multi-Channel enables the use of multiple network connections between client and server, providing increased throughput, network fault tolerance, and automatic failover capabilities. This feature aggregates bandwidth across multiple NICs and provides seamless failover when network paths fail.

## 2. Protocol Specification Reference

            assertNotEquals(hash[0], hash2[0]);
        }
    }

    /**
     * Test pre-auth integrity with SMB3.1.1
     */
    @Test
    @DisplayName("Pre-auth integrity should work with SMB3.1.1")
    void testPreauthWithSmb311() throws Exception {
        // Setup SMB3.1.1
        when(negotiateResponse.getSelectedDialect()).thenReturn(DialectVersion.SMB311);

    }

    @Test
    @DisplayName("Test log encryption")
    void testLogEncryption() {
        logger.logEncryption(true, "AES-128-GCM", "SMB3.1.1");

        Map<EventType, Long> stats = logger.getStatistics();
        assertEquals(Long.valueOf(1), stats.get(EventType.ENCRYPTION_ENABLED), "Should have 1 encryption event");
    }

    @Test