| Gilles Peskine | 74a7f93 | 2021-03-16 12:05:44 +0100 | [diff] [blame] | 1 | ## Known issues |
| 2 | |
| Dave Rodgman | 017a199 | 2022-03-31 14:07:01 +0100 | [diff] [blame] | 3 | Known issues in Mbed TLS are [tracked on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). |
| Gilles Peskine | 74a7f93 | 2021-03-16 12:05:44 +0100 | [diff] [blame] | 4 | |
| 5 | ## Reporting a bug |
| 6 | |
| 7 | If you think you've found a bug in Mbed TLS, please follow these steps: |
| 8 | |
| 9 | 1. Make sure you're using the latest version of a |
| Dave Rodgman | 0da8c51 | 2024-03-18 15:25:53 +0000 | [diff] [blame] | 10 | [maintained branch](BRANCHES.md): `main`, `development`, |
| Gilles Peskine | 74a7f93 | 2021-03-16 12:05:44 +0100 | [diff] [blame] | 11 | or a long-time support branch. |
| Dave Rodgman | 017a199 | 2022-03-31 14:07:01 +0100 | [diff] [blame] | 12 | 2. Check [GitHub](https://github.com/Mbed-TLS/mbedtls/issues) to see if |
| Gilles Peskine | 74a7f93 | 2021-03-16 12:05:44 +0100 | [diff] [blame] | 13 | your issue has already been reported. If not, … |
| 14 | 3. If the issue is a security risk (for example: buffer overflow, |
| 15 | data leak), please report it confidentially as described in |
| 16 | [`SECURITY.md`](SECURITY.md). If not, … |
| Dave Rodgman | 017a199 | 2022-03-31 14:07:01 +0100 | [diff] [blame] | 17 | 4. Please [create an issue on on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). |
| Gilles Peskine | 74a7f93 | 2021-03-16 12:05:44 +0100 | [diff] [blame] | 18 | |
| 19 | Please do not use GitHub for support questions. If you want to know |
| 20 | how to do something with Mbed TLS, please see [`SUPPORT.md`](SUPPORT.md) for available documentation and support channels. |