larabr 7a257d563d Detect invalid PKESK public point encoding on decryption
We got a report of a message including a PKESK packet where
the ECDH x25519Legacy point was missing the leading byte (0x40).
While decryption naturally would naturally fail afterwards, this
change ensures we fail at a higher level, and do not blindly pass
down invalid data to the low-level crypto functions.
2024-05-16 16:12:35 +02:00
..
2024-02-27 14:43:24 +01:00
2023-10-25 12:53:12 +02:00
2024-02-27 14:43:24 +01:00
2023-10-25 12:53:11 +02:00
2023-10-25 12:53:11 +02:00
2023-10-25 12:53:11 +02:00