aboutsummaryrefslogtreecommitdiffstats
path: root/docs/security.rst
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2016-02-19 07:11:03 -0500
committerAlex Gaynor <alex.gaynor@gmail.com>2016-02-19 07:11:03 -0500
commitf7721aaaa14f789e911a61e5e946d618521920a9 (patch)
tree545308e0857c0593797006dc89316efd615a46a4 /docs/security.rst
parentebcd037216a422ac5ac314099c47cbae02705e4c (diff)
downloadcryptography-f7721aaaa14f789e911a61e5e946d618521920a9.tar.gz
cryptography-f7721aaaa14f789e911a61e5e946d618521920a9.tar.bz2
cryptography-f7721aaaa14f789e911a61e5e946d618521920a9.zip
Good clarification from @dstufft
Diffstat (limited to 'docs/security.rst')
-rw-r--r--docs/security.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/security.rst b/docs/security.rst
index f937afb3..1cc1273d 100644
--- a/docs/security.rst
+++ b/docs/security.rst
@@ -28,8 +28,8 @@ To give a few examples of things we would consider security issues:
Examples of things we wouldn't consider security issues:
-* Offering ECB mode for symmetric encryption. Though ECB is critically weak, it
- is documented as being weak in our documentation.
+* Offering ECB mode for symmetric encryption in the *Hazmat* layer. Though ECB
+ is critically weak, it is documented as being weak in our documentation.
* Using a variable time comparison somewhere, if it's not possible to
articulate any particular program in which this would result in problematic
information disclosure.