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