[Bug 1092270] New: gpg paste problem with GNOME terminal
http://bugzilla.opensuse.org/show_bug.cgi?id=1092270 Bug ID: 1092270 Summary: gpg paste problem with GNOME terminal Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have a GPG key block copied from the browser that can be pasted into "cat
/dev/null" without problem. However when I try to paste it into "gpg", the block looks strange, and gpg refuses to accept it. The key block in question is that from https://handbrake.fr/openpgp.php.
When pasting into cat, the block ends like this:
cat >/dev/null -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBFkQpw8BEADpPeQ2xW4rVObYATTXCWGA4nHmaHkDzWMqrHRXspx80KL2Lv/8 ... TalAuh1G9VxHGQR88NntjQOK =2vLY -----END PGP PUBLIC KEY BLOCK-----^C
When pasting into gpg, the block ends like this:
gpg gpg: Go ahead and type your message ... -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBFkQpw8BEADpPeQ2xW4rVObYATTXCWGA4nHmaHkDzWMqrHRXspx80KL2Lv/8 ... N9R0KA2Tau8RgIr14e9ws1i/NylW7z/CXMtxGiWwegWJxl5ZcVKmG/3e/Nh4Am0PJ TalAuh1G9VxHGQAR88NntjQOK =2vLY -----END PGP PUBLIC KEY BLOCK-----4nHmaHkDzWMqrHRXspx80KL2Lv/8\n
And gpg outputs "gpg: invalid armor header: " -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092270
http://bugzilla.opensuse.org/show_bug.cgi?id=1092270#c1
Andreas Stieger
From the HTML code:
<p style="font-family: Courier New; font-size:10"> -----BEGIN PGP PUBLIC KEY BLOCK-----<br />
mQ[...]<br />
From the text rendering:
-----BEGIN PGP PUBLIC KEY BLOCK----- mQ[...]
2.4.1 ASCII Armor Formats
When PGP encodes data into ASCII Armor, it puts specific headers around the data, so PGP can reconstruct the data at a future time. PGP tries to inform the user what kind of data is encoded in the ASCII armor through the use of the headers.
ASCII Armor is created by concatenating the following data:
- An Armor Headerline, appropriate for the type of data - Armor Headers - A blank line - The ASCII-Armored data [...]
So clearly the online version of the key is rendered in such a way that the blank line is missing. The first line is then interpreted as a header, which results in this expected message. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092270
http://bugzilla.opensuse.org/show_bug.cgi?id=1092270#c2
--- Comment #2 from Ulrich Windl
The data is not formatted correctly.
Thanks for that, your are right! I was so much focused at the end of the block that I didn't have a look at the top. GPG public key block start like this: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQENBD9EdFcBCACvwxlLmzEPUh090rpnCNKDymGJjdoeT1oJ4xczktGk9UXf767H ... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com