Hi, mbedTLS version used is 2.14.0. mbedTLS worked fine on i386 based 64-bit linux machine out of the box. Also, we could port same on a 32-bit processor, little endian arm (EABI5 v1) based linux machine. With same configuration used in above machines, while trying to port mbedTLS on iRTOS, ARM9 …

Hi @kinani Thank you fro reporting this! From your description, it sounds to me that there is some sort of issue in 32-bit Big Endian architecture, probably in the rsa module. This obviously requires further investigation. We also used to get problem after client state:3, where alert with error…

Hi Ron, Appreciate your quick response! With some more debugging we figured some memory related problem in our OS Adaptation layer for the platform. Fixing that did complete the handshake without even setting hs_authmode to VERIFY_OPTIONAL. Thanks for the info. Because of some performance concern…

Hi Kartik, In order to have a secure transport, the messages are encrypted and authenticated ( Depending on the ciphersuite negotiated ) Since the negotiated ciphersuite is TLS-RSA-WITH-AES-128-CBC-SHA, have you considered using an AEAD based ciphersuite? Does your platform have HW acceleration? …

Ron, We forced this ciphersuite thinking it will take lesser processing (due to machine’s performance constraints). So what we want is a ciphersuite which allows us to have out-of-order transport packets and still be low on computations. Also, our platform doesn’t support hardware accelerations.…

Hi Kartik, AEAD based ciphersuites are better in terms of security. Have you tried other ciphersuites? Have you tried ECP based ciphersuites instead of RSA ones, as this reduces the key size with similar security strength? Also, our platform doesn’t support hardware accelerations. Can we configu…

Hi Ron, Thanks for the quick response. We did try TLS_RSA_WITH_AES_128_GCM_SHA256 but to no avail. We don’t have much option but to use TLS-RSA-WITH-AES-128-CBC-SHA ciphersuite. For experimental purpose, can you please guide to disable the MAC verification through config or code.?

Hi Kartik, Unfortunately, that is not really possible… Part of the TLS ciphersuites is having the packets authinticated in some way, either by MAC or AEAD. Even if we disbale on your peer the mac processing, the remote peer will still verify, and have MAC failed, sending you a fatal alert. I sho…

Hi Ron, Thanks for the insight. We are negotiating a TLS handshake. The handshake is successful but after some packets are successfully decrypted, we get -29056 (0x7180) i.e. Verification of the message MAC failed. Let the remote peer verify the MAC, we just want to disable the MAC check at our …

Hi Martik, For the benefit of the community, it is better to start a new thread if there is a new issue. Please don’t change subject, as it might confuse other users. As you can see n ssl_tls.c in the function ssl_decrypt_buf , you will see the MAC calculated for your ciphersuite, however, if you w…

Decryption fails with 0x7180 (Verification of the message MAC failed)

Mbed TLS Platform specific questions

kinani (Kartik Inani) December 11, 2018, 3:14pm 11

Hi Ron,

Thanks for your timely help.

We were getting in-order packets from transport but we were splitting them in two threads and then giving to mbedTLS, may be that caused the issue. Sending them in single thread context works fine.

Thanks,
Kartik

Topic		Replies	Views
MBEDTLS_ERR_SSL_INVALID_MAC -0x7180 and MBEDTLS_ERR_SSL_INVALID_RECORD -0x7200 Generic mbed_tls	8	6448	July 2, 2021
TLS handshake mac problem Generic	5	1251	October 21, 2018
Verification of the message MAC failed Crypto and SSL questions	3	4309	February 21, 2019
-0x7180 - SSL - Verification of the message MAC failed Bug Reports / Issues mbed_tls	0	1514	November 28, 2020
mbedTLS SSL handshake issue 2 Generic mbed_client , mbed_device_server , mbed_tls	25	30420	November 25, 2019

Decryption fails with 0x7180 (Verification of the message MAC failed)

Related topics