mbedtls-integrationlisted

# mbedTLS Integration ## Overview Use this skill to integrate mbedTLS on embedded targets by proving entropy/RNG, time, certificate storage, transport I/O, and memory configuration before debugging application protocols. TLS failures often come from platform hooks rather than cryptography logic. ## When To Use Use this skill when: - The user wants TLS, HTTPS, MQTT over TLS, DTLS, X.509, crypto, or secure boot-related primitives using mbedTLS. - The issue involves handshake failure, certificate validation, entropy source, RNG, memory allocation, time validity, or socket callbacks. - The target is resource-constrained or has hardware crypto/TRNG. Do not use this skill for generic networking before TCP/IP works. Use `lwip-integration` first when connectivity is unproven. For lightweight ECC-only operations, use `micro-ecc-integration` or `tinycrypt-integration`. ## First Questions Ask for: - mbedTLS version, target MCU/RTOS, compiler, and network stack. - Use case: TLS client, TLS server, DTLS, crypto only, MQTT TLS, HTTPS, or certificate parsing. - `mbedtls_config.h`, enabled features, heap/static allocation policy, and hardware crypto use. - Entropy/RNG source and time source. - Certificate chain model, CA storage, SNI/hostname verification, and current error code. ## Integration Checklist 1. Prove entropy and RNG. TLS requires a real entropy source. Do not ship deterministic test entropy. 1. Configure time. Certificate validation needs valid time or an expli