Originally Posted by DuckieTigger
Now all you need to fix is your gpg signatures for the kual1.0 and kual2.0. No need to reappload whole tar.gz or .zip, just add the signatures (those should be less than 1kb). Knc1 and me came to the conclusion, that you might have accidentally encrypted them rather than sign them.
Yup. noticed that. --detached-sign was what I should have used IIRC. used --sign.
C:\Program Files\GNU\GnuPG>"C:\Program Files\GNU\GnuPG\gpg2.exe" --import ./"two
gpg: C:/Users/user/AppData/Roaming/gnupg/trustdb.gpg: trustdb created
gpg: key DB626CBF: public key "twobob (twobob) <firstname.lastname@example.org>" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
C:\Program Files\GNU\GnuPG>"C:\Program Files\GNU\GnuPG\gpg2.exe" --verify "C:\Program Files\GNU\GnuPG\KindleLauncher-1.0.azw2.gpg"
gpg: Signature made 02/04/13 02:52:20 GMT Standard Time using RSA key ID DB626CBF
gpg: Good signature from "twobob (twobob) <email@example.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2F74 78B5 6C50 401D 55CF 2AC7 65C4 73B2 DB62 6CBF
Will roll into the 0.3.2 update. Appreciated.