FedoraUmbrella
ActivePublic

Members

  • This project does not have any members.

Watchers

  • This project does not have any watchers.

Recent Activity

Jan 16 2020

Rycky_Tigg added a comment to T4809: Non-operational functions and missing feature.

Reported.

Jan 16 2020, 12:38 PM · Fedora, pinentry, Bug Report
werner closed T4809: Non-operational functions and missing feature as Resolved.
Jan 16 2020, 8:50 AM · Fedora, pinentry, Bug Report

Jan 15 2020

Rycky_Tigg added a comment to T4809: Non-operational functions and missing feature.

You may.. Comments were relevant. Bye.

Jan 15 2020, 2:42 PM · Fedora, pinentry, Bug Report
werner added a comment to T4809: Non-operational functions and missing feature.

FWIW, the GTK and QT pinentries do have a qualitybar. However is is only enabled:

Jan 15 2020, 9:39 AM · Fedora, pinentry, Bug Report

Jan 14 2020

dkg added a comment to T4809: Non-operational functions and missing feature.

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.

Jan 14 2020, 3:30 PM · Fedora, pinentry, Bug Report
dkg added a comment to T4809: Non-operational functions and missing feature.

@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)

Jan 14 2020, 3:29 PM · Fedora, pinentry, Bug Report
Rycky_Tigg added a comment to T4809: Non-operational functions and missing feature.

"more specific about what you think is wrong"; From https://bugs.kde.org/show_bug.cgi?id=412569 copied)/pasted:

Jan 14 2020, 11:34 AM · Fedora, pinentry, Bug Report
werner added a comment to T4809: Non-operational functions and missing feature.

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.

Jan 14 2020, 7:34 AM · Fedora, pinentry, Bug Report
dkg added a comment to T4809: Non-operational functions and missing feature.

pinentry-gnome uses gcr's gcr_prompt_set_password_new to prompt for a new password, and ignores the SETQUALITYBAR assuan command.

Jan 14 2020, 12:12 AM · Fedora, pinentry, Bug Report

Jan 13 2020

werner added a comment to T4809: Non-operational functions and missing feature.

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.

Jan 13 2020, 7:42 PM · Fedora, pinentry, Bug Report
Rycky_Tigg added a comment to T4809: Non-operational functions and missing feature.

Hey. As reference – Complete set of features while run in Windows.

Jan 13 2020, 6:32 PM · Fedora, pinentry, Bug Report
werner added a comment to T4809: Non-operational functions and missing feature.

Please describe which features are missing.

Jan 13 2020, 4:53 PM · Fedora, pinentry, Bug Report
Rycky_Tigg created T4809: Non-operational functions and missing feature.
Jan 13 2020, 3:22 PM · Fedora, pinentry, Bug Report

Jul 2 2019

kloczek added a comment to T4602: 2.2.16: test suite fails.

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.

Jul 2 2019, 4:02 PM · Fedora, gnupg, Bug Report
werner triaged T4602: 2.2.16: test suite fails as Low priority.

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.

Jul 2 2019, 3:43 PM · Fedora, gnupg, Bug Report

Oct 24 2017

gniibe closed T2738: gpg crashes when attempting to write a key to a card as Wontfix.

GnuPG 1.4 is only for old features. New features are only supported by GnuPG 2.2.

Oct 24 2017, 2:21 AM · Fedora, Bug Report, gnupg (gpg14)

Oct 20 2017

werner added a comment to T2738: gpg crashes when attempting to write a key to a card.

I would suggest to close this as won't fix.

Oct 20 2017, 12:56 PM · Fedora, Bug Report, gnupg (gpg14)

Jul 1 2017

marcus closed T1963: ldap keyserver communication error as Invalid.
Jul 1 2017, 1:54 PM · gnupg (gpg14), Fedora, Bug Report, gnupg

May 23 2017

marcus changed the status of T2426: gpgme - Inappropriate ioctl for device from Invalid to Resolved.
May 23 2017, 9:38 AM · Python, Fedora, Bug Report, gpgme
marcus renamed T2426: gpgme - Inappropriate ioctl for device from NATIONAL SECURITY. FEDERAL OFFENSE 12-20yrs FEDERAL PRISON to gpgme - Inappropriate ioctl for device.
May 23 2017, 9:38 AM · Python, Fedora, Bug Report, gpgme

Apr 11 2017

gniibe removed a project from T2738: gpg crashes when attempting to write a key to a card: gnupg.

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.

Apr 11 2017, 3:25 AM · Fedora, Bug Report, gnupg (gpg14)

Mar 30 2017

admin created Fedora.
Mar 30 2017, 6:42 PM

Jan 6 2017

werner closed T1986: gpg-1 should fallback to ~/.gnupg/S.gpg-agent as Resolved.
Jan 6 2017, 6:16 PM · gnupg, Fedora, Feature Request
werner added a comment to T1986: gpg-1 should fallback to ~/.gnupg/S.gpg-agent.

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.

Jan 6 2017, 6:16 PM · gnupg, Fedora, Feature Request

Nov 30 2016

