10 | 10 |
Architecture: all
|
11 | 11 |
Depends: ${misc:Depends}, perl, libnet-telnet-perl, libnet-ssh2-perl, libnet-snmp-perl
|
12 | 12 |
Description: Cisco device scanner
|
13 | |
The main feature that makes cisco-torch different from
|
14 | |
similar tools is the extensive use of forking to launch
|
15 | |
multiple scanning processes on the background for maximum
|
16 | |
scanning efficiency. Also, it uses several methods of
|
|
13 |
The main feature that makes cisco-torch different from
|
|
14 |
similar tools is the extensive use of forking to launch
|
|
15 |
multiple scanning processes on the background for maximum
|
|
16 |
scanning efficiency. Also, it uses several methods of
|
17 | 17 |
application layer fingerprinting simultaneoulsy, if needed.
|
18 | |
We wanted something fast to discover remote Cisco hosts
|
19 | |
running Telnet, SSH, Web, NTP, TFTP and SNMP services and
|
20 | |
launch dicitionary attacks against the services discovered,
|
21 | |
including SNMP community attack (you would like the
|
|
18 |
We wanted something fast to discover remote Cisco hosts
|
|
19 |
running Telnet, SSH, Web, NTP, TFTP and SNMP services and
|
|
20 |
launch dicitionary attacks against the services discovered,
|
|
21 |
including SNMP community attack (you would like the
|
22 | 22 |
community.txt list :-) and TFTP servers (configuration
|
23 | |
file name bruteforcing with following config leeching). The
|
24 | |
tool can also get device configurationfiles automatically
|
|
23 |
file name bruteforcing with following config leeching). The
|
|
24 |
tool can also get device configurationfiles automatically
|
25 | 25 |
if SNMP RW community is found.
|