SNMP community string (length and complexity)

SNMP community string (length and complexity)

SNMP community string (length and complexity)
SNMP community string (length and complexity)
Friday - last edited 12 hours ago
Hardware Version:
Firmware Version:

Hi there,

 

we are usign the Omada Controller running on Linux. Latest version. And that is the issue ;-) Since one of the latest (maybe the latest) versions, we can't set a proper SNMP v1 and/or SNMPv2 community string anymore. We always get this message: Enter a value ranges from 10 to 64 characters. Gemeinschaftszeichenfolge must be a combination of letters, numbers, and special symbols. Symbols `~!@#$%^&*()_-+={}[]:;'|\<>,./ are supported. Gemeinschaftszeichenfolge should not contain consecutive identical characters.

 

Is this on purpose?

We do not want that as we have a bunch of devices and they are added to monitoring systems. Changing the community string is a lot of work.

Besides that: Enforcing complexity rules on SNMO is stupid. If  I want more security I go for SNMPv3.

 

BR
C

  0      
  0      
#1
Options
1 Accepted Solution
Re:SNMP community string (length and complexity)-Solution
12 hours ago - last edited 12 hours ago

  @Honkman 

 

Hello! Thank you for your feedback.  

 

Regarding the new rules for SNMP community strings, this is indeed a security enhancement introduced in the latest version. To improve overall device management security, SNMP v1/v2 community strings must now meet the following complexity requirements:  
- Length between 10 and 64 characters  
- Must include letters, numbers, and supported symbols (e.g., `~!@#$%^&*()_-+={}[]:;'|\<>,./`)  
- No consecutive identical characters  

 

Design Intent Explanation:*
1. Enhanced Security – While SNMPv3 is the more secure option, many legacy devices still rely on v1/v2. Simple community strings (e.g., "public"/"private") are vulnerable to brute-force or sniffing attacks, and the new rules help mitigate these risks.  
2. Alignment with Industry Practices – Similar password complexity requirements have become standard for many network devices (e.g., Cisco, Huawei, and other vendors enforce comparable policies).  

 

 

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:SNMP community string (length and complexity)-Solution
12 hours ago - last edited 12 hours ago

  @Honkman 

 

Hello! Thank you for your feedback.  

 

Regarding the new rules for SNMP community strings, this is indeed a security enhancement introduced in the latest version. To improve overall device management security, SNMP v1/v2 community strings must now meet the following complexity requirements:  
- Length between 10 and 64 characters  
- Must include letters, numbers, and supported symbols (e.g., `~!@#$%^&*()_-+={}[]:;'|\<>,./`)  
- No consecutive identical characters  

 

Design Intent Explanation:*
1. Enhanced Security – While SNMPv3 is the more secure option, many legacy devices still rely on v1/v2. Simple community strings (e.g., "public"/"private") are vulnerable to brute-force or sniffing attacks, and the new rules help mitigate these risks.  
2. Alignment with Industry Practices – Similar password complexity requirements have become standard for many network devices (e.g., Cisco, Huawei, and other vendors enforce comparable policies).  

 

 

Recommended Solution
  0  
  0  
#2
Options