[AGENT++] How to block V1 or V2 access to the VACM tables

[Jochen Katz]

Hi Fedja,

> So basically I would need to call addNewView twice (at least) in order to
> block the access to some of the branches and allow access to the others?
> Right?

yes.

> Does this example looks correct in this case:
>         vacm->addNewView("v1v2RestrictedView", "1.3.6", "", view_included,
> storageType_nonVolatile);
> 
>         vacm->addNewView("v1v2RestrictedView", "1.3.6.1.6", "",
> view_excluded, storageType_nonVolatile);
> 
> Would this give me the access to everything below the "1.3.6" except for the
> "1.3.6.1.6"?

Yes, always the longest matching subtree "wins", so for example
1.3.6.1.6.1.1 is within 1.3.6.1.6 and this is exluded.

Regards,
  Jochen