F21-ND: Yes
Rationale
For the selected producer-to-consumer role, ECDSA Data validation binds the producer key to the content. ndn-cxx passes the validated Data to the success callback; its KeyLocator identifies the key under the configured trust model. This credits authenticated item authorship, as for Nostr, not a live producer, serving cache or authenticated consumer.
Assessment method
Pinned primary-source inspection and selected-profile inference; no execution
Source context
ndn-cxx 0.9.0 Data validation state
Outstanding qualification
Use a validator policy requiring the selected ECDSA producer key under local trust anchors. Success callbacks alone are insufficient: bypassValidation also invokes them. Verify altered content/key/signature rejection; resolve and retain the validated key binding, avoid treating an unchecked KeyLocator or a mutable key name as proof, and keep accepted Data immutable. No execution or freshness guarantee.
Public sources
- https://raw.githubusercontent.com/named-data/ndn-cxx/ndn-cxx-0.9.0/ndn-cxx/security/validation-state.cpp
- https://docs.named-data.net/NDN-packet-spec/0.3/signature.html
- https://docs.named-data.net/ndn-cxx/0.9.0/doxygen/classndn_1_1Data.html
- https://raw.githubusercontent.com/named-data/ndn-cxx/ndn-cxx-0.9.0/ndn-cxx/security/validator.hpp