From 1bd531dec0b4eb745fb8856d14c1aba2b8a73026 Mon Sep 17 00:00:00 2001 From: Tim Hall Date: Sun, 1 Nov 2020 20:59:36 +0000 Subject: MLBEDSW-3249: Vela config file examples - Added sample vela.ini config file - Changed vela config format, split into system config and memory mode - Removed unused CPU cycle performance estimation - Added new CLI options for --memory-mode and --verbose-config - Changed CLI option --config to take multiple files - Removed CLI option --global-memory-clock-scales - Changed error helper functions to raise a VelaError exception - Refactored to create a new is_spilling_enabled function Signed-off-by: Tim Hall Change-Id: I27c41577e37a3859edb9524cd99784be10ef0a0d --- SECURITY.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) (limited to 'SECURITY.md') diff --git a/SECURITY.md b/SECURITY.md index d1aa6b49..c795d52a 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -7,24 +7,25 @@ then we encourage you to responsibly disclose it to us as soon as possible. Arm takes security issues seriously and welcomes feedback from researchers and the security community in order to improve the security of its products -and services. We operate a coordinated disclosure policy for disclosing +and services. We operate a coordinated disclosure policy for disclosing vulnerabilities and other security issues. Security issues can be complex and one single timescale doesn't fit all -circumstances. We will make best endeavours to inform you when we expect +circumstances. We will make best endeavours to inform you when we expect security notifications and fixes to be available and facilitate coordinated disclosure when notifications and patches/mitigations are available. ### Report -For all security issues, contact Arm by email at [arm-security@arm.com](mailto:arm-security@arm.com). -In the body of the email include as much information as possible about the issue -or vulnerability and any additional contact details. +For all security issues, contact Arm by email at +[arm-security@arm.com](mailto:arm-security@arm.com). In the body of the email +include as much information as possible about the issue or vulnerability and any +additional contact details. ### Secure submission using PGP We support and encourage secure submission of vulnerability reports using PGP, -using the key below. If you would like replies to be encrypted, please provide +using the key below. If you would like replies to be encrypted, please provide your own public key through a secure mechanism. ~~~none @@ -80,4 +81,5 @@ yYCr2gCFPymkkRYhPr2w5EgbWyzLaBIwqjyIbXaveuB3DYi2Lhbf64I= -----END PGP PUBLIC KEY BLOCK----- ~~~ -For more information visit \ No newline at end of file +For more information visit + \ No newline at end of file -- cgit v1.2.1