mirror of
				https://github.com/Mbed-TLS/mbedtls.git
				synced 2025-10-28 23:14:56 +03:00 
			
		
		
		
	Add BUGS.md
Instructions on how to report a bug. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
		
							
								
								
									
										20
									
								
								BUGS.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										20
									
								
								BUGS.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,20 @@ | |||||||
|  | ## Known issues | ||||||
|  |  | ||||||
|  | Known issues in Mbed TLS are [tracked on GitHub](https://github.com/ARMmbed/mbedtls/issues). | ||||||
|  |  | ||||||
|  | ## Reporting a bug | ||||||
|  |  | ||||||
|  | If you think you've found a bug in Mbed TLS, please follow these steps: | ||||||
|  |  | ||||||
|  | 1. Make sure you're using the latest version of a | ||||||
|  |    [maintained branch](BRANCHES.md): `master`, `development`, | ||||||
|  |    or a long-time support branch. | ||||||
|  | 2. Check [GitHub](https://github.com/ARMmbed/mbedtls/issues) to see if | ||||||
|  |    your issue has already been reported. If not, … | ||||||
|  | 3. If the issue is a security risk (for example: buffer overflow, | ||||||
|  |    data leak), please report it confidentially as described in | ||||||
|  |    [`SECURITY.md`](SECURITY.md). If not, … | ||||||
|  | 4. Please [create an issue on on GitHub](https://github.com/ARMmbed/mbedtls/issues). | ||||||
|  |  | ||||||
|  | Please do not use GitHub for support questions. If you want to know | ||||||
|  | how to do something with Mbed TLS, please see [`SUPPORT.md`](SUPPORT.md) for available documentation and support channels. | ||||||
		Reference in New Issue
	
	Block a user