I might have changed the caller (GpgME++) but what convinced me that the change in core is better is that op_keylist_next sets the return value to NULL on error.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Mar 29 2018
Mar 29 2018
I changed the interaction so that user can specify RSA or ECC, then when it's for ECC, specifying curve.
• gniibe committed rGa1515b3bbc10: g10: Support key attribute change at --card-edit/generate. (authored by • gniibe).
g10: Support key attribute change at --card-edit/generate.
• gniibe committed rG02d7bb819ff4: g10: check_pin_for_key_operation should be just before genkey. (authored by • gniibe).
g10: check_pin_for_key_operation should be just before genkey.
It looks like something wrong happened in scdaemon. Could you please try with following? .gnupg/scdaemon.conf
BenM committed rM75a1a1c33efe: Merge branch 'ben/howto-update-02' of ssh+git://playfair.gnupg.org/git/gpgme (authored by BenM).
Merge branch 'ben/howto-update-02' of ssh+git://playfair.gnupg.org/git/gpgme
example: revoke UID
docs: python bindings howto
Since I don't have macOS environment and Yubikey 4 (I only have old Yubikey), I hesitated to claim this ticket. But it is me who should take this one.
example: key signing
doc: python bindings howto
Mar 28 2018
Mar 28 2018
example: add user ID
docs python bindings howto
• werner committed rM3345a17dda22: json: Remove the "message" object thingy again. (authored by • werner).
json: Remove the "message" object thingy again.
I also stumbled on this problem in the past. However, I did not changed it because I feared to break callers which expect that the passed key object is not changed on error. This may happen in a loop where you test for an ambiguous key and don't save zway the first retrieved key. In the error case (i.e. not ambiguous) this would dump the good key object.
json: Make native messaging work.
jukivili committed rC0de2191a07d6: aarch64: Enable building the aarch64 cipher assembly for windows (authored by Martin Storsjö <martin@martin.st>).
aarch64: Enable building the aarch64 cipher assembly for windows
jukivili committed rC36e916fc332e: aarch64: Fix assembling chacha20-aarch64.S with clang/llvm (authored by Martin Storsjö <martin@martin.st>).
aarch64: Fix assembling chacha20-aarch64.S with clang/llvm
jukivili committed rCec0a2f25c0f6: aarch64: mpi: Fix building the mpi aarch64 assembly for windows (authored by Martin Storsjö <martin@martin.st>).
aarch64: mpi: Fix building the mpi aarch64 assembly for windows
jukivili committed rC4e1b628f4926: aarch64: camellia: Only use the lower 32 bit of an int parameter (authored by Martin Storsjö <martin@martin.st>).
aarch64: camellia: Only use the lower 32 bit of an int parameter
jukivili committed rCed41d6d6fb45: random: Don't assume that _WIN64 implies x86_64 (authored by Martin Storsjö <martin@martin.st>).
random: Don't assume that _WIN64 implies x86_64
Register DCO for Martin Storsjö
JJworx added a comment to T3857: Gpg4win 3.0.3 GpgOL crashes with old mails already verified by GPG4win 2.x.
Mr. Heinecke, to make sure, please note that despite the thread title these crashes happened with 3.1.0. beta 38. It would be sad if you do all of the tests and checks with 3.0.3
Use clearsign in padwidget
• gniibe committed rGe610d51f0de1: g10: Change ask_curve so that it can be used outside. (authored by • gniibe).
g10: Change ask_curve so that it can be used outside.
• aheinecke added a comment to T3857: Gpg4win 3.0.3 GpgOL crashes with old mails already verified by GPG4win 2.x.
Apologies for not replying to your mail directly. I've marked it in my INBOX to do the test with 3.0.3 first but have not gotten around to it.
• aheinecke committed rOf79f3379aba5: Fix S/MIME encryption with latest Exchange 2016 (authored by • aheinecke).
Fix S/MIME encryption with latest Exchange 2016
JJworx added a comment to T3857: Gpg4win 3.0.3 GpgOL crashes with old mails already verified by GPG4win 2.x.
Funny thing, it worked for some time, now it's reproducably crashing again. This might be the better log file.
JJworx added a comment to T3857: Gpg4win 3.0.3 GpgOL crashes with old mails already verified by GPG4win 2.x.
So, this is tested with 3.1.0 beta 38, reproducable crash
JJworx added a comment to T3857: Gpg4win 3.0.3 GpgOL crashes with old mails already verified by GPG4win 2.x.
I answered by mail in this fashion:
Mar 27 2018
Mar 27 2018
The severe delay caused by check-trustdb continues to cause problems elsewhere in the ecosystem. It would be great to try to address this so that GnuPG was more responsive for routine tasks like importing a single key.
Syssou added a comment to T3867: [DIRMNGR] Key server should be tried if passed with --keyserver, regardless of the "dead" mark.
Thank you for your answer ! :)
• werner triaged T3867: [DIRMNGR] Key server should be tried if passed with --keyserver, regardless of the "dead" mark as Normal priority.
You can do a
• aheinecke committed rKLEOPATRA1da1cbae4dd1: Merge branch 'Applications/18.04' (authored by • aheinecke).
Merge branch 'Applications/18.04'
• aheinecke committed rKLEOPATRA2dc42351b6f5: Fix raising on second call if session restored (authored by • aheinecke).
Fix raising on second call if session restored
• aheinecke committed rKLEOPATRA0fbba7b7734e: Fix crash and error handling in print seckey (authored by • aheinecke).
Fix crash and error handling in print seckey
• aheinecke changed the status of T3861: GpgOL: Crash in new Resolver when removing identity filter, a subtask of T3864: Gpg4win-3.1.0 Release blocker, from Open to Testing.
• aheinecke changed the status of T3861: GpgOL: Crash in new Resolver when removing identity filter from Open to Testing.
• aheinecke changed the status of T3861: GpgOL: Crash in new Resolver when removing identity filter, a subtask of T3742: Gpg4win 3.1.0, from Open to Testing.
• aheinecke added a comment to T2069: Passphrase prompts for each subkey, but not clear which dialog belongs to which subkey.
Was reported to me again in the context of paperkey export / print secret key in Kleopatra.
• aheinecke changed the status of T3865: Kleopatra crashes again in Gpg4win 3.1.0 beta 38 from Open to Testing.
Got it. This was a bug that was around for ages but only started to occur in the verificationresult when we started in 3.0 to show the KeyID / Options for the unknown certificates.
• aheinecke changed the status of T3865: Kleopatra crashes again in Gpg4win 3.1.0 beta 38, a subtask of T3864: Gpg4win-3.1.0 Release blocker, from Open to Testing.
• aheinecke committed rM7c220e387d51: core: Initialize key return value in gpgme_get_key (authored by • aheinecke).
core: Initialize key return value in gpgme_get_key
• werner committed rGd4dc4245bf02: Merge branch 'STABLE-BRANCH-2-2' into master (authored by • werner).
Merge branch 'STABLE-BRANCH-2-2' into master
• gniibe committed rG96918346beec: agent,scd: Use pointer to represent HANDLE. (authored by • gniibe).
agent,scd: Use pointer to represent HANDLE.
• werner committed rG02dce8c0cc57: agent: Make the request origin a part of the cache items. (authored by • werner).
agent: Make the request origin a part of the cache items.
tests: Exclude tests for Windows build.
• aheinecke added a subtask for T3742: Gpg4win 3.1.0: T3839: Trustdb corrupted after fresh install of Gpg4win.
• aheinecke added a parent task for T3839: Trustdb corrupted after fresh install of Gpg4win: T3742: Gpg4win 3.1.0.
In my opinion we should assume that c:/ was meant.
doc: Fix previous commit.
doc: python bindings howto
example: key creation
script: temp homedir config
• gniibe committed rEefc4769339d4: doc: Support cross compilation for yat2m. (authored by • gniibe).
doc: Support cross compilation for yat2m.
Mar 26 2018
Mar 26 2018
Under Wine it does not crash but returning an empty string is not a good idea in any case. The question is what to do with "c:". The usual meaning is to use the current directory of drive C. But that does not make much sense. Should we simply assume that "c:/" was meant?
• werner changed the status of T3839: Trustdb corrupted after fresh install of Gpg4win from Open to Testing.
I pushed two fixes. One which hopefully avoids the corrupted trustdbs and a second one to repair a version-record-only trustdb (the example file).
• werner committed rGeb68c2d3d1b0: gpg: Auto-fix a broken trustdb with just the version record. (authored by • werner).
gpg: Auto-fix a broken trustdb with just the version record.
• werner committed rG403aa70c52e5: gpg: Return better error codes in case of a too short trustdb. (authored by • werner).
gpg: Return better error codes in case of a too short trustdb.
gpg: Pass CTRL arg to get_trusthashrec.
• aheinecke changed the status of T3863: GpgOL: 3.1.0 Beta might send unencrypted mail even if crypto was selcted, a subtask of T3742: Gpg4win 3.1.0, from Open to Testing.
• aheinecke changed the status of T3863: GpgOL: 3.1.0 Beta might send unencrypted mail even if crypto was selcted, a subtask of T3864: Gpg4win-3.1.0 Release blocker, from Open to Testing.
• aheinecke changed the status of T3863: GpgOL: 3.1.0 Beta might send unencrypted mail even if crypto was selcted from Open to Testing.
rO4c5eed308829 fixes this.
• aheinecke added a parent task for T3865: Kleopatra crashes again in Gpg4win 3.1.0 beta 38: T3864: Gpg4win-3.1.0 Release blocker.
Again, thanks for your time testing it again.
• aheinecke committed rO4c5eed308829: Fix sending PGP/Inline synchronously (authored by • aheinecke).
Fix sending PGP/Inline synchronously
• aheinecke committed rO2f05d4ed802a: s/should_inline_crypt/do_pgp_inline/ (authored by • aheinecke).
s/should_inline_crypt/do_pgp_inline/
• aheinecke committed rO97ee667a0c24: s/is_inline_response/async_crypt_disabled/ (authored by • aheinecke).
s/is_inline_response/async_crypt_disabled/
• aheinecke committed rO9d10ff22928a: Add safety check to prevent unencrypted send (authored by • aheinecke).
Add safety check to prevent unencrypted send
• aheinecke committed rOe67c03636889: Add bug error if body_to_body failed (authored by • aheinecke).
Add bug error if body_to_body failed
• aheinecke committed rO71334bacf780: Handle encrypt / sign on empty message (authored by • aheinecke).
Handle encrypt / sign on empty message
• aheinecke committed rOe62b003f83bc: Check for error on encrypt_sign_start (authored by • aheinecke).
Check for error on encrypt_sign_start
Add gpgol_bug helper function
• aheinecke committed rOb2727a00c025: Abort if mail has no body and no attachments (authored by • aheinecke).
Abort if mail has no body and no attachments
• aheinecke committed rOa80c7502c45b: Don't carry around inline crypt state twice (authored by • aheinecke).
Don't carry around inline crypt state twice
• aheinecke committed rO52c80aec174d: Document how encryption is done in do_crypt (authored by • aheinecke).
Document how encryption is done in do_crypt
- it is reproducible
- Kleopatra crashes at the end of the verification of a signature
- it is a openPGP signature
- please see first picture
- I have only openPGP certificates in Kleopatra
• werner committed rG456a3a8e93ea: gpg: Fix trustdb updates without lock held. (authored by • werner).
gpg: Fix trustdb updates without lock held.
• werner committed rG5f00531463eb: gpg: Disable unused code parts in tdbio.c (authored by • werner).
gpg: Disable unused code parts in tdbio.c
My test case is to import my pubkey and then run:
• werner closed T2689: trustdb error when lower 32-bits of ultimately trusted fingerprint are zero as Wontfix.
We don't support v3 keys at all.
Thanks for trying out the beta and your report.
Fix was released with GPGME 1.10.0
• aheinecke added subtasks for T3864: Gpg4win-3.1.0 Release blocker: T3863: GpgOL: 3.1.0 Beta might send unencrypted mail even if crypto was selcted, T3861: GpgOL: Crash in new Resolver when removing identity filter, T3853: GpgOL: S/MIME + Exchange 2016 Can lead to 550 5.6.0 M2MCVT.StorageError.Exeption .