* `MODERN_TLS` is a secure configuration that connects to modern HTTPS servers.
 * `COMPATIBLE_TLS` is a secure configuration that connects to secure–but not current–HTTPS servers.
 * `CLEARTEXT` is an insecure configuration that is used for `http://` URLs.

These loosely follow the model set in [Google Cloud Policies](https://cloud.google.com/load-balancing/docs/ssl-policies-concepts). We [track changes](../security/tls_configuration_history.md) to this policy.

        verify(mockFilter).accept(mockResource1);
        verify(mockFilter).accept(mockResource2);
        verify(mockFilter).accept(mockResource3);
    }

    /**
     * Test that adapt method is actually used by the iterator.
     */
    @Test
    void testAdaptMethodIsUsed() {
        // Given
        when(mockDelegate.hasNext()).thenReturn(true, false);
        when(mockDelegate.next()).thenReturn(mockFileEntry1);

        byte[] r15 = NtlmUtil.getPreNTLMResponse(cifsContext, password15, challenge);

        // Assert: equal because only first 14 OEM bytes are used
        assertArrayEquals(r14, r15, "Only first 14 OEM bytes affect Pre-NTLM response");
        assertEquals(24, r14.length);

        // Verify collaborator interactions

            return null;
        }
        byte[] encrypted = Base64.getDecoder().decode(encryptedString);
        return decryptCredentials(encrypted);
    }

    /**
     * Get the salt used for key derivation
     *
     * @return salt bytes
     */
    public byte[] getSalt() {
        return salt != null ? salt.clone() : null;
    }

    /**

By default, those files are served from a <abbr title="Content Delivery Network: A service, normally composed of several servers, that provides static files, like JavaScript and CSS. It's commonly used to serve those files from the server closer to the client, improving performance.">CDN</abbr>.

But it's possible to customize it, you can set a specific CDN, or serve the files yourself.

// Copyright 2024 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

// This program can be used as go_ios_$GOARCH_exec by the Go tool. It executes
// binaries on the iOS Simulator using the XCode toolchain.
package main

import (
	"fmt"
	"go/build"
	"log"
	"os"
	"os/exec"
	"path/filepath"
	"runtime"
	"strings"
	"syscall"
)

      /*
       * If entries is full, then this implementation may end up using the entries array
       * directly and writing over the entry objects with non-terminal entries, but this is
       * safe; if this Builder is used further, it will grow the entries array (so it can't
       * affect the original array), and future build() calls will always copy any entry
       * objects that cannot be safely reused.
       */

 * determines which users have the necessary permissions to access objects
 * based on these entries.
 * <p>
 * To fully understand the information exposed by this class a description
 * of the access check algorithm used by Windows is required. The following
 * is a basic description of the algorithm. For a more complete description
 * we recommend reading the section on Access Control in Keith Brown's

@DisplayName("Smb2SessionSetupResponse Tests")
@MockitoSettings(strictness = Strictness.LENIENT)
class Smb2SessionSetupResponseTest extends BaseTest {

    private Smb2SessionSetupResponse newResponse() {
        // Configuration is not used during decode when no signing digest is set
        Configuration cfg = mock(Configuration.class);
        return new Smb2SessionSetupResponse(cfg);
    }

    /**

/**
 * The {@code MemoryDataHelper} class provides a helper for managing crawler data in memory.
 * It stores URL queues, access results, and URL patterns for inclusion and exclusion.
 * This class is designed to be used in a single-threaded environment or with external synchronization.
 *
 * <p>It uses {@code Map} and {@code Queue} data structures to hold the data. The class provides