Which RFC explains how the mac-then-encrypt needs to be implemented

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Which RFC explains how the mac-then-encrypt needs to be implemented

Phani 2004
Hi Team,

I am trying to implement mac-then-encrypt for aes_cbc_hmac_sha1 combined cipher. From the code i could understand that the first 16 bytes were being used as explicit IV while decrypting and the hmac is done for 13 bye AAD and 16 byte Fin record in finish message.

Which RFC/section explains this in detail?

Regards
Phani

Reply | Threaded
Open this post in threaded view
|

Re: Which RFC explains how the mac-then-encrypt needs to be implemented

OpenSSL - User mailing list
On 2020-03-03 07:46, Phani 2004 wrote:

> Hi Team,
>
> I am trying to implement mac-then-encrypt for aes_cbc_hmac_sha1
> combined cipher. From the code i could understand that the first 16
> bytes were being used as explicit IV while decrypting and the hmac is
> done for 13 bye AAD and 16 byte Fin record in finish message.
>
> Which RFC/section explains this in detail?
>
>
For TLS 1.2, this is RFC5246 Section 6.2.3.2

Note that each version of TLS makes arbitrary changes to the record
encryption.

Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded