403Webshell
Server IP : 121.121.20.254  /  Your IP : 216.73.217.51
Web Server : Microsoft-IIS/10.0
System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64
User : IUSR ( 0)
PHP Version : 8.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  C:/usr/etc/snmp/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : C:/usr/etc/snmp/snmpd.conf.example
# This is a an example only to assist with basic SNMPv3 configuration. Please do not use these example pass phrases, etc.

# 1. Create USM user:
# createUser <username> [<authentication algorithm: MD5|SHA> <authentication pass phrase> [<privacy algorithm: DES|AES> [<privacy pass phrase>]]]
# Important hints:
# - To use the same password for authentication and privacy the privacy pass phrase can be skipped
# - USM does not define privacy without authentication
# - SNMPv3 pass phrases must be at least 8 characters long
# For more information see http://www.net-snmp.org/docs/man/snmpd.conf.html
# Examples:
# createUser usmuser1 MD5 user1p@s$w0rd
# -> New USM user usmuser1 that uses MD5 for authentication with the defined pass phrase
# createUser usmuser2 SHA user2p@s$w0rd AES
# -> New USM user usmuser2 that uses SHA for authentication with the defined pass phrase and SHA for encryption with the same pass phrase

# 2. Define access control and privilege level:
# <access: rouser|rwuser> <username> <privilege level: noAuth,authNoPriv,authPriv> [<mibtree restriction>] 
# For more information see http://www.net-snmp.org/docs/man/snmpd.conf.html
# Examples:
# rouser usmuser1 authNoPriv							
# -> usmuser1 has read-only permission without any MIB tree restriction. Authentication is required but traffic is not encrypted
# rwuser usmuser2 authPriv 1.3.6.1.4.1.231.2.10.2.2.10
# -> usmuser2 has read-write permission on the ServerView Agents SC2 MIB tree only. Authentication is required and traffic is encrypted

# 3. Define traps:
# A defined USM user can be used to send traps to SNMPv3 capable trap handlers. 
# The mandatory engine ID uniquely identifies each SNMP Agent (trap sender) and can be found in the persistent snmpd.conf file (<installdir>\snmp\persist\snmpd.conf)
# The defined user and the unique engine IDs of all SNMP Agents have to be configured in the trap destinations snmptrapd.conf file, see example in the snmptrapd.conf
# However there's a possibility to use a fake engine ID to reduce effort for trap configuration. This is less secure! 
# This example uses 0x0102030405 as the fake engine ID like the example on http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html
# For more information see http://www.net-snmp.org/docs/man/snmptrapd.conf.html
# Examples:
# trapsess -v 3 -l authNoPriv -u usmuser1 -a MD5 -A user1p@s$w0rd -e 0x0102030405 192.168.1.1:162
# -> Traps are sent to destination 192.168.1.1:162 using the user usmuser1 with authentication using the fake engine ID. 
#	 To use the real engine ID replace the fake engine ID with the one from the persistent file mentioned above

# After the configuration is done, the Net-SNMP Agent service has to be restarted. The configuration will be updated in the persistent snmpd.conf file with hashed pass phrases.
# It's recommended to delete this snmpd.conf file afterwards to keep the pass phrases safe.


# ATTENTION:
# ServerView Agents currently use SNMPv1 internally, thus a minimum SNMPv1 configuration - restricted to localhost - is required for the ServerView Agents to work properly.
#
# The community name defined in the valid communities of the Windows builtin SNMP service has to be configured here. 
# Please make sure that there is only one valid community defined for the builtin windows SNMP service. This community needs READ ONLY rights.
# You may need to install the Windows Feature SNMP Tools to be able to configure the Windows builtin SNMP service within the Service Control Manager.
# The valid communities can also be configured via registry in the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ValidCommunities.
# The community name is defined by a REG_DWORD with the value 4 for READ ONLY rights.
#
# Net-SNMP service configuration example:
#
# com2sec           local       localhost snmpv1_localonly
# group                svGroup               v1 local
# view   svView included .1
# access               svGroup               "" any noauth exact svView none none
#
# ->  SNMPv1 configuration restricted to localhost with the community name snmpv1_localonly 
# For more information see http://www.net-snmp.org/docs/man/snmpd.conf.html

Youez - 2016 - github.com/yon3zu
LinuXploit