blob: 11b11d0cd560ffdc4f17168eed1a53edb964817d [file] [log] [blame]
Chengyu Fanb25835b2015-04-28 17:09:35 -06001; The catalog section contains settings of catalog
2general
3{
4 ; Set the catalog prefix, so that adapters can extend it as their own prefix
5 ; e.g., suppose that the catalog has the prefix "ndn:/cmip5", so QueryAdapter has the prefix
6 ; "ndn:/cmip5/catalog/query" and "ndn:/cmip5/catalog/query-results",
7 ; PublishAdapter has the prefix "ndn:/cmip5/catalog/publish"
8
9 prefix /catalog/myUniqueName
10}
11
12; The queryAdapter section contains settings of queryAdapter
13queryAdapter
14{
15 ; signingId ndn:/cmip5/test/query/identity; Set the Identity that signs data that respond
16 ; the queries
17
18 ; The database section contains settings of database for QueryAdapter
19 database
20 {
21 dbServer 127.0.0.1 ; Specify the database server
22 dbName testdb ; Specify the database name
23 dbUser testuser1 ; Specify the database user name
24 dbPasswd test123 ; Specify the associated password for the dbUser
25 }
26}
27
28; The publishAdapter section contains settings of publishAdapter
29publishAdapter
30{
31 ; ; Set the identity that signs published data
32 ; signingId ndn:/cmip5/test/publish/identity
33
Chengyu Fanc7b87ad2015-07-09 16:44:37 -060034 ; ; The security section contains the rules for the adapter to verify the
Chengyu Fanb25835b2015-04-28 17:09:35 -060035 ; ; published files indeed come from a valid publisher.
Chengyu Fanc7b87ad2015-07-09 16:44:37 -060036 ; security
Chengyu Fanb25835b2015-04-28 17:09:35 -060037 ; {
Chengyu Fanc7b87ad2015-07-09 16:44:37 -060038 ; rule
39 ; {
40 ; id "NDN Hierarchy Test Rule"
41 ; for data ; rule for Data (to validate NDN certificates)
42 ; filter
43 ; {
44 ; type name ; condition on data name
45 ; regex ^(<>*)$
46 ; }
47 ; checker
48 ; {
49 ; type hierarchical ; the certificate name of the signing key and
50 ; ; the data name must follow the hierarchical model
51 ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
52 ; }
53 ; }
54 ; trust-anchor
55 ; {
56 ; type file
57 ; file-name /directory/to/the/root.ndncert ; the file name, by default this file should be
58 ; ; in same folder as this config file.
59 ; }
Chengyu Fanb25835b2015-04-28 17:09:35 -060060 ; }
61
62 ; The database section contains settings of database
63 ; The user in publishAdapter may differ from the one in queryAdapter, to provide different
64 ; access control
65 database
66 {
67 dbServer 127.0.0.1 ; Specify the database server
68 dbName testdb ; Specify the database name
69 dbUser testuser2 ; Specify the database user name
70 dbPasswd test123 ; Specify the associated password for the dbUser
71 }
72
73 ; The sync section contains settings of ChronoSync
74 sync
75 {
76 ; Set the prefix for sync messages, default 'ndn:/ndn/broadcast'
77 prefix ndn:/ndn/broadcast
78
79 ; ; The sync_data_security section contains the rules that are required for ChronoSync nodes to
80 ; ; verify published data by other ChronoSync nodes.
81 ; ; The ChronoSync validator will be disabled when sync_data_security section is missing.
82 ; sync_data_security
83 ; {
84 ; ; ; This section defines the trust model for the ChronoSync data Management. It consists of
85 ; ; ; rules and trust-anchors, which are briefly defined in this file. Multiple rules can be
86 ; ; ; included
87 ; ; rule
88 ; ; {
89 ; ; id "ChronoSync Update Messages Rule"
90 ; ; for data ; rule for Data (to validate NDN certificates)
91 ; ; filter
92 ; ; {
93 ; ; type name ; condition on data name
94 ; ; regex ^[^<KEY>]*<KEY><>*<ksk-.*><ID-CERT><>$
95 ; ; }
96 ; ; checker
97 ; ; {
98 ; ; type hierarchical ; the certificate name of the signing key and
99 ; ; ; the data name must follow the hierarchical model
100 ; ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
101 ; ; }
102 ; ; }
103 ; ; trust-anchor
104 ; ; {
105 ; ; type file
106 ; ; file-name keys/default.ndncert ; the file name, by default this file should be placed in
107 ; ; ; the same folder as this config file.
108 ; ; }
109 ; }
110 }
111}