- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 30 2019
Apr 29 2019
Since 2.1 the standard use of gpg-agent is to have it started on demand by the components which require it. The use of
"gpg-agent --daemon /bin/sh " should be used for debugging only.
Request for key | Thu, 7 Jun 2018 11:48 +0200 |
Reply from us | Thu, 7 Jun 2018 19:05 +0200 |
Report date | Fri, 8 Jun 2018 09:14 +0200 |
Fix committed | Fri, 8 Jun 2018 11:09 +0200 |
Announcement and release | Fri, 8 Jun 2018 15:41 +0200 |
With the last release we improved the handling of sent mails, again.
Without more reports and without the info needed to analyze this further I'm lowering the priority.
I've applied your patch with an additional comment to our master branch. Thanks!
Apr 28 2019
Email did not get through (should use plain old text email), so I prepared patch myself. See D477, https://dev.gnupg.org/D477
Apr 27 2019
@dkg, thanks for the feedback. I read [doc/HACKING](https://www.gnupg.org/faq/HACKING.html) and revised the commit message so that it contains ChangeLog entries and a marker line before my description. I compared my new message to prior log entries and they seem to match now. Is this appropriate? If so, I will revise my other commits in the same manner.
Thanks for this work, @matheusmoreira ! I personally think a reusable function in common/ would be preferable, but it's probably up to @werner to decide what's best here.
Apr 26 2019
@dkg Sure! I thought I was supposed to email the patches to the development mailing list. [I've uploaded my delete-secret-subkey branch to GitHub.](https://github.com/matheusmoreira/gnupg/tree/delete-secret-subkey) You can see a comparison here. I'll describe my changes.
I think this can go to wontfix for now. Inline PGP inside of S/MIME,.. well that is not good.
I am pretty sure that this had the same underlying cause as T4332 which was fixed with Gpg4win-3.1.7
With the new keytreeview since 45f27eb3940617a8daff9b218b066ac482b9515d this is resolved.
This was fixed with c591cb20edfe70de29d343a6ce13c4b710bdeba6
This was resolved in a different way.
This was fixed.
Closing this as invalid until the info requested in the last comment is provided.
@werner This issue also applies to GPA. Looking at the edit key interface I can't see how we can handle this. Am I overlooking something or do we just loose the error information / is it not emited by gnupg?
nice, i'm glad to hear you've got something working, @matheusmoreira ! if you can point to your branch, or send patches here so that other folks can review, that would be great.
Ha, fancy that, I just added the method of using gpg-connect-agent to our new handbook, I agree that having a --delete-secret-subkeys command would be incredibly handy here.
I managed to make it work on my branch: gpg --delete-secret-key FPR! deletes just that key and no others! I will prepare a patch for this specific change and then try to implement the --delete-secret-subkeys command.
Apr 25 2019
Apr 24 2019
Screenshots were sent by e-mail to you. Thunderbird and Outlook screenshots are different.
I am quite sure! Because, (1) I opened both mails on another computer were Thunderbird is installed. Both signatures can be verified on both accounts with Thunderbird. Both mails were sent out with PGP signature by HPI Identity Leak Checker Team, so the signature generally works fine. (2) If I save the key which is as asc file in the attachment (in the account which does not work) on computer and perform then a check of the signature, I receive a input / output error in Kleopatra. I will make some screenshots, and I´ll send it by mail to you.
Are you sure that it is related to accounts and not to the mail? E.g. if you copy that mail from the second account to the first account, is it verified then?
Thank you very much!
makes sense to me. I've applied your patch so it will be part of the next release.
Apr 23 2019
FWIW, with 4a130bbc2c2f4be6e8c6357512a943f435ade28f I fixed a similar report by @syscomet but lacking a test case this was a blind flight ("This patch is not tested but a good guess."). Thanks for tracking it down.
That might have been a regression since one of the Phrabricator updates (we need to apply out own patches each time).
Minor
For reference our downstream tracker of this is https://bugs.gentoo.org/683254 including patches
Apr 22 2019
The patch touches src/Makefile.am. You need to run automake to update src/Makefile.in.
In the patch, it uses pkg_namespace variable to have prefix 'errnos_'.
Apr 21 2019
This bug makes it impossible to use gpg-agent as ssh-agent for keys generated from gnupg.
(How should I understand what passphrase should I enter?)
The only way is to load them with ssh-add.
Apr 20 2019
Apr 19 2019
Paul Wouters writes to me:
I just noticed that dirmngr(8)'s documentation for its --keyserver option says:
Note that even sending a HUP to dirmngr, when it is in this autodetection mode that observed tor at the start, is insufficient to have it re-run the autodetection. You have to explicitly terminate dirmngr to get it to unlearn the autodetected presence of Tor. This is subtly hinted at in dirmngr(8), but no justification is given for it.
I think I identified the bug. A fix is pushed.