Glad that we could locate the issue.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 30 2018
Thanks for the detailed information. From the log I can see the same behavior as in T3769 with the TITUS plugin. No Read event is passed to us.
I've added MailStore to the list of incompatible addons for now https://wiki.gnupg.org/GpgOL/IncompatibleAddons
Thanks for the great direction on how to debug the issue any further.
gpg 2.2.4-1ubunt amd64 GNU Privacy Guard -- minimalist p
The hang appears random. It sometimes works 4 out of 5 times.
With latest gpg-error and latest gnupg It still hangs for me after printing the certificate.
It's possible that was one of the upstream patches they decided to include.
It is in 1.30 which I released a few minutes ago. Only minor other changes.
@dcialdella Do you have a "non standard" GnuPG / GPGME installed? What are the versions?
I have the same issue with Xubuntu 18.04 lts, and GNUPG.
./start_linux_64bit
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"
Clearly getting SWIG and Windows to play together nicely is a bit of a big ask, but it may be possible to leverage GPGME's compiled libraries with something like CFFI's ABI calling method (yeah, I know, ABI is never ideal, but it's better than what Windows has now).
The last change to the python installer was, IIRC, one I discussed with Justus off-list around the middle of, um, last year? Maybe the year before?
Apr 29 2018
Apr 28 2018
@werner I'm afraid you are too late. Looks like this was merged into master about three years ago. I probably should not have commented on a commit that was merged so long ago :)
You need to give the --with-foo options for each package.
No, we won't cripple GnuPG for testing purposes. You intended to test something else than the provided GnuPG.
Please don't apply this, SYSROOT is not a well defined feature and it needs to be implemented everywhere in the same way.
SYSROOT support is not yet fully implemented. You need to give the --with-foo options for each package.
I will retitle this bug to indicates tha tit is a feature request.
Apr 27 2018
Now there it gets complicated. According to the card software author in 3.3 and even 2.2 there is a fix. BUT there was a small amount of cards already created in 3.3 without the fix. Nobody ever told my how to diferentiate them.
There is no Version 3.3.1 you can by - it is only 3.3. So you can buy one and hope you have a good one.
At least this is my understanding.
@aheinecke maybe recheck with GNUPG 2.2.6 or 2.2.7.
I'm using the kdepim-docker for tests, that is based on KDE Neon, that is based on Ubuntu xenial (16.04), so the version for GnuPG2 is 2.1.11-6ubuntu2. Good to know, that the GnuPG version also matters for this stuff.
Why are you looking in ${SYSROOT}/bin and not ${SYSROOT}/usr/bin? I am not sure libassuan-config is installed in different directories for different OS distros. But on my distro it is installed in /usr/bin. Has it moved from /bin to /usr/bin? When cross-compiling for ARM, the check on line 30 does not find it in sysroot and the result is it uses the host libassuan-config. See https://bugs.gentoo.org/653938
I now have all three fuzz targets stable now, and not finding more bugs besides the reported memory leaks
https://github.com/gpg/gnupg/compare/master...catenacyber:7651c60
What do you think of it ? Do you want to use it for continuous integration ?
Hi Andre,
Thanks for the tip, moving unopened secure email to a folder is the solution, I guess I just had to ask.
Beta? the last issue I report I was told to test on the beta which worked and forgot upgrade afterward.
ALL GOOD! Merci!
Jacques
From: aheinecke (Andre Heinecke) <noreply@dev.gnupg.org>
Sent: April 27, 2018 12:43 AM
To: Jacques Latour <Jacques.Latour@cira.ca>
Subject: [Task] [Closed] T3943: gpgOL
aheinecke closed this task as "Invalid".
aheinecke added a comment.
yes sorry, but due to a design limitation it's impossible to move mails while the decrypted / verified content is visible. Our task for this is T3459https://dev.gnupg.org/T3459 (so I'm closing here as invalid even though the problem is valid.)
As workaround you have to move mails while they are not shown. E.g. if you move them without selecting them, or unselect a mail by shift clicking it. Here is an example what I mean by that:
https://files.intevation.de/users/aheinecke/gpgol_moving.gif
Btw. Is there a reason why you are using a beta and not 3.1.0 ?
TASK DETAIL
https://dev.gnupg.org/T3943
EMAIL PREFERENCES
https://dev.gnupg.org/settings/panel/emailpreferences/
To: aheinecke
Cc: aheinecke, latour_jacques, gp_ast
This is an automated email from the GnuPG development hub. If you have registered in the past at https://bugs.gnupg.org/ your account was migrated automatically. You can visit https://dev.gnupg.org/ to set a new password and update your email preferences.
Ok so it was impossible to detect when a mail is printed and block the printing until the decryption was completed.
This was fixed with 7eed3c4c5e9f84bed0e412213cf404a18cd54358
Oops. I also opened T3939 about this.
I can't reproduce this with GnuPG 2.2.6 or 2.2.7 beta and GPGME 1.11.0 . There I correctly get User Canceled for OpenPGP but "No Secret Key" for S/MIME, also using GpgME++.
Hi Carlos,
yes sorry, but due to a design limitation it's impossible to move mails while the decrypted / verified content is visible. Our task for this is T3459 (so I'm closing here as invalid even though the problem is valid.)
Apr 26 2018
I note that this problem could also affect a user with multiple identities, one of which has their decryption keys on a smartcard. If a message arrives encrypted to both identities, but the user does not have their smartcard available, they will hit the same issue.
Does v3.3.1 fix this? (The release notes for it seem to imply that's not the case.)