experiments/clixon
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* INSTALLFLAGS added with default value -s(strip).

Browse source 
* For debug do: CFLAGS=-g INSTALLFLAGS= ./configure
This commit is contained in:
Olof hagsand 2018-04-30 12:06:19 +02:00
parent 1ac57dedaf
commit 7532fdde77
15 changed files with 63 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README_NACM.md
View file

@ -7,15 +7,15 @@ The support is as follows:
* There is a yang config variable `CLICON_NACM_MODE` to set whether NACM is disabled, uses internal(embedded) NACM configuration, or external configuration. (See yang/clixon-config.yang)
* If the mode is internal, NACM configurations is expected to be in the regular configuration, managed by regular candidate/runing/commit procedures. This mode may have some problems with bootstrapping.
* If the mode is `external`, the `CLICON_NACM_FILE` yang config variable contains the name of a separate configuration file containing the NACM configurations. After changes in this file, the backend needs to be restarted.
* The [example](example/README.md) contains a http basic auth and a NACM backend callback for state variable.
* The [example](example/README.md) contains a http basic auth and a NACM backend callback for mandatory state variables.
* There are two [tests](test/README.md) using internal and external NACM config
* The backend provides a limited NACM support (when enabled) decscribed below
* The backend provides a limited NACM support (when enabled) described below
NACM functionality
==================
NACM is implemented in the backend and the access checks are made at a
single point: in from_client_msg() when an internal netconf RPC has
NACM is implemented in the backend and a single access check is made
in from_client_msg() when an internal netconf RPC has
just been received and decoded. The code is in nacm_access().
The functionality is as follows: