<filename>.<ext>.asc: This should be an ascii encrypted file (option: --armor) of the <filename>.<ext> file.
It although can be an ascii encoded key file.
The *.sig Files
<filename>.<ext>.sig: This should be an ascii encoded signature file corresponding to <filename>.<ext>.
The *.key Files
<filename>.key: This should be an ascii encrypted key (option: --armor)
Support for an alternate homedir/key ring
When VSCode is opened in a folder with (file:pubring.kbxOR file:pubring.gpg) AND (folder:private-keys-v1.dOR file:secring.gpg) included, then the --homedir parameter is used in every command of this VSCode instance.
Additionally the extension supports a workspace configuration to set the path for the keyring. Consequently there is a order for the keyring location:
Use local keyring in workspace, when detected
When not 1. , then check for GnuPG.homedir configuration
When not 2. , then use GnuPG default keyring location
Using several VSCode instances at the same time is not recommended, because the gpg-agent is running in the background for one session. Otherwise you have to kill the session. TIP: Change folder in one instance, because gpg-agent will be killed automatically.
Use Check GnuPG command to see the current used home directory.
Use pure GnuPG installation (gnupg-w32-<version>_<date>.exe)