mbedtls/SECURITY.md

## Reporting Vulneratibilities

If you think you have found an Mbed TLS security vulnerability, then please
send an email to the security team at
<mbed-tls-security@lists.trustedfirmware.org>.

## Security Incident Handling Process

Our security process is detailed in our
[security
center](https://developer.trustedfirmware.org/w/mbed-tls/security-center/).

Its primary goal is to ensure fixes are ready to be deployed when the issue
goes public.

## Maintained branches

Only the maintained branches, as listed in [`BRANCHES.md`](BRANCHES.md),
get security fixes.
Users are urged to always use the latest version of a maintained branch.
Add SECURITY.md There was no mention of our security email address, nor of our security process, in the repo, which made them hard to discover for contributors. Also, this filename is recognized by github: https://docs.github.com/en/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com> 2021-02-25 10:41:38 +00:00			`## Reporting Vulneratibilities`

			`If you think you have found an Mbed TLS security vulnerability, then please`
			`send an email to the security team at`
			`<mbed-tls-security@lists.trustedfirmware.org>.`

			`## Security Incident Handling Process`

Redo of PR#5345. Fixed spelling and typographical errors found by CodeSpell. Signed-off-by: Shaun Case <warmsocks@gmail.com> Signed-off-by: Dave Rodgman <dave.rodgman@arm.com> 2021-12-21 05:14:10 +00:00			`Our security process is detailed in our`
Minor presentation improvements Minor wording improvement and cosmetic formatting improvements. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2021-03-16 11:04:44 +00:00			`[security`
Add SECURITY.md There was no mention of our security email address, nor of our security process, in the repo, which made them hard to discover for contributors. Also, this filename is recognized by github: https://docs.github.com/en/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com> 2021-02-25 10:41:38 +00:00			`center](https://developer.trustedfirmware.org/w/mbed-tls/security-center/).`

			`Its primary goal is to ensure fixes are ready to be deployed when the issue`
			`goes public.`

			`## Maintained branches`

Minor presentation improvements Minor wording improvement and cosmetic formatting improvements. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2021-03-16 11:04:44 +00:00			Only the maintained branches, as listed in [`BRANCHES.md`](BRANCHES.md),
			`get security fixes.`
Add SECURITY.md There was no mention of our security email address, nor of our security process, in the repo, which made them hard to discover for contributors. Also, this filename is recognized by github: https://docs.github.com/en/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com> 2021-02-25 10:41:38 +00:00			`Users are urged to always use the latest version of a maintained branch.`