I have a test encrypted file on my computer that when I run
gpg(2) --verify message.txt.asc
gpg: Signature made Tue Mar 3 21:16:41 2015 PST using RSA key ID ******* gpg: Good signature from "John Doe <firstname.lastname@example.org>" gpg: WARNING: not a detached signature; file 'message.txt' was NOT verified!
And if I run
gpg(2) -d message.txt.asc
It does not prompt for the passphrase on my private key and yet still decrypts the gpg message. The other random .gpg/.asc files I have require that I decrypt them with a passphrase and --verify does not work.
What is the deal with the original file such that --verify works and I can decrypt without a passphrase? Is there a gpg command that analyzes a given file so I can gain context as to why it is not password protected? I thought it might be a detached signature (albeit without the default .sig extension) but there is a message in it as well. I do not have a gpg-agent running fwiw.