# SMB3 Lease Feature - Detailed Design Document

## 1. Overview

SMB3 leases provide a client caching mechanism that replaces the traditional oplock mechanism. Leases enable better performance through client-side caching while maintaining cache coherency across multiple clients.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13**: SMB2 CREATE Request with Lease Context
- **MS-SMB2 Section 2.2.14**: SMB2 CREATE Response with Lease State

            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);

    /**
     * AES-128-CCM cipher identifier for SMB3 encryption
     */
    public static final int CIPHER_AES_128_CCM = EncryptionNegotiateContext.CIPHER_AES128_CCM;
    /**
     * AES-128-GCM cipher identifier for SMB3.1.1 encryption
     */
    public static final int CIPHER_AES_128_GCM = EncryptionNegotiateContext.CIPHER_AES128_GCM;
    /**
     * AES-256-CCM cipher identifier for SMB3 encryption (future support)
     */

# SMB3 Advanced Features Implementation Plan

## Overview
This document outlines the implementation plan for advanced SMB3 features that are currently not implemented in JCIFS. These features are essential for enterprise-grade SMB3 support, providing enhanced performance, reliability, and scalability.

## Implementation Phases

### Phase 1: SMB3 Lease Implementation (Foundation)
**Priority: HIGH** | **Estimated Effort: 3-4 weeks**

import jcifs.internal.util.SMBUtil;
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
 */

        smb2.mid = 100;

        ServerMessageBlock smb3 = new TestServerMessageBlock();
        smb3.mid = 200;

        assertEquals(smb1, smb2);
        assertNotEquals(smb1, smb3);
        assertEquals(smb1.hashCode(), smb2.hashCode());
        assertNotEquals(smb1.hashCode(), smb3.hashCode());
        assertNotEquals(smb1, new Object());
    }

    @Test

     *
     * @return preferred encryption cipher list in order of preference for SMB3 encryption
     * @since 2.2
     */
    String getPreferredCiphers();

    /**
     * Property {@code jcifs.smb.client.aes256Enabled} (boolean, default true)
     *
     * @return whether AES-256 encryption ciphers are enabled for SMB3.x
     * @since 2.2
     */
    boolean isAES256Enabled();

    /**

    }

    @Test
    @DisplayName("Test decode with real-world SMB3 values")
    void testDecodeWithRealWorldValues() throws SMBProtocolDecodingException {
        // Prepare test data with realistic SMB3 values
        byte[] buffer = new byte[50];
        int bufferIndex = 0;

        // SMB3 capabilities

    protected boolean signingEnforced = false;
    /** Whether to enforce signing for IPC connections */
    protected boolean ipcSigningEnforced = true;
    /** Whether SMB3 encryption is enabled */
    protected boolean encryptionEnabled = false;
    /** Whether SMB3 compression is enabled */
    protected boolean compressionEnabled = false;
    /** Preferred encryption ciphers in order of preference */

        this.channelExecutor = Executors.newCachedThreadPool(r -> {
            Thread t = new Thread(r, "SMB3-MultiChannel-Worker");
            t.setDaemon(true);
            return t;
        });

        this.healthCheckExecutor = Executors.newScheduledThreadPool(2, r -> {
            Thread t = new Thread(r, "SMB3-MultiChannel-HealthCheck");
            t.setDaemon(true);
            return t;
        });