Why does PGP complain about checking signatures every so often?
• Version 2.3a introduced the “pkcs_compat” option, allowing the format of signatures to change slightly to make them more compatible with industry standards. (See question 2.1.) MIT PGP, because it uses the RSAREF library, is unable to understand the old signature format, so it therefore ignores the signature and warns you that it is doing so. • This problem comes up mostly with old key signatures. If your key contains such old signatures, try to get those people who signed your key to resign it. • If an old signature is still vitally important to check, get a non-MIT version of PGP to check it with, such as ViaCrypt’s. Go to Table of Contents • 2.4. Why does it take so long to encrypt/decrypt messages? • This problem can arise when you have placed the entire public key ring from one of the servers into the pubring.pgp file. PGP may have to search through several thousand keys to find the one that it is after. The solution to this dilemma is to maintain 2 public key rings. The first r
Version 2.3a introduced the “pkcs_compat” option, allowing the format of signatures to change slightly to make them more compatible with industry standards. MIT PGP, because it uses the RSAREF library, is unable to understand the old signature format, so it therefore ignores the signature and warns you that it is doing so. This problem comes up mostly with old key signatures. If your key contains such old signatures, try to get those people who signed your key to resign it with a newer version of PGP. If an old signature is still vitally important to check, get a non-MIT version of PGP to check it with, such as ViaCrypt’s.
