commit | c2fedec406705fd716c3d00db047144c450cc375 | [log] [tgz] |
---|---|---|
author | Davide Pesavento <davidepesa@gmail.com> | Tue Sep 19 16:30:30 2023 -0400 |
committer | Davide Pesavento <davidepesa@gmail.com> | Tue Sep 19 16:30:30 2023 -0400 |
tree | b6b86e3f676bf8be11cca69abb41b3d42135a487 | |
parent | a3dbb94232715b86b90954d77a94b8334c43b7aa [diff] |
build: switch source archive to xz compression Change-Id: Id48d81e5b91aad8b2b69925e2c8ed3506e7e17d9
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.