From d5f6dec048d3d4d94f1fcdb3f4249cf6e71c4b92 Mon Sep 17 00:00:00 2001 From: Ben McGinnes Date: Mon, 19 Mar 2018 15:03:00 +1100 Subject: [PATCH] doc: python bindings howto * Slight python-gnupg clarification. See also this thread: https://lists.gnupg.org/pipermail/gnupg-devel/2018-March/033528.html --- lang/python/docs/GPGMEpythonHOWTOen.org | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lang/python/docs/GPGMEpythonHOWTOen.org b/lang/python/docs/GPGMEpythonHOWTOen.org index 4a215544..b364b516 100644 --- a/lang/python/docs/GPGMEpythonHOWTOen.org +++ b/lang/python/docs/GPGMEpythonHOWTOen.org @@ -115,11 +115,11 @@ The popularity of this package stemmed from its ease of use and capability in providing the most commonly required features. - Unfortunately it has been beset by a number of security issues, - most of which stemmed from using unsafe methods of accessing the - command line via the =subprocess= calls. While some effort has - been made over the last two to three years (as of 2018) to - mitigate this, particularly by no longer providing shell access + Unfortunately it has been beset by a number of security issues in + the past; most of which stemmed from using unsafe methods of + accessing the command line via the =subprocess= calls. While some + effort has been made over the last two to three years (as of 2018) + to mitigate this, particularly by no longer providing shell access through those subprocess calls, the wrapper is still somewhat limited in the scope of its GnuPG features coverage.