build.log396 KBDownload
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Aug 21 2023
Aug 21 2023
thesamesam added a comment to T6673: gpgme-1.22.0 fails to compile tests (when building in source tree).
Done. Will be tested with T5903: Kleopatra: Add refresh button in certificatedetails .
Minor correction of the interface changes:
qt: toLogString NEW.
Aug 17 2023
Aug 17 2023
• ikloecker added a comment to T6554: Kleopatra: Reports success when gpgtar is kill with SIGTERM or SIGKILL while folder is encrypted.
Yes, gpgtar emits a SUCCESS status. gpgme should probably check for this.
Aug 14 2023
Aug 14 2023
Done. This can be tested with the run-import test runner (which I did).
• ikloecker moved T6648: GpgME: Support offline flag for all operations of gpgsm from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker triaged T6648: GpgME: Support offline flag for all operations of gpgsm as Normal priority.
Aug 11 2023
Aug 11 2023
Closing. For now, all that's needed has been added to GpgME. Additional changes in Kleopatra are tracked in T5903: Kleopatra: Add refresh button in certificatedetails . If further changes in GpgME are needed, then a new task will be opened.
Jul 31 2023
Jul 31 2023
Jul 28 2023
Jul 28 2023
• ikloecker changed the status of T6622: Kleopatra: Misleading result when decrypting clear signed message followed by public key block in notepad from Open to Testing.
Should be fixed.
• werner raised the priority of T6622: Kleopatra: Misleading result when decrypting clear signed message followed by public key block in notepad from Normal to High.
• ikloecker changed the status of T6617: General error when trying to decrypt a public key block in the notepad from Open to Testing.
The error was changed to "Bad data" which should be more appropriate.
• werner added a comment to T6617: General error when trying to decrypt a public key block in the notepad.
I would change the error to GPG_ERR_BAD_DATA .
Jul 27 2023
Jul 27 2023
• werner renamed T6620: Add a way to extract ECC key parameters from a public key from Add a way to extarct ECC key parameters from a public key to Add a way to extract ECC key parameters from a public key.
• werner triaged T6620: Add a way to extract ECC key parameters from a public key as Normal priority.
Jul 26 2023
Jul 26 2023
• ikloecker updated subscribers of T6617: General error when trying to decrypt a public key block in the notepad.
I had a look at this. gpg emits the following status messages:
[GNUPG:] UNEXPECTED 0<LF> [GNUPG:] FAILURE decrypt 38<LF>
• ebo updated the task description for T6617: General error when trying to decrypt a public key block in the notepad.
• aheinecke closed T6332: GPG: Extend / rework "is_file_compressed", a subtask of T6351: Kleopatra: Performance problems when encrypting large files, as Resolved.
Jul 25 2023
Jul 25 2023
@ikloecker I think your logs contain only false positives, I do not know that we use any defines created by config.h. Maybe for gpgme_off_t but even so when I moved gpgme++ and qgpgme from kdepimlibs into the GPGME repo I did not add any defines to configure for that.
Jul 24 2023
Jul 24 2023
• ebo moved T5906: gpgme cpp/qt: Only export symbols that are part of the ABI from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T5943: gpg: Report details about failed symmetric decrypt with ERROR status from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jul 20 2023
Jul 20 2023
• ebo moved T5478: Kleopatra: Performance problems decrypting and encrypting large Archives from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jul 19 2023
Jul 19 2023
• aheinecke closed T5478: Kleopatra: Performance problems decrypting and encrypting large Archives as Resolved.
Jul 10 2023
Jul 10 2023
One complication comes from the fact that gpgmepp and qgpgme include the global config.h that is generated by configure. This needs to be replaced. I'll attach two files where I grepped for usage of the config.h's #defines (generated on Linux) in lang/cpp and lang/qt. The files probably contain false positives.
defines-used-in-lang-cpp.txt1 KBDownload
defines-used-in-lang-qt.txt8 KBDownload
I was able to find the Craft blueprint with the CMake build system in my Win VM and pushed it to invent: https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/5e9aae4d006f69657d3612c2fe398c9e5ae69ac0, feel free to use it for inspiration or base for future work, or ignore it completely :). It's probably far from a production-ready CMake script, some years ago I just really really *really* wanted to build KMail on Windows (don't ask why) so I did some unspeakable evils to make it happen. This is one of the better things that came out of it...
Jul 7 2023
Jul 7 2023
Jul 6 2023
Jul 6 2023
• ebo closed T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename as Resolved.
as this task is for a technical restructuring task, which is obviously done and works, closing this ticket.
• ebo added a comment to T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename.
On the command line:
gpgtar -v --status-fd 2 -er Ted -s -o tt.tar.gpg tiefer_test
leaves a .tar.gpg file behind, too, if
- you kill it with CTRL-C
- if you call it without -s and stop the gpgtar.exe process in the task manager
- if you call it with -s and give the correct password
• ikloecker added a comment to T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename.
I'm wondering why I don't see something like
org.kde.pim.kleopatra: slotResult Removing output file ... after error or cancel
in the debug output. It should be output whenever the signing and/or encryption job ended with a non-zero error code and the output file exists. (See commit on 22 June).
• ebo added a comment to T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename.
On Windows the process is stopped but you end up with a too small archive.
If you cancel immediately (presumably as long as the file still has size 0) it is removed, though.
Jul 5 2023
Jul 5 2023
Jul 5 2023, 11:56 AM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
• werner moved T6534: gpg's progress_filter needs to use uint64_t from Backlog to WiP on the gnupg22 board.
Jul 5 2023, 11:16 AM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
Jul 4 2023
Jul 4 2023
• werner moved T6534: gpg's progress_filter needs to use uint64_t from QA to gnupg-2.4.3 on the gnupg24 board.
Jul 4 2023, 2:44 PM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
• aheinecke added a comment to T5478: Kleopatra: Performance problems decrypting and encrypting large Archives.
I ran the test AES.OCB encrypt only, no compression test with the same GnuPG 2.4 version on Linux.
Jul 3 2023
Jul 3 2023
Jul 3 2023, 2:48 PM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
• aheinecke triaged T6572: Kleopatra / GPGME: Show difference between nonRepudiation and digitalSignature in summary line as Wishlist priority.
This works.
Jun 22 2023
Jun 22 2023
• ikloecker added a comment to T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename.
When the output parameter is given it might even clean up a temporary file on error, but it might also not so we should make sure on a higher level that we check for that and remove it when gpgtar crashes or something like that.
• werner triaged T6554: Kleopatra: Reports success when gpgtar is kill with SIGTERM or SIGKILL while folder is encrypted as Normal priority.
Due to the double fork in gpgme we won't get the exit code which gpgtar emits. Possible actions in a signal handler are also limited; in particular we can't use stdio or estream. The only option to print a status line would we by using write directly. However, this might mess with the libassuan buffering. Thus, it is not a good idea to pkill gpgtar. Same is true for gpg and gpgsm.
• ikloecker renamed T6554: Kleopatra: Reports success when gpgtar is kill with SIGTERM or SIGKILL while folder is encrypted from Kleopatra: Reports success when gpgtar is kill with SIGTERM while folder is encrypted to Kleopatra: Reports success when gpgtar is kill with SIGTERM or SIGKILL while folder is encrypted.
Jun 21 2023
Jun 21 2023
• ikloecker changed the status of T5478: Kleopatra: Performance problems decrypting and encrypting large Archives from Open to Testing.
ready for testing
• ikloecker changed the status of T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename, a subtask of T5478: Kleopatra: Performance problems decrypting and encrypting large Archives, from Open to Testing.
• ikloecker changed the status of T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename, a subtask of T6351: Kleopatra: Performance problems when encrypting large files, from Open to Testing.
• ikloecker changed the status of T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename from Open to Testing.
Done. Can be tested and closed with T5478: Kleopatra: Performance problems decrypting and encrypting large Archives.
• ikloecker triaged T6550: GpgME / QGpgME Extend non-archive jobs to accept input / output from a filename as Normal priority.
Jun 16 2023
Jun 16 2023
I tested this with OpenPGP and 2.4.3-beta19 on Windows. Worked nicely.
Jun 16 2023, 2:39 PM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
Jun 15 2023
Jun 15 2023
• ikloecker changed the status of T6373: Kleopatra: Show progress dialog when moving decrypted archive to final destination, a subtask of T5478: Kleopatra: Performance problems decrypting and encrypting large Archives, from Testing to Open.
• werner moved T6534: gpg's progress_filter needs to use uint64_t from WiP to QA on the gnupg24 board.
Jun 15 2023, 11:21 AM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
And of course we also need to adjust GPGME
Jun 15 2023, 10:58 AM · gpgme (gpgme 1.23.x), gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.3), Feature Request, Restricted Project, Windows
Jun 12 2023
Jun 12 2023
• ikloecker changed the status of T5478: Kleopatra: Performance problems decrypting and encrypting large Archives from Testing to Open.
I'm reopening this. Its probably not a regression but I was sure that we had progress for large files fixed in the past.
Yeah no progress for files larger then 32 bit o.O... But this used to work 😭
On 64 bit linux this works btw. so I think it comes down to the difference between 32 bit off_t and 64 bit off_t
Yeah, its the ugly off_t again. I am just testing how this works with single files above that threshold we worked quite a bit on this back in the days https://dev.gnupg.org/T2368
Yeah, probably a Windows/MinGW 32-bit problem. GpgME::Data does
off_t size = seek(0, SEEK_END); seek(0, SEEK_SET); std::string sizestr = std::to_string(size); // Ignore errors as this is optional gpgme_data_set_flag(d->data, "size-hint", sizestr.c_str());
Probably some issue with large files / integer overflow. I am testing on Windows with 32 bit.
Jun 9 2023
Jun 9 2023
Mh, let me check where the size hint should come from and why it might be missing in my windows test. That is indeed strange then.
For me this does work also when decrypting:
btw. this does not work on the decrypting side because kleopatra there apparently does not provide a size hint. So it goes:
• aheinecke triaged T6530: GPGME / QGpgME Extend Archivejobs to accept input / output from a filename as High priority.
• aheinecke added a comment to T5478: Kleopatra: Performance problems decrypting and encrypting large Archives.
Oh my, so I have not really tested this for nearly three months and had my head in the send when reviewing it. I really need to apologize for that. The performance improvement is _not_ what I hoped for if it is even there.
Jun 5 2023
Jun 5 2023
• werner closed T5003: GpgME++: Add support for gpgme_set_expire, a subtask of T4999: GPGME: Add interface for quick-set-expire, as Resolved.
Jun 1 2023
Jun 1 2023
Works good enough for me
• aheinecke moved T6362: Libkleo, GpgOL: Use global inst-type flag of GPGME from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker closed T6510: GpgME++: Treat GPG_ERR_FULLY_CANCELED as GPG_ERR_CANCELED in GpgME::Error as Resolved.
Fixed.
May 31 2023
May 31 2023
• ikloecker triaged T6510: GpgME++: Treat GPG_ERR_FULLY_CANCELED as GPG_ERR_CANCELED in GpgME::Error as Normal priority.
May 25 2023
May 25 2023
secring.gpg is only used by unsupported legacy versions of GnuPG. Since 2.1 it is not anymore used.
May 24 2023
May 24 2023
So if I have \MyDirectory\pubring.pgp and MyDirectory\secring.pgp files, how do I use the --homedir option to access those?
May 23 2023
May 23 2023
Should be fixed now; see commit above.
FWIW: WriteFile and write are more different than in using a HANDLE vs. a libc file descriptor. Despite that a HANDLE might be a 64 bit pointer, it is guaranteed that the value fits into a 32 bit variable. But they still index different objects. The return code and error values are also different.
Much simpler: write is only used in the callbacks and over there gpgme_io_writen[n] shall be used anyway.
it's not hard to fix that header to actually provide a sensible write(), avoiding the issue listed on the mailing list, where there was no return to check:
May 22 2023
May 22 2023
May 19 2023
May 19 2023
This is not really what the issue here is talking about. This issue was about "merging" multiple keyrings into a single view. If I understand you correctly you want to have matching pubrings and secret key directories for different applications. That is fully covered and what many users do by setting GNUPGHOME through the environment, the --homedir option or the windows registry.
Did anything get implemented to handle this? We have a central network file share where we store our public and secret key rings. We have several different applications that access these key rings. I'm trying to convert one of them from using gpg.exe via the command line with the --keyring and --secret-keyring paramters to using gpgme, but I don't see a way to specify the keyrings. Any help would be appreciated.
May 19 2023, 12:18 PM · gnupg22 (gnupg-2.2.42), gnupg24 (gnupg-2.4.2), Bug Report, Restricted Project
Apr 27 2023
Apr 27 2023
works now, Gpg4win-4.1.1-beta295
Apr 26 2023
Apr 26 2023
• gniibe changed the status of T6466: gpgme python example code contains insecure code pattern / chmod permission race condition from Open to Testing.
@ikloecker Thanks for your comment. I put a comment in the commit.