- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 21 2021
Thank you for your report.
Let me rephrase from a viewpoint of mine (an implementer).
May 20 2021
The first two patch sets are now applied with the exception of
the gpgsplit fix; I did not applied that patch to add a free() in case of write errors.
Current look without public keys:
Ha! This would have affected Kleopatra if we followed werners suggestion to use default. But in Kleo I decided that I needed to show my users what the default is so we do not use default in this case.
In T5393#145098, @gniibe wrote:Please note that *_error-from_syserror accesses system's errno which may be cleared by xfree.
The paper describes another problem: interoperability (or interpretation) of "ElGamal encryption", and its impact.
This is another test case for GNU C library's strncmp:
This is the minimized test case.
May 19 2021
Having a fallback in Kleopatra makes sense because very old HKP keyservers don't return the fingerprint and LDAP keyservers not using the modernized schema do neither.
Please read also the report T5442 which is basically the same.
Thanks for the well written report. We had another already, and thus I merged it into T5415.
I did a new test and found that if it is a single file regardless of disk size, no error appears, but when there are multiple files in a single encrypted folder with a size greater than 1.5GB, the error occurs. Traverse a directory like Zorvek and Aheinecke wrote would be an optimal solution or at least some alert messsage to be aware of the action no supported.
I have removed all of the changed code in my working copy. ;-)
I just talked with werner about that and he told me that GnuPG can return the fingerprint. And I also mentioned to him that kleopatra really assumes that a Fingerprint is always set for a valid key object.
I have allowed myself to edit this task to more reflect what this is about. Although the error is of course in my opinion more of a bug because it is so bad but I would rather fix it with this feature.
I actually agree that this makes sense. I mean at least Kleo could say: "Hey we have detected 50 files that are encryped in this folder tree, do you really want to decrypt them all?"
Should have linked the commit with a patch for Gpg4win here: 22bc52775bdb I mostly needed that as an immediate fix for someone testing with ldap servers a lot.
Funny thing is that I can't replicate it anymore with the current version (2.2.18-beta77). I tested it on two machines and things just worked. One machine had just one reader and the other had several virtual readers in addition to the scr3500. After adding --reader-port for the latter it worked as well. I don't think I had a Windows update in the meantime.
Then let's get it in there. It's pretty easy to traverse a directory.
reading your report again: You clicked on a folder and expected that all encrypted files in this folder will be decrypted? That is unfortunately not supported.
May 18 2021
I have the same message when i try to decrypt files larger than 1.5GB in size; i atached the report "gpgconf --show-version"