[BEEPwg] Cipher block boundaries and the TCP mapping
ghudson at MIT.EDU
Sat Aug 7 01:38:32 PDT 2004
On Fri, 2004-08-06 at 01:29, james woodyatt wrote:
> Is it my imagination, or does the TCP mapping for the BEEP protocol not
> specify any way for frames to be spaced properly so that they always
> begin (or end) on a cipher block boundary?
Why do you want this? Don't TLS and SASL mechanisms have their own
padding facilities for encoding short blocks of data?
More information about the BEEPwg