Re: [TLS] rfc7366: is encrypt-then-mac implemented?

[Nikos Mavrogiannopoulos <[e-mail]>]

On Wed, 2014-10-29 at 15:30 +0000, Peter Gutmann wrote:
> Manuel Pégourié-Gonnard <[e-mail]> writes:
> 
> >The *only* difference is (something that doesn't involve the definition of
> >length), so the definition of the length is unchanged, therefore it's the one
> >from RFC 5246.
> 
> No it isn't.  RFC 7366 moves the MAC outside the GenericXXXCipher fragment, so
> it's no longer included.

I don't think it matter that the MAC is outside the GenericXXXCipher
fragment. TLSCiphertext is defined in RFC7366 as follows:

   struct {
          ContentType type;
          ProtocolVersion version;
          uint16 length;
          GenericBlockCipher fragment;
          opaque MAC;
          } TLSCiphertext;

(for block ciphers at least). That TLSCiphertext.length send on the wire
contains both fragment and MAC length, doesn't it?

regards,
Nikos