We have the problem again that revoked UIDs are not ignored by the validity check in isDeVsAndValid.
I wonder if we should make a function that combines isKeyDeVs and uidsHaveFullValidity.
As we skip revoked Uids I wonder if we should not also skip invalid UserIds, because we would never use them.
| rLIBKLEO Libkleo | |||
| rLIBKLEO93ea0bde0ad6 Remove duplicate keyValidity helper | |||
| rLIBKLEOe0e4b2bff211 Make the key resolver reject not fully valid keys in compliance mode | |||
| rLIBKLEO8400035eedd5 Simplify checking keys for compliance with de-vs mode | |||
| rLIBKLEO257c62365032 Move Formatting::isKeyDeVs to compliance | |||
| rLIBKLEO222614e5450c Move Formatting::uidsHaveFullValidity to keyhelpers | |||
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAc4c9e6fbd089 Use new helper function | |||
| rKLEOPATRA1d70e822f9ea Use new keyIsCompliant helper to unify compliance check | |||
We are now using the new helper DeVSCompliance::keyIsCompliant everywhere where previously isKeyDeVs and uidsHaveFullValidity were used or should have been used (as in SignEncryptWidget::isDeVsAndValid).
works, a key with a revoked uid is accepted as VS-NfD compliant, VS-Desktop-3.1.27.0-beta44