From 878106732fa6dfd49f2a234e0976564d0725316f Mon Sep 17 00:00:00 2001 From: Stephan Bosch Date: Tue, 15 Jan 2019 16:24:10 +0100 Subject: [PATCH] =?utf8?q?=E2=80=9Cthird=20party=E2=80=9D=20is=20adjective?= =?utf8?q?=20and=20needs=20hyphen?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit --- docs/appendices/crypto-export.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/appendices/crypto-export.rst b/docs/appendices/crypto-export.rst index c4079a60a..9a1e3b023 100644 --- a/docs/appendices/crypto-export.rst +++ b/docs/appendices/crypto-export.rst @@ -2,7 +2,7 @@ Cryptographic software and export control ========================================= In certain legal climates, PowerDNS might potentially require an export control status, particularly since PowerDNS software contains cryptographic primitives. -PowerDNS does not itself implement any cryptographic algorithms but relies on third party implementations of AES, RSA, ECDSA, GOST, MD5 and various SHA-based hashing algorithms. +PowerDNS does not itself implement any cryptographic algorithms but relies on third-party implementations of AES, RSA, ECDSA, GOST, MD5 and various SHA-based hashing algorithms. Starting with 4.0.0, PowerDNS will link in hash and cryptographic primitives from the open source `OpenSSL `_ library. -- 2.40.0