[Bug 958891] New: gnupg in Tumbleweed 20151209 - finds ambiguity where there is none
http://bugzilla.opensuse.org/show_bug.cgi?id=958891 Bug ID: 958891 Summary: gnupg in Tumbleweed 20151209 - finds ambiguity where there is none Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: nwr10cst-oslnx@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.14.10 Safari/537.21 Build Identifier: I noticed the problem, because I could not open KDEWallet (uses GPG encryption). Here's some output: --- cut here --- % gpg --list-keys rickert gpg: key specification 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' is ambiguous gpg: (check argument of option '--encrypt-to') gpg: 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' matches at least: gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1 gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1 --- cut here --- That's bogus ambiguity. Maybe it is finding the same key twice, perhaps because an earlier gpg2 version insisted on copying keys to another place. I've flagged this as "critical" since I lose access to kdewallet. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c4
--- Comment #4 from Neil Rickert
Reporter, kindly test the next build from security:privacy/gpg2 when it appears in an hour or so
Sorry I'm late with this. Yesterday, I was dealing with a hard drive failure. I have tested that new build. When I try the command: gpg --list-keys rickert my session seems to hang. Running "top" in another terminal shows that "gpg" appears to be looping (100% cpu time). I'll also mention that the problem discussed upstream (link in c#1) appears to be a different problem. That was concerned with ambiguity between an active key and an expired key. The problem that I reported is different. It is showing ambiguity between a key and itself. It is finding ambiguity where there is none. See my initial report. I'll add that, after noticing the loop, I did a full switch to the security:privacy repo, just in case the looping was due to conflicting software. After that switch, it still loops. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c5
Andreas Stieger
I have tested that new build. When I try the command:
gpg --list-keys rickert
my session seems to hang. Running "top" in another terminal shows that "gpg" appears to be looping (100% cpu time).
I revoked the SR as at the least the bug reference would be incorrect, and potentially there is a loop problem.
I'll also mention that the problem discussed upstream (link in c#1) appears to be a different problem.
Ah, different Neils.
That was concerned with ambiguity between an active key and an expired key. The problem that I reported is different. It is showing ambiguity between a key and itself. It is finding ambiguity where there is none. See my initial report.
I'll add that, after noticing the loop, I did a full switch to the security:privacy repo, just in case the looping was due to conflicting software. After that switch, it still loops.
Have you reported this upstream? The reason is that if it is not openSUSE specific we would like to involve upstream as much as possible. As this seems to be a public keyring issue, can I please ask you to attach (a minimum version) of the public keyring demonstrating the problem? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c6
--- Comment #6 from Neil Rickert
encrypt-to 0x46B1EFE1
So it seems that the problem is in the parsing of options. It is seeing my attempt to be unambiguous with "encrypt-to" as an ambiguity. If you want, I can reinstall the updated version from security:/privacy and check whether that now works. I have not yet reported upstream. I'll do that later today (Chicago time). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c7
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c8
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=958891
http://bugzilla.opensuse.org/show_bug.cgi?id=958891#c9
Andreas Stieger
We can revisit this bug when upstream fixes or addresses the above, usually through a bugfix release. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com