MbedTlsError(-30592) after upgrading to latest commit

[yanshay]

I have a program that works using esp-mbedtls (async)
I upgraded to the latest commit, it required adding SHA parameter to the Session::new and did the same as the example.
I started receiving MbedTlsError(-30592) which based on error codes I found mean:
0x7780 SSL - A fatal alert message was received from our peer.

Note that I'm using TLS1.2 (that's why I'm using esp-mbedtls).

What's causing this?
Seems like the remote system I'm connecting to doesn't like this SHA.

Is there a way to use the new code with previous behavior? This is really critical to me.

[AnthonyGrondin]

Are you using esp-mbedtls as a client or as a server?

The latest changes with SHA should not affect operations, because it uses the Hardware SHA acceleration instead of the Software provided solution from esp-mbedtls.

[yanshay]

I'm on esp32s3 so I believe it isn't RISCV but rather Xtensa, right?
Does that mean can't have required logs?

[AnthonyGrondin]

You can, but you'd need to patch esp-mbedtls due to the following line:

esp-mbedtls/esp-mbedtls/src/lib.rs

Lines 144 to 150 in d5e29f8

	#[allow(unused)]
	pub fn set_debug(level: u32) {
	#[cfg(not(target_arch = "xtensa"))]
	unsafe {
	mbedtls_debug_set_threshold(level as c_int);
	}
	}

This is from back when Xtensa didn't support C variadics.

[yanshay]

I opened issue #60 regarding this

[yanshay]

You can, but you'd need to patch esp-mbedtls due to the following line:

esp-mbedtls/esp-mbedtls/src/lib.rs

Lines 144 to 150 in d5e29f8

	#[allow(unused)]
	pub fn set_debug(level: u32) {
	#[cfg(not(target_arch = "xtensa"))]
	unsafe {
	mbedtls_debug_set_threshold(level as c_int);
	}
	}

This is from back when Xtensa didn't support C variadics.

do you mean just remove the #[cfg(not(target_arch = "xtensa"))] ? Now Xtensa support that?

And what integer should I set the level to?

[yanshay]

@AnthonyGrondin - I uploaded logs to the issue I opened, I wasn't able to figure out by myself anything smart from those logs except a different in size towards the end of the session.
Your assistance in resolving this will be appreciated.
Currently esp-mbedtls doesn't with esp-hal 0.22 and I wanted to try to fix it but no point doing this on an not latest version of esp-mbedtls.

[yanshay]

For further logs, you can try and set esp_mbedtls::set_debug() if you are on RISCV. I believe you also need to build esp-wifi with the sys-logs feature enabled

@AnthonyGrondin I had some mixups in folders locations and seems like it didn't really take the set_debug properly.
Once I fixed that I received a linker error:
undefined reference to mbedtls_debug_set_threshold'`

Do I need to compile myself somehow the mbedtls library to see logs? Is there binary available for debugging?

Any guidance/assistance would be appreciated.

[AnthonyGrondin]

Sorry about the delays,

I wrote a guide on how to compile and edit mbedtls config for each chip here: #64 (comment)

To fix the "undefined reference to mbedtls_debug_set_threshold" issue, if you're on a commit previous to 1431835 you need to rebuild mbedtls with the MBEDTLS_DEBUG_C flag enabled. This is done automatically past this commit

[yanshay]

I managed to get the logs for the failed session and attach them here, I don't understand much in this domain, maybe you can take a look and see if you can figure something out? As wrote on the other discussion I can't compare it with the working session.
tls-session-bad.txt

[AnthonyGrondin]

Closing as fixed in d6e5041

See #60 for more context