gniibe claimed T2738: gpg crashes when attempting to write a key to a card.
Nov 30 2016, 3:12 AM · Fedora, Bug Report, gnupg (gpg14)

Oct 6 2016

baptistemm added projects to T2738: gpg crashes when attempting to write a key to a card: gnupg (gpg14), gnupg, Bug Report, Fedora.
Oct 6 2016, 4:15 AM · Fedora, Bug Report, gnupg (gpg14)

Aug 16 2016

werner added a comment to T2426: gpgme - Inappropriate ioctl for device.

Thanks for testing.

Aug 16 2016, 7:36 PM · Python, Fedora, Bug Report, gpgme
werner closed T2426: gpgme - Inappropriate ioctl for device as Resolved.
Aug 16 2016, 7:36 PM · Python, Fedora, Bug Report, gpgme

Aug 14 2016

techtonik added a comment to T2426: gpgme - Inappropriate ioctl for device.

I've made new container and can't repeat the bug. gpgme
components got updated in Fedora.

Aug 14 2016, 5:59 PM · Python, Fedora, Bug Report, gpgme

Aug 2 2016

justus added a comment to T2426: gpgme - Inappropriate ioctl for device.

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.

Aug 2 2016, 2:06 PM · Python, Fedora, Bug Report, gpgme

Jul 29 2016

techtonik added a comment to T2426: gpgme - Inappropriate ioctl for device.

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

Jul 29 2016, 3:26 PM · Python, Fedora, Bug Report, gpgme
techtonik added a comment to T2426: gpgme - Inappropriate ioctl for device.

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 29 2016, 3:11 PM · Python, Fedora, Bug Report, gpgme

Jul 27 2016

justus added a comment to T2426: gpgme - Inappropriate ioctl for device.

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?

Jul 27 2016, 12:24 PM · Python, Fedora, Bug Report, gpgme
justus claimed T2426: gpgme - Inappropriate ioctl for device.
Jul 27 2016, 12:24 PM · Python, Fedora, Bug Report, gpgme
techtonik added projects to T2426: gpgme - Inappropriate ioctl for device: Python, Fedora, Bug Report, gpgme.
Jul 27 2016, 11:01 AM · Python, Fedora, Bug Report, gpgme

Nov 19 2015

neal added a comment to T1963: ldap keyserver communication error.

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 19 2015, 9:41 AM · gnupg (gpg14), Fedora, Bug Report, gnupg

Nov 11 2015

aheinecke closed T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected as Resolved.
Nov 11 2015, 3:28 PM · Not A Bug, Fedora, Bug Report, gnupg
aheinecke added a comment to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected.

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 11 2015, 3:28 PM · Not A Bug, Fedora, Bug Report, gnupg

Nov 8 2015

SlipperyCow reopened T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected as "Open".
Nov 8 2015, 5:09 AM · Not A Bug, Fedora, Bug Report, gnupg
SlipperyCow added a comment to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected.

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 8 2015, 5:09 AM · Not A Bug, Fedora, Bug Report, gnupg

Nov 6 2015

neal added a comment to T1210: gpgkey2ssh aborting when run without parameters.

The main complaint was fixed in 2b27acc and the program was marked as deprecated
in the documentation.

Nov 6 2015, 12:32 PM · Fedora, Feature Request
neal closed T1210: gpgkey2ssh aborting when run without parameters as Resolved.
Nov 6 2015, 12:32 PM · Fedora, Feature Request

Sep 28 2015

werner closed T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected as Resolved.
Sep 28 2015, 11:14 AM · Not A Bug, Fedora, Bug Report, gnupg

Sep 24 2015

SlipperyCow added a comment to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected.

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 24 2015, 5:45 PM · Not A Bug, Fedora, Bug Report, gnupg
SlipperyCow reopened T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected as "Open".
Sep 24 2015, 1:12 PM · Not A Bug, Fedora, Bug Report, gnupg

Sep 3 2015

neal removed a project from T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected: Stalled.
Sep 3 2015, 10:41 AM · Not A Bug, Fedora, Bug Report, gnupg
neal closed T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected as Resolved.
Sep 3 2015, 10:41 AM · Not A Bug, Fedora, Bug Report, gnupg
neal added a comment to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected.

Based on aheinecke's comments I'm closing this.

Sep 3 2015, 10:41 AM · Not A Bug, Fedora, Bug Report, gnupg

Aug 28 2015

aheinecke added a project to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected: Not A Bug.
Aug 28 2015, 10:54 PM · Not A Bug, Fedora, Bug Report, gnupg
aheinecke added a comment to T2048: KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected.

Kgpg is unmaintained upstream (meaning KDE) Afaik it does not work with gnupg 2.1

We (talking as a kdepim developer here) are currently in the process of removing
libkgpg dependencies in the hope to remove Kgpg altogether. You should use
Kleopatra and nag the Kleopatra developers (me) about features of KGpgp you will
miss in Kleopatra.

This bug has nothing to do with Gpg and should be filed on bugs.kde.org against
kgpg (but as I said it's unmaintained so you probably should not bother)

Aug 28 2015, 10:54 PM · Not A Bug, Fedora, Bug Report, gnupg