[Bug 1028867] New: gpg 2.1.19 breaks tools with sudden warning message
http://bugzilla.suse.com/show_bug.cgi?id=1028867 Bug ID: 1028867 Summary: gpg 2.1.19 breaks tools with sudden warning message Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team@suse.de Reporter: werner@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Currently password-store does not build in Tumbleweed, that is the new gpg cause a warning message which break the test suite do to this line gpg: WARNING: no command supplied. Trying to guess what you mean ... compare with current build result of password-store in project security:privacy. Also with upstream report https://bugs.gnupg.org/gnupg/msg9873 the problem in the test suite of password-store is a superfluous line ... on Leap 42.2 the test suite results e.g. gpg -v --no-secmem-warning --no-permission-warning --list-only --keyid-format long tests/trash\ directory.t0300-reencryption.sh/test-store//folder/cred1.gpg gpg: public key is BEDE59896B2B2DF9 gpg: public key is F4D1428776173888 where as on Tumbleweed this becomes gpg2 -v --list-only --keyid-format long tests/trash\ directory.t0300-reencryption.sh/test-store//folder/cred1.gpg gpg: WARNING: no command supplied. Trying to guess what you mean ... gpg: public key is BEDE59896B2B2DF9 gpg: public key is F4D1428776173888 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1028867
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c1
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c2
Andreas Stieger
Currently password-store does not build in Tumbleweed
Actually it does, SR#477543 is not even in. I think you mean security:privacy. (In reply to Dr. Werner Fink from comment #1)
what is the reason to break an already existing API?
Take it easy, you make it sound as if this was deliberate? That is kind of what staging is for. And frankly I would claim that gpg2 is a little further down in the rings than password-store. Thanks for the references, will be checked out. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c3
Andreas Stieger
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c4
--- Comment #4 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c5
--- Comment #5 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c6
Andreas Stieger
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c7
--- Comment #7 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c8
--- Comment #8 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c9
Andreas Stieger
(In reply to Andreas Stieger from comment #6)
--decrypt
is simply wrong as the tests d onot decrypt here, only list the public keys
https://www.gnupg.org/documentation/manuals/gnupg/GPG-Esoteric-Options.html --list-only Changes the behaviour of some commands. This is like --dry-run but different in some cases. The semantic of this option may be extended in the future. Currently it only skips the actual decryption pass and therefore enables a fast listing of the encryption keys. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c10
--- Comment #10 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c11
--- Comment #11 from Bernhard Wiedemann
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c12
--- Comment #12 from Andreas Stieger
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c13
Dr. Werner Fink
Way to go for casually glancing over the NOT "simply wrong".
Does this mean I should switch back to parsing the information messages about the public keys written by gpg 2.1 to stderr for --decrypt ... or what is wrong with my approach of using the public keys written on stdout for -list-packets -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c15
--- Comment #15 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1028867
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1028867
http://bugzilla.suse.com/show_bug.cgi?id=1028867#c16
--- Comment #16 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1028867
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com