From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7 StumbleUpon/1.89

Description of problem:
Blank spaces can cause rpm to refuse to import a valid GPG key

Version-Release number of selected component (if applicable):
Verified on rpm-4.2.1-4.4

How reproducible:
Always

Steps to Reproduce:
1. generate a key with gpg --keygen
2. export it with gpg --armor --export KEYID > key.asc
3. verify that rpm accepts it with rpm --import key.asc
4. add a single space in the blank line between the headers and the
actual key
5. verify that rpm rejects it: rpm --import key.asc returns "import
read failed"

Actual Results:  See "Steps to reproduce"

Expected Results:  rpm should strip off unnecessary blanks and accept
the key. Unnecessary blanks are sometimes inserted when the key is
emailed, copy-pasted, etc.

Additional info:
For this specific test case, the relevant code snippet is in
rpmio/rpmpgp.c in function pgpReadPkts

            if (*t != '\n') {
                pstate = 0;
                continue;
            }

i.e. if the empty line between the headers and the key contains just a
newline it is considered valid, otherwise the key is discarded