correct gpg/pgp signatures (why reject a .changes file?)
Hello,
recently, I was trying to upload a package of mine to a server and
got this message in return:
____________________________________________________________________
PGP/GnuPG signature check failed on sumo_1.0-5.2_i386.changes
ERROR: Header line added to ASCII armor: "Hash: SHA1"
ASCII armor corrupted.
Error: Transport armor stripping failed for file /tmp/pgptemp.$00
For a usage summary, type: pgp -h
For more detailed help, consult the PGP User's Guide.
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Warning: unsafe permissions on file
"/home/ftp/ftpfau/ftplinux/DQueued/./debian-keyring.gpg"
gpg: Signature made Fri Nov 22 04:09:55 2002 MET using DSA key ID
A690AB48
gpg: Can't check signature: public key not found
(Exit status 2)
sumo_1.0-5.2_i386.changes has bad PGP/GnuPG signature!
Removing sumo_1.0-5.2_i386.changes, but keeping its associated files
for now.
____________________________________________________________________
Is it because I'm simply not allowed to do that (as not being a
debian developer) or is there something I can do about it?
Thanks,
andrej
--
echo ${girl_name} > /etc/dumpdates
Reply to: