Page MenuHome GnuPG

gpgolProject
ActivePublic

Members

  • This project does not have any members.
  • View All

Watchers (1)

Recent Activity

Today

aheinecke triaged T6864: GpgOL: Invalid filenames are not checked for temporary files as Normal priority.
Mon, Dec 4, 11:10 AM · vsd33, Restricted Project, gpgol

Thu, Nov 30

aheinecke triaged T6861: GpgOL: Crash when switching from calendar back to mailview as High priority.
Thu, Nov 30, 4:17 PM · Restricted Project, gpgol

Wed, Nov 29

aheinecke closed T6856: GpgOL is reported as slowing down the start of Outlook as Resolved.

I am closing this as resolved for now. I would need a completely new client or mess with the registry keys in which outlook stores the performance data to test this. But I would bet it still lists us as responsible for the slow start of outlook. But the time it will then show should now be 0ms since we absolutely do nothing anymore in our DLLMain.

Wed, Nov 29, 10:57 PM · vsd32, gpgol, Bug Report, gpg4win
aheinecke added a comment to T6856: GpgOL is reported as slowing down the start of Outlook.

I don't really know how to test this though since it tracks this over time and history. Let us see if my change fixes this, It may be that outlook does not measure the DLLMain (which I am pretty sure it does) but the actual COM initialization, in which case my change did nothing. But I don't see any way in which my change could make things worse.

Wed, Nov 29, 10:40 PM · vsd32, gpgol, Bug Report, gpg4win
aheinecke triaged T6856: GpgOL is reported as slowing down the start of Outlook as High priority.

I think outlook shows any native addin there. As you can see by the empty bar we don't really do anything in there to slow it down. But let me check if I can move the extremely little code we have in there somewhere else.

Wed, Nov 29, 8:32 PM · vsd32, gpgol, Bug Report, gpg4win
ArminiXTS added a comment to T6856: GpgOL is reported as slowing down the start of Outlook.

Wed, Nov 29, 7:48 PM · vsd32, gpgol, Bug Report, gpg4win
ArminiXTS created T6856: GpgOL is reported as slowing down the start of Outlook.
Wed, Nov 29, 7:48 PM · vsd32, gpgol, Bug Report, gpg4win
aheinecke triaged T6854: Kleopatra / libkleo: Improve tooltips for unusable keys in keyresolver as Low priority.
Wed, Nov 29, 7:15 PM · Restricted Project, libkleo, gpgol

Mon, Nov 27

ebo moved T6837: GpgOL: Keyresolver size default too small from QA to vsd-3.2.0 on the vsd32 board.
Mon, Nov 27, 4:00 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
ebo added a comment to T6837: GpgOL: Keyresolver size default too small.

I can confirm this

Mon, Nov 27, 4:00 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo

Sat, Nov 25

aheinecke added a comment to T6837: GpgOL: Keyresolver size default too small.

Works nicely for me in beta300

Sat, Nov 25, 10:18 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke moved T6837: GpgOL: Keyresolver size default too small from Backlog to QA on the vsd32 board.
Sat, Nov 25, 10:17 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke changed the status of T6837: GpgOL: Keyresolver size default too small from Open to Testing.

Looks good now

Sat, Nov 25, 5:12 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke added a comment to T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST.

The Keyresolver did not allow me to encrypt to an S/MIME cert where the root CA was not in my trustlist.txt that was part of this feature to allow users to encrypt "non vs-nfd compliant" to such untrusted keys, like they would be able to also encrypt to untrusted openpgp keys.

Sat, Nov 25, 4:40 AM · vsd32 (vsd-3.2.0), vsd, Restricted Project, gpgol
aheinecke added a comment to T6837: GpgOL: Keyresolver size default too small.

New MR: https://invent.kde.org/pim/libkleo/-/merge_requests/61

Sat, Nov 25, 4:11 AM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo

Fri, Nov 24

aheinecke added a project to T6837: GpgOL: Keyresolver size default too small: vsd32.

MR for this: https://invent.kde.org/pim/libkleo/-/merge_requests/60/

Fri, Nov 24, 6:41 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke added a project to T6837: GpgOL: Keyresolver size default too small: Restricted Project.

I am temped to put the VSD-3.2 flag on it and raise prio to high because of strategic reasons... So if someone has a cheap fix for this. Please go for it.

Fri, Nov 24, 4:31 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke triaged T6837: GpgOL: Keyresolver size default too small as Normal priority.
Fri, Nov 24, 4:29 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol, libkleo
aheinecke added a comment to T6828: GpgOL: Decrypting encrypted drafts with S/MIME smartcard results in Operation Cancelled.

Similarly if you decrypt with a PKI BW card and the mimeviewer there are also no longer problems which again might be related that the internal states where somewhat disturbed by the loop in Kleopatra.

Fri, Nov 24, 3:05 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol
aheinecke closed T6828: GpgOL: Decrypting encrypted drafts with S/MIME smartcard results in Operation Cancelled as Resolved.

I retested this with the current beta and It works without problems. I somehow suspect that the permanent access loop from Kleopatra caused other Smartcard operations to be canceled. Since the test setup is not really good to reproduce to for Ebo I resolved this myself.

Fri, Nov 24, 3:04 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol
aheinecke moved T6828: GpgOL: Decrypting encrypted drafts with S/MIME smartcard results in Operation Cancelled from Backlog to vsd-3.2.0 on the vsd32 board.
Fri, Nov 24, 3:03 PM · vsd32 (vsd-3.2.0), Restricted Project, gpgol
ebo moved T6823: GpgOL: Security Approval reports "Operation Failed" error if key generation was canceled from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Fri, Nov 24, 11:44 AM · vsd32 (vsd-3.2.0), libkleo, gpgol, Restricted Project

Thu, Nov 23

ebo moved T6823: GpgOL: Security Approval reports "Operation Failed" error if key generation was canceled from QA to vsd-3.2.0 on the vsd32 board.
Thu, Nov 23, 5:26 PM · vsd32 (vsd-3.2.0), libkleo, gpgol, Restricted Project
ebo added a comment to T6823: GpgOL: Security Approval reports "Operation Failed" error if key generation was canceled.

Works on windows, too. VS-Desktop-3.1.90.295-Beta

Thu, Nov 23, 5:25 PM · vsd32 (vsd-3.2.0), libkleo, gpgol, Restricted Project
ebo moved T6813: GpgOL: Key generation window does not close from QA to vsd-3.2.0 on the vsd32 board.
Thu, Nov 23, 5:08 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ebo added a comment to T6813: GpgOL: Key generation window does not close.

works, VS-Desktop-3.1.90.295-Beta

Thu, Nov 23, 5:07 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ebo moved T6566: GpgOL: newly generated key not loaded in the security confirmation dialog from QA to vsd-3.2.0 on the vsd32 board.
Thu, Nov 23, 5:06 PM · vsd32 (vsd-3.2.0), gpgol, Restricted Project
ebo added a comment to T6566: GpgOL: newly generated key not loaded in the security confirmation dialog.

works, VS-Desktop-3.1.90.295-Beta

Thu, Nov 23, 5:05 PM · vsd32 (vsd-3.2.0), gpgol, Restricted Project
aheinecke moved T6823: GpgOL: Security Approval reports "Operation Failed" error if key generation was canceled from Backlog to QA on the vsd32 board.
Thu, Nov 23, 2:18 PM · vsd32 (vsd-3.2.0), libkleo, gpgol, Restricted Project
aheinecke moved T6827: GpgOL: Check S/MIME draft encrypt and use GPGME_ENCRYPT_ALWAYS_TRUST from WiP to QA on the vsd32 board.
Thu, Nov 23, 2:17 PM · gpgol, Restricted Project, vsd32
aheinecke moved T6813: GpgOL: Key generation window does not close from WiP to QA on the vsd32 board.
Thu, Nov 23, 2:16 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project

Tue, Nov 21

ikloecker changed the status of T6813: GpgOL: Key generation window does not close from Open to Testing.

I have added a workaround and tested it on Windows. Works now for me, including T6566.

Tue, Nov 21, 1:58 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
aheinecke added a comment to T6813: GpgOL: Key generation window does not close.

@ikloecker I suggest giving up on this, I know that it is frustrating but it does not make much sense, it is probably related to some compiler settings / Qt cross compile issue and might be a bug in qt. Just do an old style connect and leave a comment that we will revisit this with Qt6. When VSD 3.2 is our last major release based on Qt5 we should not spend too much time investigating this which might be completely different (or not) with Qt6.

Tue, Nov 21, 7:34 AM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project

Mon, Nov 20

ikloecker moved T6813: GpgOL: Key generation window does not close from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Mon, Nov 20, 8:22 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ikloecker claimed T6813: GpgOL: Key generation window does not close.
Mon, Nov 20, 8:22 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ikloecker added a comment to T6813: GpgOL: Key generation window does not close.

And it's the signals that are not found. I don't see any indication that this has anything to do with the slots/lambdas.

Mon, Nov 20, 2:17 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ikloecker added a comment to T6813: GpgOL: Key generation window does not close.

Well, the failed new style connects are logged for me with "QObject::connect: signal not found in QGpgME::QGpgMEQuickJob". I haven't dug into how the check works for those connects. It turns out that none of the three connects to the signals of QuickJob work (two of those connects are done in ProgressDialog). Even the connect to the argument-less done() signal. So this has nothing to do with default arguments. This is very disturbing because this means that any other connect might also be broken.

Mon, Nov 20, 2:15 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
aheinecke added a comment to T6813: GpgOL: Key generation window does not close.

Ah no I see the difference here. Instead of connecting to a lambda with no args 96da231f97eff9485f62ab925d81252f5f97fc31 connected to the functions which were used in the old signal / slot syntax. I think the fix might be to explicitly list the args of the quickjob result or to use afunction to handle the keygenresult.

Mon, Nov 20, 1:56 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ebo moved T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST from QA to vsd-3.2.0 on the vsd32 board.
Mon, Nov 20, 1:49 PM · vsd32 (vsd-3.2.0), vsd, Restricted Project, gpgol
ebo added a comment to T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST.

works, VS-Desktop-3.1.90.287-Beta

Mon, Nov 20, 1:48 PM · vsd32 (vsd-3.2.0), vsd, Restricted Project, gpgol
aheinecke added a comment to T6813: GpgOL: Key generation window does not close.

It does not log failed connections but new style connections are never logged when they fail. Since they can't fail ;-)

Mon, Nov 20, 1:43 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
aheinecke moved T6813: GpgOL: Key generation window does not close from Backlog to WiP on the vsd32 board.
Mon, Nov 20, 1:40 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
aheinecke added a project to T6813: GpgOL: Key generation window does not close: vsd32.
Mon, Nov 20, 1:40 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
aheinecke raised the priority of T6813: GpgOL: Key generation window does not close from Normal to High.

Let me put this on the 3.2 workboard since we already have the "reports error when canceled" on that workboard and T6566 too depens on this, in fact I am currently working on this even though it was not on the workbaord.

Mon, Nov 20, 1:40 PM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project
ebo added a comment to T6566: GpgOL: newly generated key not loaded in the security confirmation dialog.

Seems T6813 blocks me from testing this. The generate window does not close and even if I abort the window, the generated key is not loaded. It is not selectable even if I remove the filter.

Mon, Nov 20, 1:30 PM · vsd32 (vsd-3.2.0), gpgol, Restricted Project
aheinecke triaged T6828: GpgOL: Decrypting encrypted drafts with S/MIME smartcard results in Operation Cancelled as High priority.
Mon, Nov 20, 11:06 AM · vsd32 (vsd-3.2.0), Restricted Project, gpgol
aheinecke moved T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST from WiP to QA on the vsd32 board.
Mon, Nov 20, 10:31 AM · vsd32 (vsd-3.2.0), vsd, Restricted Project, gpgol
aheinecke moved T6566: GpgOL: newly generated key not loaded in the security confirmation dialog from WiP to QA on the vsd32 board.
Mon, Nov 20, 10:31 AM · vsd32 (vsd-3.2.0), gpgol, Restricted Project
ikloecker added a comment to T6813: GpgOL: Key generation window does not close.

Does Qt log failed connections?

Mon, Nov 20, 8:25 AM · vsd32 (vsd-3.2.0), gpgol, libkleo, Restricted Project

Sun, Nov 19

aheinecke changed the status of T6827: GpgOL: Check S/MIME draft encrypt and use GPGME_ENCRYPT_ALWAYS_TRUST from Open to Testing.
Sun, Nov 19, 2:16 PM · gpgol, Restricted Project, vsd32