I believe this allows APT to request a safe minimum RSA length from gpgv for verification purposes, and then we could even run gpgv a 2nd time without the flag and print a diagnostic for an orderly transition to at least 2048R.
sorry about that, too quick to send :(
Control: severity -1 important Bumping this. 1024R keys are becoming increasingly unsafe, and this will eventually become release critical for trixie because we shouldn't ship it with trust for those keys. And APT is not capable of checking the key size itself because gpg status fd doesn't expose it - that'd be an alternative solution.
OK the option does not do what it said back then. Logs are below; tl,dr is: 1. Without de-vs compliance setting, it is ignored silently 2. With de-vs compliance setting it is still a good signature 3. Only way to notice it is to also set --require-compliance For APT we want to just ban sub-2048R keys, possibly sub-3072R keys (apparently 2048R is no longer considered safe enough for some draft standards).