| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The get_next implementation of vacmAccessTable did not return all
available table data. Instead, it only returned the first column for
each row, and all columns for the last row available.
Fix the get_next implementation of vacmAccessTable to return all table
entries.
|
|
|
|
There are problems with the handling of vacmAccessTableStatus that cause
some SNMP test suites to report errors.
Most notably, errorneous set operations frequently cause "genErr" errors
to be returned which usually is a sign for bad coding. These "genErr"
errors are usually caused by badmatch exceptions coming from
{ok, Row} = snmpa_vacm:get_row(RowIndex)
if the row does not exist.
This patch fixes the badmatch errors and adjusts the semantic of the
RowStatus handling in that table to be compliant with the RowStatus
textual description of SNPMv2-TC MIB.
|
|
Improve error handling while reading agent config files.
OTP-9943
|
|
Removed the use synchronization mechanism during vacm table dumping.
This could not be placed in the master agent since it was sometimes
used from the master agent. Also is was credated and used from the
top agent supervisor, befor the master agent process was created...
OTP-9851
|
|
changes where made to the VACM security-to-group, access and
view-tree-family tables.
OTP-9367
|
|
|
|
snmp_view_based_acm_mib:snmp_view_based_acm_mib:reconfigure/1 on a
running node, the table vacmAccessTable was not properly cleaned.
This meant that if some entries in the vacm.conf file was removed
(compared to the "current" config), while others where modified
and/or added, the removed entrie(s) would still exist in the
vacmAccessTable table.
Merge branch 'bmk/snmp/vacmAccessTable_cleanup/OTP-8981' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/vsn.mk
|
|
is_set_ok and set operation(s), all values of the
vacmAccessSecurityModel column was incorrectly translated
to *any*.
Merge branch 'bmk/snmp/verify_vacm_security_model/OTP-8980' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/test/snmp_appup_test.erl
lib/snmp/vsn.mk
|
|
|
|
Also added config file for usm.
And more sed'ing...
|
|
|
|
|
|
the vacmAccessTable whas not properly cleaned.
This means that if some entries in the vacm.conf file was removed
compared to the "current" config), while others where modified
and/or added, the removed entrie(s) would still exist in the vacmAccessTable.
|
|
is_set_ok and set opteration(s), all values of the
vacmAccessSecurityModel column was incorrectly
translated to *any*.
|
|
|
|
opteration(s), all values of the vacmAccessSecurityModel column was
incorrectly translated to "any".
|
|
vacmViewTreeFamilyTable.
There is still vacmAccessTable and vacmContextTable.
|
|
|
|
|
