The wireguard_write encryption result is different from the official one about boringtun HOT 5 OPEN

This is my code about the handshake：

from boringtun.

i follow this step . https://www.ntkernel.com/boringtun-based-wireguard-client-for-windows/

from boringtun.

It could be related to the size of the packet not being 100% Wireguard spec:

encrypted_static: &src[40..88], // SIZE u8;32, 88-40 = 48 bytes, seems too big for the spec (32)
encrypted_timestamp: &src[88..116], // SIZE u8;12, 116-88 = 28 bytes, seems too big for the spec (12)

from boringtun.

It could be related to the size of the packet not being 100% Wireguard spec:

boringtun/boringtun/src/noise/mod.rs

Line 141 in 18eaf59

encrypted_static: &src[40..88],

encrypted_static: &src[40..88], // SIZE u8;32, 88-40 = 48 bytes, seems too big for the spec (32) encrypted_timestamp: &src[88..116], // SIZE u8;12, 116-88 = 28 bytes, seems too big for the spec (12)

Is there something wrong with my handshake data? How do I deal with this? Thank you for your reply。

from boringtun.

I am afraid you need to do the analysis yourself. It may be related to handshake field length, but this is for you to find out...

from boringtun.