// Add some dummy security data at offset 64 from start
        buffer[64] = (byte) 0x4E; // NTLMSSP signature start
        buffer[65] = (byte) 0x54;
        buffer[66] = (byte) 0x4C;
        buffer[67] = (byte) 0x4D;
        buffer[68] = (byte) 0x53;
        buffer[69] = (byte) 0x53;
        buffer[70] = (byte) 0x50;
        buffer[71] = (byte) 0x00;

        return buffer;
    }

        println(
                "transferCorrupted",
                event.getException().getClass() + ": " + event.getException().getMessage());
    }

    protected long toKB(long bytes) {
        return (bytes + 1023) / 1024;
    }

    private void println(String event, String message) {
        print(event, message);
        out.println();
    }

            final byte[] mechanismListMIC) {
        setMechanisms(mechanisms);
        setContextFlags(contextFlags);
        setMechanismToken(mechanismToken);
        setMechanismListMIC(mechanismListMIC);
    }

    /**
     * Constructs a NegTokenInit by parsing the provided token bytes
     * @param token the SPNEGO token bytes to parse

        rpc.unicode_string dummyRus = new rpc.unicode_string();
        dummyRus.buffer = new short[] { 'T', 'e', 's', 't', 'i', 'n', 'g' };
        dummyRus.length = 14; // 7 characters * 2 bytes/char
        dummyRus.maximum_length = 14;
        UnicodeString manualUnicodeString = new UnicodeString(dummyRus, false);

以下是一個更完整的範例。

使用一個依賴來檢查使用者名稱與密碼是否正確。

為此，使用 Python 標準模組 [`secrets`](https://docs.python.org/3/library/secrets.html) 來比對使用者名稱與密碼。

`secrets.compare_digest()` 需要接收 `bytes`，或是只包含 ASCII 字元（英文字符）的 `str`。這表示它無法處理像 `á` 這樣的字元，例如 `Sebastián`。

為了處理這點，我們會先將 `username` 與 `password` 以 UTF-8 編碼成 `bytes`。

接著我們可以使用 `secrets.compare_digest()` 來確認 `credentials.username` 等於 `"stanleyjobson"`，而 `credentials.password` 等於 `"swordfish"`。

    @Override
    public synchronized void write(final byte[] b, int off, final int len) throws IOException {
        if (len > 0xFFFF) {
            throw new IOException("write too large: " + len);
        }
        if (off < 4) {
            throw new IOException("NetBIOS socket output buffer requires 4 bytes available before off");
        }

        off -= 4;

        b[off + 0] = (byte) SessionServicePacket.SESSION_MESSAGE;

            // Default constructor
        }

        /** The revision level of the SID structure */
        public byte revision;
        /** The number of sub-authorities in the SID */
        public byte sub_authority_count;
        /** The identifier authority value (6 bytes) */
        public byte[] identifier_authority;
        /** The array of sub-authority values */
        public int[] sub_authority;

Nesse exemplo, nós não declaramos nenhum modelo do Pydantic. Na verdade, o corpo da requisição não está nem mesmo <dfn title="convertido de algum formato simples, como bytes, em objetos Python">analisado</dfn> como JSON, ele é lido diretamente como `bytes`, e a função `magic_data_reader()` seria a responsável por analisá-lo de alguma forma.

De toda forma, nós podemos declarar o esquema esperado para o corpo da requisição.

          bf.put("element" + i);
        }

        // Calculate expected size based on bitSize()
        // Header: 1 byte (strategy) + 1 byte (hash functions) + 4 bytes (array length) = 6 bytes
        // Data: bitSize / 8 bytes
        long predictedSize = bf.bitSize() / 8 + 6;
        assertThat(bf.serializedSize()).isEqualTo(predictedSize);

        // Serialize and measure actual size

   */
  var peerSettings = DEFAULT_SETTINGS

  /** The bytes consumed and acknowledged by the application. */
  val readBytes: WindowCounter = WindowCounter(streamId = 0)

  /** The total number of bytes produced by the application. */
  var writeBytesTotal = 0L
    private set

  /** The total number of bytes permitted to be produced according to `WINDOW_UPDATE` frames. */