Fix issue #28: SNMPv2c does not work anymore (ErrNoPermission)
- Introduction of SnmpV3Only Configuration:
A new SecurityConfig configuration option, SnmpV3Only, has been added.
This setting instructs the server to accept SNMP version 3 (SNMPv3) requests
exclusively. This addition is a response to the request made in issue #23,
aiming to provide enhanced security by leveraging SNMPv3's advanced features.
- Code Improvements and Bug Fix for Issue #28:
The contributions from @adenis78 and @ConsoleTVs have been refined and
incorporated to resolve the issue where SNMPv2c was not functioning correctly.
- Defensive Rechecking of Configuration and Community Handling:
Enhanced validation checks have been implemented to ensure robust error
handling and response mechanisms. In scenarios where the specified community
is not found within the subagent configuration, and there's an absence of a
SecurityConfig.NoSecurity setting, the server will now refrain from responding.
- Utilization of
NoSecurityfor Compatibility and Testing:
The SecurityConfig.NoSecurity configuration has been introduced
to facilitate bypassing certain security checks.
