1a8e1175bSopenharmony_ci## Known issues 2a8e1175bSopenharmony_ci 3a8e1175bSopenharmony_ciKnown issues in Mbed TLS are [tracked on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). 4a8e1175bSopenharmony_ci 5a8e1175bSopenharmony_ci## Reporting a bug 6a8e1175bSopenharmony_ci 7a8e1175bSopenharmony_ciIf you think you've found a bug in Mbed TLS, please follow these steps: 8a8e1175bSopenharmony_ci 9a8e1175bSopenharmony_ci1. Make sure you're using the latest version of a 10a8e1175bSopenharmony_ci [maintained branch](BRANCHES.md): `main`, `development`, 11a8e1175bSopenharmony_ci or a long-time support branch. 12a8e1175bSopenharmony_ci2. Check [GitHub](https://github.com/Mbed-TLS/mbedtls/issues) to see if 13a8e1175bSopenharmony_ci your issue has already been reported. If not, … 14a8e1175bSopenharmony_ci3. If the issue is a security risk (for example: buffer overflow, 15a8e1175bSopenharmony_ci data leak), please report it confidentially as described in 16a8e1175bSopenharmony_ci [`SECURITY.md`](SECURITY.md). If not, … 17a8e1175bSopenharmony_ci4. Please [create an issue on on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). 18a8e1175bSopenharmony_ci 19a8e1175bSopenharmony_ciPlease do not use GitHub for support questions. If you want to know 20a8e1175bSopenharmony_cihow to do something with Mbed TLS, please see [`SUPPORT.md`](SUPPORT.md) for available documentation and support channels. 21