Skip to content

jam-awake/gpg-verify-bug

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

gpg-verify-bug

Files that demonstrate an issue with gpg verify.

Keys were generated using the ProtonMail/go-crypto library, not GPG. This might be affected by ProtonMail/go-crypto#184 (i.e. https://dev.gnupg.org/T4579).

Steps to reproduce:

  1. Import all keys in keys directory: gpg --import keys/*.asc
  2. Run ./debug.sh <keyId> using the table below (output of ./print-key-ids.sh)
Key Id Bit Length Key File
806663D3E04590E7 2048 keys/2048-bit-length-key.pub.asc
7EB71AABF1C4A864 3072 keys/3072-bit-length-key.pub.asc
B793E0C25EABE63E 4096 keys/4096-bit-length-key.pub.asc

Imported keys can be deleted via

for i in keys/*.pub.asc; do
  keyId=$(gpg --show-keys --keyid-format=long --with-colons "$i" | grep '^pub' | cut -d: -f5)
  echo "Deleting key ${keyId}"
  gpg --delete-secret-keys "${keyId}"
  gpg --delete-keys "${keyId}"
done

About

Files that demonstrate an issue with `gpg verify`

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages