We currently only support binary '.sig' gpg signatures.
We should also support ASCII-armored '.asc' gpg signatures as they are equally
valid.
This will require a config option to be added to control the extension which is
added to a filename to determine the signature filename and will require the
gpg signature verification code to be tested with ASCII-armored signatures. If
the current code doesn't support these signatures it will need extending to do
so.
Original issue reported on code.google.com by paul.betafive on 8 May 2014 at 2:59
Original issue reported on code.google.com by
paul.betafive
on 8 May 2014 at 2:59