Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to the development branch of Mbed TLS #6992

Closed

Conversation

daverodgman
Copy link
Contributor

As per #5637, return to fuzzing the development branch of Mbed TLS.

Signed-off-by: Dave Rodgman dave.rodgman@arm.com

@daverodgman daverodgman force-pushed the mbedtls_development_switch branch from 000f508 to b19ccf9 Compare January 17, 2022 17:08
@daverodgman
Copy link
Contributor Author

Update as most of the projects have been updated independently of this PR

@DavidKorczynski
Copy link
Collaborator

@guidovranken - could you verify this one?

@guidovranken
Copy link
Contributor

guidovranken commented Jan 18, 2022

Thanks @daverodgman

You can also remove these 2 lines since they are not supported by the new version of mbed TLS:

scripts/config.pl set MBEDTLS_MD2_C
scripts/config.pl set MBEDTLS_MD4_C

I'm getting these errors when I compile the existing Cryptofuzz module with the new mbed TLS: https://gist.github.com/guidovranken/2990a57942a53043a3032b0681214a5a

Would you mind giving some pointers how to work around these?

As per google#5637, return to fuzzing the development branch of Mbed TLS.

Signed-off-by: Dave Rodgman <dave.rodgman@arm.com>
@daverodgman
Copy link
Contributor Author

Hi, the errors relate to these changes:

https://github.com/ARMmbed/mbedtls/blob/development/docs/3.0-migration-guide.md#most-structure-fields-are-now-private

We do have a planned task to add accessors for these fields:

Mbed-TLS/mbedtls#4838
Mbed-TLS/mbedtls#5017

In the short term, probably using the MBEDTLS_PRIVATE macro is the way to go.

@guidovranken
Copy link
Contributor

I've made the requisite changes to both the fuzzer and to #7062 so this PR can be closed.

@DavidKorczynski
Copy link
Collaborator

Thanks @guidovranken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants