Re: Modificar el nombre de distribucion .
El Miércoles, 28 de Diciembre de 2005 15:29, Ricardo Frydman Eureka! escribió:
|| Ricardo_Bendita wrote:
|| > Buenas a todos lista, bueno mi pregunta es la siguiente :
|| >
|| > ¿ Con que software o parche, podria alterar que al momento de escanear
|| > por ejemplo con
|| > el nmap mi Sistema operativo en vez de aparecer que se trata de un
|| > linux muestre que
|| > es un windows xp/2000 o unix o el que sea ?
|| >
|| > En algun momento hace mucho habia leido sobre este tema, navegando por
|| > google, pero
|| > ahora no encuentro nada :( , espero me puedan dar sus comentarios,
|| > gracias por todo .
||
|| /etc/issue ?
Yo uso para esos menesteres el comando "xprobe2 IP/dominio" y la información
que ofrece no tiene nada que ver con el contenido de /etc/issue. Además, qué
tiene que ver hacer un nmap con leer un fichero en /etc? ¿cómo puede alguien
remotamente leer el /etc/issue mediante un escaneo de puertos?
~ $ cat /etc/issue
Debian GNU/Linux 3.1 \n \l
~ $ xprobe2 localhost
Xprobe2 v.0.2.2 Copyright (c) 2002-2005 fyodor@o0o.nu, ofir@sys-security.com,
meder@o0o.nu
[+] Target is localhost
[+] Loading modules.
[+] Following modules are loaded:
[x] [1] ping:icmp_ping - ICMP echo discovery module
[x] [2] ping:tcp_ping - TCP-based ping discovery module
[x] [3] ping:udp_ping - UDP-based ping discovery module
[x] [4] infogather:ttl_calc - TCP and UDP based TTL distance calculation
[x] [5] infogather:portscan - TCP and UDP PortScanner
[x] [6] fingerprint:icmp_echo - ICMP Echo request fingerprinting module
[x] [7] fingerprint:icmp_tstamp - ICMP Timestamp request fingerprinting
module
[x] [8] fingerprint:icmp_amask - ICMP Address mask request fingerprinting
module
[x] [9] fingerprint:icmp_port_unreach - ICMP port unreachable fingerprinting
module
[x] [10] fingerprint:tcp_hshake - TCP Handshake fingerprinting module
[x] [11] fingerprint:tcp_rst - TCP RST fingerprinting module
[+] 11 modules registered
[+] Initializing scan engine
[+] Running scan engine
[-] ping:tcp_ping module: no closed/open TCP ports known on 127.0.0.1. Module
test failed
[-] ping:udp_ping module: no closed/open UDP ports known on 127.0.0.1. Module
test failed
[-] No distance calculation. 127.0.0.1 appears to be dead or no ports known
[+] Host: 127.0.0.1 is up (Guess probability: 25%)
[+] Target: 127.0.0.1 is alive. Round-Trip Time: 0.00086 sec
[+] Selected safe Round-Trip Time value is: 0.00172 sec
[-] fingerprint:tcp_hshake Module execution aborted (no open TCP ports known)
[+] Primary guess:
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.10" (Guess probability: 74%)
[+] Other guesses:
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.9" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.8" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.7" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.6" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.5" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.4" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.3" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.2" (Guess probability: 74%)
[+] Host 127.0.0.1 Running OS: "Linux Kernel 2.6.1" (Guess probability: 74%)
[+] Cleaning up scan engine
[+] Modules deinitialized
[+] Execution completed.
--
y hasta aquí puedo leer...
Reply to: