md4.update(Strings.getUNIBytes(password));
        return md4.digest();
    }

    /**
     * Generates the NT password hash for the given password.
     * This version accepts char[] for better security.
     *
     * @param password the password to hash as char array
     * @return nt password hash
     */
    public static byte[] getNTHash(final char[] password) {

        when(mockDelegate.next()).thenReturn(mockFileEntry1, mockFileEntry2, mockFileEntry3);

        // Create a mock filter that accepts file1 and file3 but not file2
        when(mockFilter.accept(mockResource1)).thenReturn(true);
        when(mockFilter.accept(mockResource2)).thenReturn(false);
        when(mockFilter.accept(mockResource3)).thenReturn(true);

    }

    @Test
    @DisplayName("Parse accepts non-zero outer tag numbers (current implementation behavior)")
    void testParseAcceptsNonZeroOuterTag() throws Exception {
        // Note: The current implementation does not validate the outer APPLICATION tag number
        // This test documents the actual behavior - any tag number is accepted
        byte[] token =

   *
   * <p>This deliberately avoids all nameservice lookups (e.g. no DNS).
   *
   * <p>This method accepts non-ASCII digits, for example {@code "１９２.１６８.０.１"} (those are fullwidth
   * characters). That is consistent with {@link InetAddress}, but not with various RFCs. If you
   * want to accept ASCII digits only, you can use something like {@code
   * CharMatcher.ascii().matchesAllOf(ipString)}.
   *

   * an exception if parsing fails. Additionally, this method only accepts ASCII digits, and returns
   * {@code null} if non-ASCII digits are present in the string.
   *
   * <p>Note that strings prefixed with ASCII {@code '+'} are rejected, even though {@link
   * Integer#parseInt(String)} accepts them.
   *
   * @param string the string representation of a long value

   * throwing an exception if parsing fails. Additionally, this method only accepts ASCII digits,
   * and returns {@code null} if non-ASCII digits are present in the string.
   *
   * <p>Note that strings prefixed with ASCII {@code '+'} are rejected, even though {@link
   * Integer#parseInt(String)} accepts them.
   *
   * @param string the string representation of an integer value

  }

  /**
   * This accepts a [BufferedSource] instead of using [Socket.source], just in case we've already
   * received data from the peer. This accepts a [BufferedSink] for symmetry with the source.
   */
  fun initReaderAndWriter(
    name: String,
    socket: BufferedSocket,
    client: Boolean,
  ) {
    val extensions = this.extensions!!

   *
   * <p>This deliberately avoids all nameservice lookups (e.g. no DNS).
   *
   * <p>This method accepts non-ASCII digits, for example {@code "１９２.１６８.０.１"} (those are fullwidth
   * characters). That is consistent with {@link InetAddress}, but not with various RFCs. If you
   * want to accept ASCII digits only, you can use something like {@code
   * CharMatcher.ascii().matchesAllOf(ipString)}.
   *

  /**
   * A {@link Correspondence} which accepts finite values within {@link #ALLOWED_ERROR} of each
   * other.
   */
  private static final Correspondence<Number, Number> FINITE_QUANTILE_CORRESPONDENCE =
      Correspondence.tolerance(ALLOWED_ERROR);

  /**
   * A {@link Correspondence} which accepts either finite values within {@link #ALLOWED_ERROR} of

  /**
   * A {@link Correspondence} which accepts finite values within {@link #ALLOWED_ERROR} of each
   * other.
   */
  private static final Correspondence<Number, Number> FINITE_QUANTILE_CORRESPONDENCE =
      Correspondence.tolerance(ALLOWED_ERROR);

  /**
   * A {@link Correspondence} which accepts either finite values within {@link #ALLOWED_ERROR} of