commit | 6866b90a30d9779ce1fd3c0bdafbb32553472eb6 | [log] [tgz] |
---|---|---|
author | Davide Pesavento <davidepesa@gmail.com> | Sun Dec 22 23:11:26 2024 -0500 |
committer | Davide Pesavento <davidepesa@gmail.com> | Sun Dec 22 23:11:26 2024 -0500 |
tree | d8111f293c65ee9789c30b02b1e77bd026d8d2a9 | |
parent | 6481e1e245322f157d246dcd03ddfb882b846494 [diff] |
Improve log messages and general code cleanup in CaModule Change-Id: Ie455ec14594e7662800faa887da72574bff73407
The NDN certificate management protocol (NDNCERT) enables automatic certificate management in NDN. In Named Data Networking (NDN), every entity should have a corresponding identity (namespace) and the corresponding certificate for this namespace. Moreover, entities need simple mechanisms to manage sub-identities and their certificates. NDNCERT provides flexible mechanisms to request certificates from a certificate authority (CA) and, as soon as the certificate is obtained, mechanisms to issue and manage certificates in the designated namespace. Note that NDNCERT does not impose any specific trust model or trust anchors. While the primary use case of this protocol is to manage NDN testbed certificates, it can be used with any other set of global and local trust anchors.
See our GitHub wiki for more details.
Please submit any bug reports or feature requests to the NDNCERT issue tracker.
We greatly appreciate contributions to the NDNCERT code base, provided that they are licensed under the GNU GPL version 3 or a compatible license. If you are new to the NDN software community, please read our Contributor's Guide to get started.
NDNCERT is free software distributed under the GNU General Public License version 3. See COPYING.md
for details.