Prepare for a cleaner docker build.
autogen.sh: Do not use --enable-maintainer-mode
Mote stuff for a cleaner docker build.
Improve signing and fix file names in the nsis scripts.
Update autogen.sh and add option --with-playground
Simplify PO build rules for our NSIS-only useto support VPATH.
Minor improvements for build.sh.
More changes to the new docker based build system.
Improve test for duplicate packages.
Do not use gnupg.net as server
Fix last commit - of course it is the builddir.
Finally link the created installer to an artifacts directory.
Update gpgme to version 1.24.1
Use GnuPG 2.5.2 and current GUI tarballs.
Update NSIS for the changed poppler dll name.
Extend the versioninfo.txt file.
New option --force for build.sh
Introduce new Makefile variables
Actually put the commit-id into the versioninfo.txt
New option to build.sh do run download.sh
Initial set of changes to build MSIs out of source.
Update gpg-authcode-sign.sh from GnuPG.
Add a way to run commands from docker on the host
Some cleanups for building MSIs
Update to gnupg-2.5.3-beta6
Update to gnupg 2.5.3, gpgol 2.5.15, and current kleo packages.
One more fix to build.sh for Friday night.
Update to KDE frameworks 6.9
Remove bad patch due to the updated KDE frameworks.
Use the RUNCMD mechanism also for osslsigncode.
Add some more files to .gitignore
Fix make dist which did not anymore work due to VPATH build.
Add missing script fpr make dist.
Include more build info into the MSIs
msi: Fix the list of GUIDs
Install the versioninfo.txt also for MSI.
msi: Now uses gnupg-vsd as standard home directory.
msi: Tweaks for better 64 bit support.
msi: Fix quoting og the Win64 property value.
msi: Some reformatting for easier reading of make-msi.pl
msi: Minor changes and a small fix to gen-gnupg.sh
msi: Installing to the 64 bit folder does now work.
Merge branch 'wk-temporary' into gpg4win-5-branch
Update gpgme to regular 1.24.2 release.
• werner updated the task description for
T7440: Release GPGME 1.24.1.
Won't be fixed for the creation thing.
Fix typo in a macro reference.
This is the old code from gnupg-2.0/agent/gpg-agent.c:
inotify is already used used on Linux to check for a lost homedir. The once-in-a-minute check should be the same as with the other daemons and has proved to be very useful. The whole thing has been discussed over and over again a long time ago and - as with other system daemon - we agreed on scheduling at the full second.
gpg: Store Link attributes for composite keys.
aheinecke: Yeah, but I did quite some changes to build.sh for a real out-of-source build (w/o copying files)
gpg: New option --disable-pqc-encryption.
gpgscm: Fix possible segv in the process functions.
kbx: Fix for building without keyboxd.
gpgscm: Fix for gcc < 4.5
gpg: Fix --quick-add-key for Weierstrass ECC with usage given.
No real world bug reports for this and thus a backport has a small risk of a regression.
• werner renamed
T7505: SSH agent failing "agent refused operation" due to Bitwarden from
SSH agent failing "agent refused operation" to
SSH agent failing "agent refused operation" due to Bitwarden.
Thanks for that info. I tag it as FAQ and change the subject in case someone searches for such a problem.
The compliance mode likes 4880 or 2440 are only here for backward compatibility in case that is needed. New keys shall always be generated using the current default algorithms. Note that a mode like de-vs is different in that it is used to comply with certain regulatory demands and not as a backward compatibility hack.
gpg: Fix --quick-add-key for Weierstrass ECC with usage given.
• werner committed
rG8ae8f12e5359: po: Update to po/pt.po (authored by Daniel Cerqueira <dan.git@lispclub.com>).
po: Update to po/pt.po
Fixed in master and the new gpgme-1.24-branch. Thus this fix will be in 2.0.0 and 1.24.2
Sorry, this will not be fixed for 2.4.
Update copyright notices.
• werner renamed
• gloria-disabled from
gloria to
gloria-disabled.
core: Fix regression for RSA in gpgme_pubkey_algo_string.
I am pretty sure this was my fault: rM62b6c1f16 is the culprit.
@gouttegd: Good idea. I did this with the above patches.
FWIW, If a fix is really required for gnupg this will be done for gnupg26 and not for gnupg22. However, it is mostly a kleopatra issue.
gpg: Simplify the compliance settings.
gpg: Base compliance "de-vs" now on "gnupg" and not on "openpgp".
doc: Record that gpg policy compliance options are last-one-wins
gpg: --compliance={pgp7, pgp8} also now restore default options
gpg: --compliance=gnupg restores default for policy-affected options
• werner committed
rG54a8770aeb20: gpg: --compliance=rfc2440 does not require cross-certification (authored by Daniel Kahn Gillmor via Gnupg-devel <gnupg-devel@gnupg.org>).
gpg: --compliance=rfc2440 does not require cross-certification
Thanks. I applied all 4 patches to master and did one additional change to get --allow-old-cipher-algos straight.
I never tested the WSL stuff with gpg-agent but I use the standard OpenSSH based ssh server on Windows on a daily base. It is actually part of our release build chain. A recent problem I encountered was fixed in master with rG2469dc5aae and should be backported to 2.4. Might be related to your problem but I need to read your detailed bug report more closely.
That gpg seems to be some other or patched software than the one from gnupg:
gpgsm: Allow unattended PKCS#12 export without passphrase.
gpgsm: Allow CSR generation with an unprotected key.
Signs from the past or is this due to fixed Observer URI I did this morning in this repo?
gpgconf assumes that there is only one of the daemons. In fact it can only work with one and that is the one daemon which listens on the socket. all daemon's do a self-check by trying to connect to themself and terminate if they realize that they are not anymore the owner of the socket. As long as a daemon is started by a gnupg component a file system lock is taken to avoid duplicate launching. However it a daemon is stared by other means this could lead to a race.