| 1 |
Disable using secure memory for pygcrypt backend since we are not |
| 2 |
processing secrets. This can avoid the libgcrypt memory error; however, |
| 3 |
it turned out to be a huge memory/resource leak which needs to be fixed |
| 4 |
independently. |
| 5 |
--- |
| 6 |
pym/portage/checksum.py | 3 ++- |
| 7 |
1 file changed, 2 insertions(+), 1 deletion(-) |
| 8 |
|
| 9 |
diff --git a/pym/portage/checksum.py b/pym/portage/checksum.py |
| 10 |
index 9e7bffea9..4174638e6 100644 |
| 11 |
--- a/pym/portage/checksum.py |
| 12 |
+++ b/pym/portage/checksum.py |
| 13 |
@@ -161,7 +161,8 @@ if False: |
| 14 |
|
| 15 |
class GCryptHashWrapper(object): |
| 16 |
def __init__(self, algo): |
| 17 |
- self._obj = pygcrypt.hashcontext.HashContext(algo=algo) |
| 18 |
+ self._obj = pygcrypt.hashcontext.HashContext(algo=algo, |
| 19 |
+ secure=False) |
| 20 |
|
| 21 |
def update(self, data): |
| 22 |
self._obj.write(data) |
| 23 |
-- |
| 24 |
2.15.1 |
Archives