commit | 63900d5a619dfc317eb773d0646c31c7e366858c | [log] [tgz] |
---|---|---|
author | tylerliu <tylersiqi@163.com> | Wed Sep 30 03:01:18 2020 -0700 |
committer | tylerliu <tylersiqi@163.com> | Wed Sep 30 03:01:18 2020 -0700 |
tree | e704c0442461deab7d1813be5b9d5c565b5c76be | |
parent | 8e170d64c34448d20fdcc55c533bdf90ca0850b8 [diff] |
variable renaming and sqlite code optimization Change-Id: Ida2c854f87c528820945bc6246678d87543b1ed9
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 GPL 3.0+ or a compatible license (see below). If you are new to the NDN software community, please read the Contributor's Guide to get started.
NDNCERT is an open source project licensed under the GPL version 3. See COPYING.md
for more information.