Oops, sorry, mischecked dates.
These fixes landed master some time ago, but not available in v0.16.0
(targeted for the v0.17.0).
On 29.04.2022 15:58, Nickolay Olshevsky wrote:
Hi,
It depends on what is called 'chokes' and which behaviour is expected.
RNP since v0.16.0 handles such cases in the following way: API returns
information about the valid/invalid/unknown signatures and CLI
interprets that, displaying information to the user. However, CLI
still returns error code if at least one signature is invalid or
unknown. Probably that's why it is marked in red in the
interoperability test suite.
On 29.04.2022 03:28, Daniel Kahn Gillmor wrote:
The Ask
=======
Could every implementer please take a look at the sample messages
offered in the interop test suite, run them against their tooling, and
propose and identify a patch if the current tooling chokes? If you
think the test suite is wrong, and your client handles the situation
fine despite looking problematic in the test suite, that would also be
good news. Please report!
Regards,
--dkg
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp
--
Best regards,
Nickolay Olshevsky
o(_dot_)nickolay(_at_)gmail(_dot_)com
OpenPGP_0xB82E690843E5C423.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp