What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
CC | astieger@suse.com | |
Resolution | --- | INVALID |
Assignee | bnc-team-screening@forge.provo.novell.com | astieger@suse.com |
The data is not formatted correctly. >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[...] >From https://tools.ietf.org/html/rfc1991#section-2.4.1 > 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.