Jan 7 2021
Jan 16 2020
Jan 15 2020
You may.. Comments were relevant. Bye.
FWIW, the GTK and QT pinentries do have a qualitybar. However is is only enabled:
Jan 14 2020
In T4809#131931, @werner wrote:
BTW, the qualitybar is not shown by default, only if you configure sme of the extra password checks. We may even remove it completely because it leads to wrong assumption on why a passphrase is required.
@Rycky_Tigg cases 1, 2, and 3 that you document here each show the behavior that i would expect from pinentry-gnome3, given the definition of its Assuan-based API and its use of gcr-prompter. (i'm assuming that in case 3 the user just waited longer than the allowed timeout)
"more specific about what you think is wrong"; From https://bugs.kde.org/show_bug.cgi?id=412569 copied)/pasted:
BTW, the qualitybar is not shown by default, only if you configure sme of the extra password checks. We may even remove it completely because it leads to wrong assumption on why a passphrase is required.
pinentry-gnome uses gcr's gcr_prompt_set_password_new to prompt for a new password, and ignores the SETQUALITYBAR assuan command.
Jan 13 2020
It seems that gnome-keyring-daemon has some incompatible changes which breaks that version of pinentry-gnome. Or GKR has not been setup properly. I'd suggest to use pinentry-gtk until folks with knowledge about Gnome folks have figured out what is going wrong.
Hey. As reference – Complete set of features while run in Windows.
Please describe which features are missing.
Jul 2 2019
I cannot do that because all listed above packages are my own products.
Fedora is not execution test suites in more than 90% of all packages so they are not aware of most of the issues exposed by test suites.
Please focus on possible causes of above tests.
I'm opened on any suggestions to make additional diagnostics.
Thanks. You may want to ask on the mailing list gnupg-users to see whether someone else has had problems building on rawhide. Right now we do not have the time for individual support and thus I unfortunately need to prioritize this bug report down.
Oct 24 2017
GnuPG 1.4 is only for old features. New features are only supported by GnuPG 2.2.
Oct 20 2017
I would suggest to close this as won't fix.
Jul 1 2017
May 23 2017
Apr 11 2017
Please use GnuPG 2 (2.0 or 2.1) for using smartcard/token.
smartcard support in GnuPG 1.4 is way old and only supports shorter key length.
Mar 30 2017
Jan 6 2017
I would suggest to add
gpgconf --launch gpg-agent
GPG_AGENT_INFO="$(gpgconf --list-dirs agent-socket):-1:1"
export GPG_AGENT_INFO
to your startup script. This starts gpg-agent and sets the correct socket name
into the envar.
Nov 30 2016
Oct 6 2016
Aug 16 2016
Thanks for testing.
Aug 14 2016
I've made new container and can't repeat the bug. gpgme
components got updated in Fedora.
Aug 2 2016
Ok, there are no significant patches on top of pygpgme. Note that pygpgme is not really
maintained, and that we neither develop nor support pygpgme. But seeing that dnf is important to
Fedora, let's figure this out.
It would be nice if you could try to reproduce the problem without pygpgme though, just to make a
more minimal test case. I see the exception is thrown during some import. This is how I strace
gnupg to see what ioctls it is issuing:
% strace -eioctl g10/gpg --import ../tests/openpgp/samplekeys/ecc-sample-1-pub.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: key 0BA52DF0BAA59D9C: public key "ec_dsa_dh_256 <openpgp@brainhub.org>" imported
- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=26716, si_uid=1000, si_status=0,
si_utime=0, si_stime=0} ---
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
gpg: Total number processed: 1
gpg: imported: 1
+++ exited with 0 +++
Note that if you try to strace your gpgme-based application, you need to pass '-f' to strace to
follow forks.
I have grepped through gpgme and gnupg, and it looks like gnupg is only doing ioctls to terminals,
so maybe your container setup is doing something funny to terminals. But let's see what the strace
shows.
Jul 29 2016
Here is the info about Fedora patches
https://www.rpmfind.net/linux/RPM/fedora/secondary/devel/rawhide/src/p/pygpgme-0.3-15.fc24.src.html
On Wed, Jul 27, 2016 at 1:24 PM, Justus Winter via BTS
<gnupg@bugs.g10code.com> wrote:
I see that you are using pygpgme, is that correct?If so, which version, and are
there significant patches applied in the Fedora package? And can you please tell
me what version of libgpgme you are using?
Jul 27 2016
Thanks for the report.
I see that you are using pygpgme, is that correct? If so, which version, and are
there significant patches applied in the Fedora package? And can you please tell
me what version of libgpgme you are using?
Let's try to figure out which ioctl fails. Could you try to strace this process?
Nov 19 2015
I'm closing this as Werner think it is a problem with Fedora and the original
reporter hasn't suggested this is not the case.
Nov 11 2015
For the record Rolf Eike Beer still maintains KGpg (I was not aware of this when
i wrote T2048 (aheinecke on Aug 28 2015, 10:54 PM / Roundup))
And he is planning to port it to Qt5.
See: https://mail.kde.org/pipermail/kde-community/2015q3/001651.html
Please leave this issue closed here. This bug either belongs in the Fedora
Bugtracker or in KDE's bugtracker.
Nov 8 2015
On 6 November, there was finally some movement on the 22 July Bug I filed at:
https://bugzilla.redhat.com/show_bug.cgi?id=1245732
Rex Dieter provided the underlying explanation of the KGpg autostart failure on
Fedora 22 (or newer) systems:
He stated:
"Simple reason is that plasma5 doesn't support kde4 apps' use of
X-KDE-Autostart-condition"
Note: Rex is also developing/testing a patch to address this plasma5
shortcoming for Fed 22 systems.
Importantly, and as I had suspected and alluded to, this plasma5 lack of support
explains why the KGpp failure to autostart occured *only* on my Fed 22 systems,
and did not impact any of the other KDE operating systems I use.
I have upgraded all my Fed 22 systems to Fed 23, where the KGpg autostart
currently continues to persist. I have documented the workaround in the Bug
report linked above for anyone impacted. This workaround also works in Fed 23.
Hopefully, this issue will be fully resolved in the next Fedora-approved release
of KGpg.
Nov 6 2015
The main complaint was fixed in 2b27acc and the program was marked as deprecated
in the documentation.
Sep 28 2015
Sep 24 2015
I laughed when I first read aheinecke's comments, at least right up until the
moment the gravity of the 'unmaintained upstream' hit me!
The Bug I filed on 22 July at: https://bugzilla.redhat.com/show_bug.cgi?id=1245732
has gone exactly nowhere, in a hurry, despite being assigned to Ngo Than.
In any event, another Fedora Forum user and I tracked down the root cause ourselves.
I can confirm this KGpg failure to autostart is *NOT* in any way related to GnuPG.
I have already documented how to cause, and how to avoid, this KGpg autostart
failure in this thread: http://forums.fedoraforum.org/showthread.php?t=305604
Hint: If you are interested, read page 2 of ^that thread first, for a summary,
and a reproducible testing procedure.
aheinecke: Kleopatra was, and is, a 'thing' of beauty! ;-3
Sep 3 2015
Based on aheinecke's comments I'm closing this.