- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 21 2022
Only just noticed that this was added incompletely, it was added to the build system but not linked in.
Dec 20 2022
Reopening this as there still seem to be ways to run into a deadlock as was reported in RT#13361. While I still think this points to some issue in gpgsm, when Testing this I found the behavior of Kleopatra to be wrong.
Has been remedied. We should have noticed before the release but the heavy warnings you get only appear if the binary is downloaded from the internet.
This was an accident. Will be fixed ASAP.
Dec 19 2022
Dec 13 2022
Dec 12 2022
Dec 9 2022
Dec 7 2022
Ok. So after further discussion. It is good that you kept a WKDRefreshJob copy :)
Dec 6 2022
I do not really understand why this is necessary. The problem is that /nonfatal conflicts with our msi creation as there is no such equivalent in the wix toolset language.
Nov 28 2022
Nov 18 2022
Nov 3 2022
I recently noticed that the old workaround by setting a kategory when it is not visible in the messagelist does not work on a default Outlook 2204 anymore. This raises the priority of this issue.
There must be something special with the message. Can you save the message to a file and use the command line to decrypt it? Is there anything special with it? Is it maybe a binary and not text? Although I tried decrypting random bytes with the notepad and it worked for me. Is the message very large? Anything unusual? Or does it even happen for you when you encrypt a short text to yourself and then decrypt it again?
Oct 27 2022
The issue with rWe06c325a9a29 was that it linked in all breeze icons and nowadays would also link in all breeze-dark icons. Which increased the size of Kleopatra so much that there was no performance gain and the fallbacks were still checked. This might require a fix in Qt / Kiconloader not to use fallbacks and also to only resource up the subset of icons which we actually use and package.
In QGPGME which is used by GpgOL and Kleopatra we have solved this by loading the configuration only once and then reusing it. I see no need to change something in gpgconf here.
Oct 26 2022
Oct 25 2022
I have pushed the patch, but still it did not work for me properly over everything and I had to add --enable-install-gpg-error-config to libgpg-error. This was because of at least the 64 bit build of libassuan-master it picked up gpg-error-config from my host system. I then tried to add --with-gpg-error-prefix to the assuan call but that failed because it only looked for gpg-error-config in this prefix and not for any gpgrt-config and failed immediately with a command not found error.
In that case could you please attach a basic log from selecting an S/MIME Mail with S/MIME disabled? Activatable under GpgOL options / logging
I think there is a mixup here. I believe that you are experiencing https://dev.gnupg.org/T6192 (From 2019) which is a fairly recent regression and was discovered by our internal QA in September. As we did not get reports about this we only gave it low priority.
Test result: --libs ====================: pkg-config gpg-error -L/home/aheinecke/dev/main/lib64 -lgpg-error ====================: gpgrt-config -L/var/example-target/home/aheinecke/dev/main/lib64 -lgpg-error ==================== Test result: --cflags ====================: pkg-config gpg-error -I/home/aheinecke/dev/main/include ====================: gpgrt-config -I/var/example-target/home/aheinecke/dev/main/include ==================== Test result: --cflags --libs ====================: pkg-config gpg-error -I/home/aheinecke/dev/main/include -L/home/aheinecke/dev/main/lib64 -lgpg-error ====================: gpgrt-config -I/var/example-target/home/aheinecke/dev/main/include -L/var/example-target/home/aheinecke/dev/main/lib64 -lgpg-error ==================== Test result: --version ====================: pkg-config gpg-error 1.8.0 ====================: gpgrt-config 1.47-beta4 ====================
Oct 24 2022
Oct 18 2022
Thanks for the report, since you are using it on the command line and it works I assume that trust-model is set to tofu+pgp? Because in the Test code there is no context flag for tofu+pgp trust model.
I tend to close this as a duplicate.
Cool, I will try it out ASAP. You must have read my mind. Only yesterday evening I ran into problems because the current code in src/Makefile.am to symlink the static libs did not work on my new dev system with a lib64 layout and thought that I needed just a patch like this to fix it properly.
We need to understand the usecase here.
Oct 17 2022
Oct 13 2022
Sep 29 2022
With a gcrypt not claiming compliance you should not get the status compliant or not but GnuPG should error out with forbidden.