https://bugs.kde.org/show_bug.cgi?id=386791
--- Comment #7 from Stefan Brüns ---
Git commit 3aa911d4a0ac88a0a8adf3076f579a8ba4f73ed5 by Stefan Brüns.
Committed on 08/02/2019 at 14:21.
Pushed by bruns into branch 'master'.
[Extractor] Exclude GPG encrypted data from being indexed
Summary:
https://bugs.kde.org/show_bug.cgi?id=386791
Stefan Brüns changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #6 from Stefan Brüns ---
https://bugs.kde.org/show_bug.cgi?id=386791
--- Comment #5 from Victor Bouvier-Deleau
---
(In reply to Stefan Brüns from comment #4)
> The file is equivalent to e.g. the output of the following?
>
> $> dd if=/dev/zero bs=1k count=1000 | gpg2 -a -e -o foo.gpg -r
>
> Although the file is
https://bugs.kde.org/show_bug.cgi?id=386791
Stefan Brüns changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=386791
--- Comment #3 from Victor Bouvier-Deleau
---
Ok so the steps to reproduce the bug without having access to my files would
be:
1. Create a lot of GPG encrypted files that would amount for 1GiB or so
2.
https://bugs.kde.org/show_bug.cgi?id=386791
--- Comment #2 from Nate Graham ---
Go ahead and just add another comment. I don't think we need your
encrypted file. :)
Nate
On 11/12/2017 01:32 PM, Victor Bouvier-Deleau wrote:
> https://bugs.kde.org/show_bug.cgi?id=386791
>
https://bugs.kde.org/show_bug.cgi?id=386791
--- Comment #1 from Victor Bouvier-Deleau
---
I don't see a way to edit comments and I accidentaly pressed enter while
editing the previous one...
I'm able to reproduce the leak every time. If I
https://bugs.kde.org/show_bug.cgi?id=386791
Nate Graham changed:
What|Removed |Added
CC||pointedst...@zoho.com
--