This was done by Tobias.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Tue, Apr 9
Thu, Mar 28
For the reference, for now i just did the dummy install in the Fedora spec file:
Tobias, if you find some time, can you please see how this can be done.
Mar 18 2024
Thank you!
See T7046 for the release info. Note that the mentioned fix for kwallet already landed.
Noteworthy changes in version 1.2.1 (2022-08-24)
Mar 14 2024
Mar 8 2024
I still need to land the fix for the kwallet problem, but that can be done first thing monday so nothing that really blocks a release
I had a look at the open tasks for pinentry(-qt) and didn't see anything that we should address before doing a release. @werner?
Mar 7 2024
I should say: I can ship a snapshot in Gentoo if that's okay, but I'd prefer not to.
Feb 21 2024
Lowering priority because it does not seem to be a popular issue.
Feb 2 2024
This is still an issue.
Jan 29 2024
Jan 10 2024
Thanks for the contribution, sorry this took us a while to get to. I've merged your changes to the pinentry repo now.
Dec 28 2023
Dec 27 2023
Dec 12 2023
Nov 27 2023
Still no response after more than 2 years?
Nov 10 2023
Thanks for the reviews. And your beautiful work, by which I also mean the response to the feedback and how you managed to work with phabricator. I will commit the patch on your behalf then later.
I think that tried_password_cache in the documentation is wrong. The text:
and @code{tried_password_cache} is false
Thanks for the update.
Nov 9 2023
In general, the changes look good.
Oct 6 2023
Sep 21 2023
Sep 20 2023
I'm using the standard pinentry provided by Homebrew: https://formulae.brew.sh/formula/pinentry#default
gpg -v -K does not require a pinentry. You can check this by adding debug-pinentry and log-file /some/file to the gpg-agent.conf - you should not see any pinentry invocation.
Aug 21 2023
We should not backport this to 2.2; better update to the current stable version (2.4)
Using Ubuntu, it's GnuPG 2.2 (which doesn't have the fix of T4585). Without the fix, killing gpg (by CTRL-C) causes problematic situation where pinentry remains asking.
That's because gpg-agent and pinentry don't know the frontend side has been killed. T4585 introduced a watching thread into gpg-agent, so that it can correctly detect lost of frontend.
Aug 18 2023
Hi @gniibe - thanks for your fix.
Pushed the fix for SIGINT handling of pinentry-tty and pinentry-curses by: rPa6f63fe37dbf: tty,curses: Upon SIGINT, let pinentry exit gracefully.
This fix should improve the situation.
Thank you for the report.
I found a bug in pinentry-curses and pinentry-tty for handling SIGINT. I am going to fix this.
Aug 14 2023
In T6085#162923, @ikloecker wrote:In T6085#162918, @ebo wrote:well, when creating openPGP keys with kleopatra I did not see any hints. I do not think that the issue would be vaild for password based encryption. There the common usecase is autogeneration, anyway
Autogeneration isn't viable if an organization has stupid password constraints that the autogenerated passwords do not satisfy. In particular, the autogenerated passwords do not contain any non-alphanumeric characters, but many password policies require such a character.
Aug 10 2023
Jul 24 2023
Jun 1 2023
I have set T6513: Kleopatra: Require GpgME 1.21 as blocker for this issue because, in my opinion, showing the above mentioned "Operation fully cancelled" error message is from a user perspective worse than showing multiple password prompts.
May 31 2023
Setting close_button when the user rejected the pin entry (by pressing the close button, the Cancel button or Esc) causes fully canceled. Unfortunately, Kleopatra (and in fact GpgME::Error) has no idea that fully canceled should be treated as canceled and not as error. Therefore, Kleopatra shows an ugly error message:
An error occurred while trying to change the passphrase for [...]:
Operation fully cancelled
May 17 2023
I see the problem: The Qt Pinentry does not implement the BUTTON_INFO status and thus we don't get a fully canceled error back (gpg-agent maps the cancel error to fully-cancel if the close button was used). Should be easy to fix in pinentry (set pinentry->close_button in the close eventhandler).
May 12 2023
Thank you, your suggestion inspired me to experiment a bit further and I found the problem - I needed in fact to delete the line from my ssh config, no idea why:
Match host * exec "gpg-connect-agent UPDATESTARTUPTTY /bye"
Now I update startup tty only on terminal start and it seems to be working. Still a bit strange.
On a terminal, please invoke:
$ gpg-connect-agent UPDATESTARTUPTTY /bye
May 4 2023
Apr 10 2023
Apr 5 2023
Mar 28 2023
Actually this is about improving an error message.
Mar 21 2023
ok, ticket for the new issue is T6418
Mar 20 2023
Not sure why this was assigned to Andre.
In T5543#168681, @ebo wrote:How about emptying both fields in case of mismatch and start from the beginning?
This exact step works. But if you misspell the repeat its unintuitive again what you should do.
closing with reference to external testing
Turned out to be a bit come complicated. I hope that I did not break any of the other pinentries:
rP8ab1682e80a2b4185ee9ef66cbb44340245966fc
Mar 2 2023
Added SETQUALITYBAR support with some fixes for glitches when an error string was set. Wide characters seem to work OK.
Feb 27 2023
Added curses-repeat branch which needs testing for wide chars and other stuff in case i missed something
Jan 19 2023
Nov 14 2022
Nov 3 2022
Oct 28 2022
This is now ready for testing.
Sep 26 2022
pinentry-emacs is obsolete. It's for older Emacs (<= 25, IIUC) which had lisp/pinentry.el.
For Emacs 26 and newer, you can simply use epa-pinentry-mode having the value of loopback.
Sep 22 2022
Sep 14 2022
works now
Sep 9 2022
Thanks for your help @gniibe and apologies for wasting your time. It looks like this is an issue with ncurses on musl systems and I'll pursue it there. I have a patch to their configure which works & fixes building pinentry.
I've reported it on bug-ncurses@ to get some insight: https://marc.info/?l=ncurses-bug&m=166268018624805&w=2.
Mysteriously, I get nothing:
$ pkg-config --cflags nurses
Sep 8 2022
Could you please check what pkg-config --cflags ncurses returns?
In my environment (of Debian), it returns:
It looks like there was a problem similar to this a while ago: https://dev.gnupg.org/T2320 where it turned out for unicode ncurses builds, a specific header had to be included, but that workaround seems to have been removed from pinentry since.
Sep 6 2022
In T6085#162918, @ebo wrote:well, when creating openPGP keys with kleopatra I did not see any hints. I do not think that the issue would be vaild for password based encryption. There the common usecase is autogeneration, anyway
In T6085#162921, @aheinecke wrote:@ikloecker yes as mentioned in my response the current hints are only for symmetric.
@ikloecker yes as mentioned in my response the current hints are only for symmetric.
well, when creating openPGP keys with kleopatra I did not see any hints. I do not think that the issue would be vaild for password based encryption. There the common usecase is autogeneration, anyway
The long hint is "hidden" in the tooltip of the short hint.
And the issue for which @ebo opened this ticket is in my opinion that you have to fail first before you see the hint.
Sep 5 2022
I think there was a misunderstanding here. We already set .pinentry.constraints.hint.long and .pinentry.constraints.hint.short in GnuPG-VSD but firstly they are only about symmetric.
And the issue for which @ebo opened this ticket is in my opinion that you have to fail first before you see the hint.