Nmap "Torizado"

[OLM]

Hola a todos, estoy intentando "torizar" Nmap a la red Tor, he utilizado el siguiente comando:

Código [Seleccionar] Expandir

proxychains nmap -sT -PN -n -sV -p80 192.168.1.41

pero me aparece el siguiente error

Código [Seleccionar] Expandir

ProxyChains-3.1 (http://proxychains.sf.net)

Starting Nmap 6.00 ( http://nmap.org ) at 2012-06-26 21:53 CEST
|S-chain|-<>-127.0.0.1:9050-<--timeout
Nmap scan report for 192.168.1.41
Host is up (0.00026s latency).
PORT   STATE  SERVICE VERSION
80/tcp closed http

Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 0.16 seconds


¿Como puedo averiguar si realmente Nmap lo tengo listo para trabajar con la red Tor? ¿Y para utilizarlo con la interfaz gráfica?

Saludos!!!!

[_- Xhenox -_]

Yo pienso si la otra PC no tiene NMAP instalado, no lo conseguiras hacer nada, tambien depende de lo que quieres hacer;;




Si te sale el error pienso que sera por esto  "80/tcp closed http"   porque el puerto 80 te lo tienen tapado..

[Kasswed]

has probado con torify?

torify nmap...

[adastra]

 Postea el fichero proxychains.conf. Tienes que tirar en ese fichero del servidor SOCKS de TOR (Y evidentemente tienes que tener TOR iniciado). Por otro lado, no es mala idea la de ejecutar NMAP con torify.


http://thehackerway.com/2011/10/14/preservando-el-anonimato-y-extendiendo-su-uso-%E2%80%93-torifying-aplicaciones-y-comandos-%E2%80%93%C2%A0parte%C2%A0iii/

[OLM]

Este es el fichero de configuracion:

Código [Seleccionar] Expandir

# proxychains.conf  VER 3.1
#
#        HTTP, SOCKS4, SOCKS5 tunneling proxifier with DNS.
#

# The option below identifies how the ProxyList is treated.
# only one option should be uncommented at time,
# otherwise the last appearing option will be accepted
#
#dynamic_chain
#
# Dynamic - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# at least one proxy must be online to play in chain
# (dead proxies are skipped)
# otherwise EINTR is returned to the app
#
strict_chain
#
# Strict - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# all proxies must be online to play in chain
# otherwise EINTR is returned to the app
#
#random_chain
#
# Random - Each connection will be done via random proxy
# (or proxy chain, see  chain_len) from the list.
# this option is good to test your IDS :)

# Make sense only if random_chain
#chain_len = 2

# Quiet mode (no output from library)
#quiet_mode

# Proxy DNS requests - no leak for DNS data
proxy_dns

# Some timeouts in milliseconds
tcp_read_time_out 15000
tcp_connect_time_out 8000

# ProxyList format
#       type  host  port [user pass]
#       (values separated by 'tab' or 'blank')
#
#
#        Examples:
#
#            socks5 192.168.67.78 1080 lamer secret
# http 192.168.89.3 8080 justu hidden
# socks4 192.168.1.49 1080
#         http 192.168.39.93 8080
#
#
#       proxy types: http, socks4, socks5
#        ( auth types supported: "basic"-http  "user/pass"-socks )
#
[ProxyList]
# add proxy here ...
# meanwile
# defaults set to "tor"
socks4 127.0.0.1 9050

Está sin tocar, como podría configurarlo, porque de tanto modificarlo al final lo deje hecho una pena.
Saludos!!!!