commit | e78fd4d972d0b34711896086ae5eab848b1f2595 | [log] [tgz] |
---|---|---|
author | Tianyuan Yu <tianyuan@cs.ucla.edu> | Wed May 25 13:18:06 2022 -0700 |
committer | Tianyuan Yu <tianyuan@cs.ucla.edu> | Thu May 26 19:04:05 2022 -0700 |
tree | 10a7cd9c65cf384c5d97728abc5dd030f53a3b98 | |
parent | 829aff664105c42408872a9b88536c60acf9660c [diff] |
ca: set Data FreshnessPeriod in CaModule::issueCertificate() Change-Id: I42a169f309e1069965b5f91ed8542a868a77c15b
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.