Instalar un mini-servidor web en windows

Por medio de softdates usuario de elhacker.net me encuentro con un post muy interesante y util que nos permite de una forma muy sencilla crear un mini servidor , ademas de eso con el portabilizador creado por mi puedes hacer que cualquier pc sea un miniserver simplemente copiando las carpetas al disco c y listo ya con tu configuracion predetermianda.

Objetivo: Instalar un mini-servidor web en tu PC para que puedas acceder a tus archivos desde cualquier lugar con un simple navegador (en HTTPS).
Permite subir y bajar archivos, así como diversas operaciones (copiar, renombrar, eliminar, editar, buscar, comprimir, etc.).
Esto te permite tener un espacio de almacenamiento en la web con la capacidad de tu disco duro!

En la pantalla vemos como es el administrador de archivos una vez que está instalado:


Necesario:
- Windows 95/98/ME/NT/2000/XP/2003
- conexión a Internet (de preferencia permanente como la ADSL), con IP dinámica o estática.

Herramientas utilizadas:
- pi3web (servidor web)
- Quixplorer (administrador de archivos en php)

Estas dos herramientas son gratuitas y opensource.
Pi3web es un servidor web muy compacto (2.3 Mo a descargar), opensource, soporta php, rápido, consume pocos recursos (alrededor 10 Mo de memoria viva), funciona bajo todas las versiones de Windows (del 95 al 2003), fácil de instalar, generación de certificados SSL muy simple, funciona como servicio o aplicación, se desinstala limpiamente.

Quixplorer es un administrador de archivos en PHP práctico y eficaz, que no requiere una base mySQL.
La gestión de derechos es práctica y sencilla.


==============================================
ETAPA 1 – Instalar DNS

Es necesario que puedas acceder a tu PC desde Internet con un nombre fijo
(para que evites tener que recordar tu dirección IP).

Para ello, puedes utilizar servicios gratuitos como dyndns.org. Inscríbete en la
página web e instala el programa DynDns en tu PC.

Esto te permitirá acceder a tu PC con un nombre fijo (por ejemplo toto.dyndns.org)

Verifica que tu DNS funciona bien, para ello haz ping a tu PC: ping toto.dyndns.org

En adelante, supondremos que tu máquina se llama toto.dyndns.org

==============================================
ETAPA 2 – Instalación de pi3web

2.1) Descarga pi3web de http://pi3web.sourceforge.net/pi3web/
(Pi3Web-x86Win32-2_0_3.exe o versión superior.)

2.2) Instala pi3web:
2.2.a) Ejecuta Pi3Web-x86Win32-2_0_3.exe, y sigue la instalación.
2.2.b) En la pantalla "Configure server identity", marca "SSL".
2.2.c) En la pantalla "Generate SSL demo server keys and certificates":
- En "Common name" y "Server name", ingresa toto.dyndns.org
- Vacía todos los otros campos.
2.2.d) En la pantalla "Server Server Run Mode", selecciona "System service",
y termina la instalación.

2.3) Configura pi3web. En la ventana "Pi3web Server Admin"

2.3.a) En la pestaña "Mappings", elimina todas las líneas salvo aquellas
en la que el “From” es:
- /icons/
- /images/
- /errors/
- /

2.3.b) Siempre en la pestaña "Mappings", agrega los 2 mappings siguientes:
Type From To Realm
-------------------------------------------------------
Document /quix/.config/ dummy-directory/ (none)
Document /quix/.include/ dummy-directory/ (none)


2.3.c) En la pestaña “HTTP”:
- En la zona "Server stamp", vacía el texto ("Pi3Web/2.0.3")
- En "Index files", elimina todo, luego añade: index.php y index.html
- En "Methods", marca POST
- En "Size limit", ingresa 99999999

Haz clic en “OK”.

2.3.d) Elimina los archivos contenidos en el directorio C:\Pi3Web\WebRoot

2.3.e) Crea un archivo vacio: C:\Pi3Web\WebRoot\index.html

2.3.f) En tu disco duro, crea el directorio c:\tmp

2.3.g) Modifica el archivo C:\Pi3Web\bin\php.ini:

- Cambia: post_max_size = 8M
a: post_max_size = 99M

- Cambia: upload_max_filesize = 2M
a: upload_max_filesize = 99M

- Cambia: memory_limit = 8M
a: memory_limit = 99M

- Cambia: max_execution_time = 30
a: max_execution_time = 1800

(Esto permitirá subir archivos hasta 99 Mo)


==============================================
ETAPA 3 – Instalación de Quixplorer

3.a) Descarga Quixplorer desde: http://quixplorer.sourceforge.net/
(por ejemplo quixplorer_2_3_1.zip)

3.b) Crea el directorio C:\Pi3Web\WebRoot\quix

3.c) Descomprime el archivo ZIP en C:\Pi3Web\WebRoot\quix
(index.php debe estar aquí: C:\Pi3Web\WebRoot\quix\index.php)

3.d) Edita el archivo C:\Pi3Web\WebRoot\quix\.config\conf.php:

- Cambia: $GLOBALS["require_login"] = false;
a: $GLOBALS["require_login"] = true;

- Cambia: $GLOBALS["script_name"] = "[http://]".$GLOBALS['__SERVER']
['HTTP_HOST'].$GLOBALS['__SERVER']["PHP_SELF"];
a: $GLOBALS["script_name"] = "[https://]".$GLOBALS['__SERVER']
['HTTP_HOST'].$GLOBALS['__SERVER']["PHP_SELF"];

- Cambia: $GLOBALS["home_dir"] = "/home/you/public_html";
a: $GLOBALS["home_dir"] = "/";

- Cambia: $GLOBALS["zip"] = false; //function_exists("gzcompress");
a: $GLOBALS["zip"] = true; //function_exists("gzcompress");

3.e) Edita el archivo C:\Pi3Web\WebRoot\quix\.config\.htusers.php:

- Cambia: array("admin","9628d0d187029e6337baa86780b2abb6",".",
"http://localhost/",1,"",7,1),
a: array("admin","9628d0d187029e6337baa86780b2abb6",
"c:/","http://localhost/",1,"",7,1),


==============================================
ETAPA 4 – Configuración final

4.a) Abre el navegador, y ve a la dirección https://localhost/quix/

Conéctate con el login “admin”, contraseña "pwd_admin".

Ve inmediatamente a la página de admin, y cambia la contraseña admin.
(Penúltimo botón, justo antes del botón "Logoff").

A partir de aquí, podrás crear usuario.
(así como asignar directorios específicos a cada usuario.)

Observa que los enlaces haciendo clic sobre los archivos no funcionan.
(Siempre tendremos que hacer clic en el botón "Download" en la columna
de la derecha para descargar un archivo.)
Esto es normal ya que tu disco duro no es compartido en Internet fuera
del administrador de archivos Quixplorer.

4.b) Ahora que los usuarios están configurados, abre tu servidor web a Internet:
Menú Inicio > Programas > Pi3Web > Server Admin
En la pestaña “General”, selecciona "Remotely using a hostname".
En "Hostname", ingresa toto.dyndns.org
Haz clic en “OK”

4.c) Ahora ya puedes acceder a tu PC desde la dirección
https://toto.dyndns.org/quix/
Con Quixplorer podrás crear espacios para almacenar separados para cada usuario,
o también crear usuarios que sólo tengan acceso de sólo lectura.

==============================================
Observaciones en cuanto a la seguridad:



A)
¿Por qué Quixplorer y la presencia de un index.html vacio?
Porque si por casualidad un hacker entra a tu sitio web, éste sólo verá una página en blanco.
No sabrá que Quixplorer está instalado. Esto disminuye el riesgo de ataques en Quixplorer.

B)
En el archivo C:\Pi3Web\WebRoot\quix\.include\footer.php elimina todo lo que se encuentre entre las líneas: function show_footer() { // footer for html-page
y: }
(esto evita que el webmaster de la página de Quixplorer conozca la dirección de tu página web gracias al HTTP Referer.)

C)
En el archivo C:\Pi3Web\WebRoot\quix\.include\login.php
Encuentra la ubicación de este código:
---%-----------

if(isset($GLOBALS['__POST']["p_user"])) {
// Check Login
if(!activate_user(stripslashes($GLOBALS['__POST']["p_user"]), md5
(stripslashes($p_pass)))) {
logout();
}



---%-----------

y agrega sleep(10).
---%-----------

if(isset($GLOBALS['__POST']["p_user"])) {
// Check Login
sleep(10); if(!activate_user(stripslashes
($GLOBALS['__POST']["p_user"]), md5(stripslashes($p_pass)))) {
logout();
}


---%-----------

Esto impondrá un tiempo de espera de 10 segundos a la ventana de login, lo que protege a Quixplorer contra los ataques del tipo de “fuerza bruta”.

cerrando puertos 137,138,139 y 445

Via telescopio  me encuentro con este intersante tip para cerrar los famosos puertos de netbios y del smb ahra bien es muy facil.

Van a:
inicio
ejecutar como
ahi escriben regedit
dan click en HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
NetBT
Parameters
quedando de esta forma en la ventana de regedit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

Ahora bien renombran la clave TransportBindName a TransportBindNameBAK y listo ahi tienen sus puertos cerrados facilmente

identificacion de servicios con nmap

Nmap nos mostrara de forma muy precisa los servicios que se estan ejecutando en un sistema en este caso nuestro localhost , esto nos ayuda a dientificar posibles puertos abiertos que sin duda como el 139 son una visible amenaza para un hacker en el ataque de recursos compartidos por la netbios donde en windows seria nbtstat.

para saber que servicios corren ejecutamos nmap -sT -O localhost

Connect Scan Timing: About 35.73% done; ETC: 10:20 (0:02:46 remaining)
Stats: 0:01:34 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 36.03% done; ETC: 10:20 (0:02:45 remaining)
Stats: 0:01:34 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 36.23% done; ETC: 10:20 (0:02:45 remaining)
Stats: 0:01:35 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 36.53% done; ETC: 10:20 (0:02:44 remaining)
Stats: 0:01:35 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 36.73% done; ETC: 10:20 (0:02:43 remaining)
Stats: 0:01:36 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 37.03% done; ETC: 10:20 (0:02:42 remaining)
Stats: 0:01:36 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 37.23% done; ETC: 10:20 (0:02:41 remaining)
Stats: 0:01:37 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 37.53% done; ETC: 10:20 (0:02:40 remaining)
Stats: 0:01:37 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 37.73% done; ETC: 10:20 (0:02:39 remaining)
Stats: 0:01:38 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.03% done; ETC: 10:20 (0:02:38 remaining)
Stats: 0:01:38 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.23% done; ETC: 10:20 (0:02:37 remaining)
Stats: 0:01:39 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.33% done; ETC: 10:20 (0:02:38 remaining)
Stats: 0:01:39 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.53% done; ETC: 10:20 (0:02:37 remaining)
Stats: 0:01:40 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.83% done; ETC: 10:20 (0:02:36 remaining)
Stats: 0:01:40 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 38.93% done; ETC: 10:20 (0:02:36 remaining)
Stats: 0:01:41 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 39.07% done; ETC: 10:20 (0:02:36 remaining)
Stats: 0:01:41 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 39.23% done; ETC: 10:20 (0:02:36 remaining)
Stats: 0:01:42 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 39.40% done; ETC: 10:20 (0:02:36 remaining)
Stats: 0:01:42 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 39.63% done; ETC: 10:20 (0:02:35 remaining)
Stats: 0:01:43 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 39.83% done; ETC: 10:20 (0:02:34 remaining)
Stats: 0:01:43 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.13% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:44 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.27% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:44 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.30% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:44 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.30% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:45 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.43% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:46 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.70% done; ETC: 10:20 (0:02:33 remaining)
Stats: 0:01:47 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 40.70% done; ETC: 10:20 (0:02:35 remaining)
Stats: 0:02:45 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 64.55% done; ETC: 10:20 (0:01:30 remaining)
Stats: 0:02:46 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 64.95% done; ETC: 10:20 (0:01:29 remaining)
Stats: 0:02:47 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 65.08% done; ETC: 10:20 (0:01:29 remaining)
Stats: 0:02:48 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 65.95% done; ETC: 10:20 (0:01:26 remaining)
Stats: 0:02:49 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 66.07% done; ETC: 10:20 (0:01:26 remaining)
Stats: 0:02:50 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 66.57% done; ETC: 10:20 (0:01:25 remaining)
Stats: 0:02:51 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 67.07% done; ETC: 10:20 (0:01:23 remaining)
Stats: 0:02:52 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 67.95% done; ETC: 10:20 (0:01:21 remaining)
Stats: 0:02:53 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 68.08% done; ETC: 10:20 (0:01:21 remaining)
Stats: 0:02:58 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 70.80% done; ETC: 10:20 (0:01:13 remaining)
Stats: 0:02:59 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 71.30% done; ETC: 10:20 (0:01:11 remaining)
Stats: 0:02:59 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 71.45% done; ETC: 10:20 (0:01:11 remaining)
Stats: 0:03:00 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 71.73% done; ETC: 10:20 (0:01:10 remaining)
Stats: 0:03:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.02% done; ETC: 10:20 (0:01:10 remaining)
Stats: 0:03:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.05% done; ETC: 10:20 (0:01:10 remaining)
Stats: 0:03:02 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.32% done; ETC: 10:20 (0:01:09 remaining)
Stats: 0:03:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.42% done; ETC: 10:20 (0:01:09 remaining)
Stats: 0:03:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.63% done; ETC: 10:20 (0:01:09 remaining)
Stats: 0:03:05 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 72.92% done; ETC: 10:20 (0:01:08 remaining)
Stats: 0:03:06 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 73.32% done; ETC: 10:20 (0:01:07 remaining)
Stats: 0:03:07 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 73.52% done; ETC: 10:20 (0:01:07 remaining)
Stats: 0:03:12 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 75.52% done; ETC: 10:20 (0:01:02 remaining)
Stats: 0:03:13 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 75.92% done; ETC: 10:20 (0:01:01 remaining)
Stats: 0:03:14 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 76.05% done; ETC: 10:20 (0:01:01 remaining)
Stats: 0:03:15 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 76.92% done; ETC: 10:20 (0:00:58 remaining)
Stats: 0:03:16 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 77.42% done; ETC: 10:20 (0:00:57 remaining)
Stats: 0:03:17 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 77.55% done; ETC: 10:20 (0:00:57 remaining)
Stats: 0:03:18 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 78.05% done; ETC: 10:20 (0:00:55 remaining)
Stats: 0:03:19 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 78.92% done; ETC: 10:20 (0:00:53 remaining)
Stats: 0:03:20 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 79.05% done; ETC: 10:20 (0:00:52 remaining)
Stats: 0:03:20 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 79.42% done; ETC: 10:20 (0:00:51 remaining)
Stats: 0:03:21 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 79.77% done; ETC: 10:20 (0:00:50 remaining)
Stats: 0:03:21 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 79.85% done; ETC: 10:20 (0:00:50 remaining)
Stats: 0:03:22 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 80.27% done; ETC: 10:20 (0:00:49 remaining)
Stats: 0:03:23 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 80.58% done; ETC: 10:20 (0:00:48 remaining)
Stats: 0:03:24 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 80.97% done; ETC: 10:20 (0:00:47 remaining)
Stats: 0:03:25 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 81.10% done; ETC: 10:20 (0:00:47 remaining)
Stats: 0:03:26 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 81.60% done; ETC: 10:20 (0:00:46 remaining)
Stats: 0:03:27 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 82.10% done; ETC: 10:20 (0:00:45 remaining)
Stats: 0:03:28 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 82.97% done; ETC: 10:20 (0:00:42 remaining)
Stats: 0:03:29 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 83.17% done; ETC: 10:20 (0:00:42 remaining)
Stats: 0:03:29 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 83.50% done; ETC: 10:20 (0:00:41 remaining)
Stats: 0:03:30 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 83.67% done; ETC: 10:20 (0:00:40 remaining)
Stats: 0:03:30 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 84.00% done; ETC: 10:20 (0:00:40 remaining)
Stats: 0:03:31 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 84.17% done; ETC: 10:20 (0:00:39 remaining)
Stats: 0:03:31 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 84.50% done; ETC: 10:20 (0:00:38 remaining)
Stats: 0:03:32 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 84.67% done; ETC: 10:20 (0:00:38 remaining)
Stats: 0:03:32 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 85.00% done; ETC: 10:20 (0:00:37 remaining)
Stats: 0:03:33 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 85.17% done; ETC: 10:20 (0:00:37 remaining)
Stats: 0:03:33 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 85.50% done; ETC: 10:20 (0:00:36 remaining)
Stats: 0:03:34 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 85.67% done; ETC: 10:20 (0:00:35 remaining)
Stats: 0:03:34 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 86.00% done; ETC: 10:20 (0:00:34 remaining)
Stats: 0:03:35 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 86.17% done; ETC: 10:20 (0:00:34 remaining)
Stats: 0:03:35 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 86.50% done; ETC: 10:20 (0:00:33 remaining)
Stats: 0:03:36 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 86.67% done; ETC: 10:20 (0:00:33 remaining)
Stats: 0:03:36 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 86.92% done; ETC: 10:20 (0:00:32 remaining)
Stats: 0:03:37 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 87.10% done; ETC: 10:20 (0:00:32 remaining)
Stats: 0:03:37 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 87.42% done; ETC: 10:20 (0:00:31 remaining)
Stats: 0:03:38 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 87.55% done; ETC: 10:20 (0:00:30 remaining)
Stats: 0:03:38 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 87.72% done; ETC: 10:20 (0:00:30 remaining)
Stats: 0:03:39 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 87.88% done; ETC: 10:20 (0:00:30 remaining)
Stats: 0:03:39 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 88.13% done; ETC: 10:20 (0:00:29 remaining)
Stats: 0:03:40 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 88.30% done; ETC: 10:20 (0:00:29 remaining)
Stats: 0:03:40 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 88.63% done; ETC: 10:20 (0:00:28 remaining)
Stats: 0:03:41 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 88.80% done; ETC: 10:20 (0:00:27 remaining)
Stats: 0:03:41 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 89.13% done; ETC: 10:20 (0:00:26 remaining)
Stats: 0:03:42 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 89.30% done; ETC: 10:20 (0:00:26 remaining)
Stats: 0:03:42 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 89.33% done; ETC: 10:20 (0:00:26 remaining)
Stats: 0:03:43 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 89.80% done; ETC: 10:20 (0:00:25 remaining)
Stats: 0:03:43 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 90.13% done; ETC: 10:20 (0:00:24 remaining)
Stats: 0:03:44 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 90.30% done; ETC: 10:20 (0:00:24 remaining)
Stats: 0:03:44 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 90.63% done; ETC: 10:20 (0:00:23 remaining)
Stats: 0:03:45 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 90.80% done; ETC: 10:20 (0:00:22 remaining)
Stats: 0:03:45 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 91.13% done; ETC: 10:20 (0:00:21 remaining)
Stats: 0:03:46 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 91.45% done; ETC: 10:20 (0:00:21 remaining)
Stats: 0:03:46 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 91.67% done; ETC: 10:20 (0:00:20 remaining)
Stats: 0:03:47 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 91.95% done; ETC: 10:20 (0:00:19 remaining)
Stats: 0:03:47 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 92.17% done; ETC: 10:20 (0:00:19 remaining)
Stats: 0:03:48 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 92.45% done; ETC: 10:20 (0:00:18 remaining)
Stats: 0:03:48 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 92.67% done; ETC: 10:20 (0:00:18 remaining)
Stats: 0:03:49 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 92.95% done; ETC: 10:20 (0:00:17 remaining)
Stats: 0:03:49 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 93.17% done; ETC: 10:20 (0:00:16 remaining)
Stats: 0:03:50 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 93.45% done; ETC: 10:20 (0:00:16 remaining)
Stats: 0:03:50 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 93.67% done; ETC: 10:20 (0:00:15 remaining)
Stats: 0:03:51 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 93.95% done; ETC: 10:20 (0:00:14 remaining)
Stats: 0:03:51 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 94.17% done; ETC: 10:20 (0:00:14 remaining)
Stats: 0:03:52 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 94.45% done; ETC: 10:20 (0:00:13 remaining)
Stats: 0:03:52 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 94.67% done; ETC: 10:20 (0:00:13 remaining)
Stats: 0:03:53 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 94.95% done; ETC: 10:20 (0:00:12 remaining)
Stats: 0:03:53 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 95.17% done; ETC: 10:20 (0:00:11 remaining)
Stats: 0:03:54 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 95.45% done; ETC: 10:20 (0:00:11 remaining)
Stats: 0:03:54 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 95.67% done; ETC: 10:20 (0:00:10 remaining)
Stats: 0:03:55 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 95.95% done; ETC: 10:20 (0:00:09 remaining)
Stats: 0:03:55 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 96.17% done; ETC: 10:20 (0:00:09 remaining)
Stats: 0:03:56 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 96.38% done; ETC: 10:20 (0:00:08 remaining)
Stats: 0:03:56 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 96.60% done; ETC: 10:20 (0:00:08 remaining)
Stats: 0:03:57 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 97.02% done; ETC: 10:20 (0:00:07 remaining)
Stats: 0:03:58 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 97.32% done; ETC: 10:20 (0:00:06 remaining)
Stats: 0:04:00 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 97.72% done; ETC: 10:20 (0:00:05 remaining)
Stats: 0:04:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 98.22% done; ETC: 10:20 (0:00:04 remaining)
Stats: 0:04:02 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 98.35% done; ETC: 10:20 (0:00:04 remaining)
Stats: 0:04:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.22% done; ETC: 10:20 (0:00:01 remaining)
Stats: 0:04:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.58% done; ETC: 10:20 (0:00:01 remaining)
Stats: 0:04:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.80% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:05 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:05 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:06 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:06 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:07 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 99.99% done; ETC: 10:20 (0:00:00 remaining)
Stats: 0:04:08 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 100.00% done; ETC: 10:20 (0:00:00 remaining)
Skipping OS Scan against localhost (127.0.0.1) because it doesn't work against y
our own machine (localhost)
Interesting ports on localhost (127.0.0.1):
Not shown: 996 closed ports
PORT STATE SERVICE
135/tcp open msrpc
445/tcp open microsoft-ds
1026/tcp open LSA-or-nterm
1034/tcp open unknown

OS detection performed. Please report any incorrect results at http://nmap.org/s
ubmit/ .
Nmap done: 1 IP address (1 host up) scanned in 248.06 seconds

en este caso solo se han identificado puertos udp pero nmap tambien puede identificar los puertos udp simplemente enviando un paquete al puerto y si recibe una respuesta icmp(protocolo de mensajes de control en internet ) el puerto esta cerrado deno ser asi esta abierto.

ahora que son estos puertos :

si observamos bien podemos determinar que el puerto 135 es esencial para los sistemas windows por tanto ya sabes qeu este localhost corre bajo windows .

Por otra parte el puerto 445 tiene el objetivo de compartir archivos con sistemas remotos por eso fue victima de ataques como el sasser y el blaster por eso es importante cerrarlo.por ultimo nos qeudan el 1026 y el 1034 que son servicios usulaes y que no causan probelam para un buen windows con firewal .

Busqueda de servicios rpc

RPC es un tipo de servicio en linux significa llamadas a procedimientos remotos y que estos no tienen puertos asignados . pero que carajos es esto , pues bien el rpc nos permite hacer llamdas a procedimientos de otras maquinas a traves de la red y como estos vueltos no tienen puertos para ellos utilizan un demonio llamado portmap..pero que es portmap pues este es un servicio de escucha a 111 tipo rpc y en palabras cristianas qeu significa , pues que el portmap hace de intermediario cuando una maquina se queire conectar a un puerto primero tiene que pregunatrle a portamp en qeu puerto tcp o udp esta escuchando el demonio con el que quiere hablar

Busquedas dns

Ahora vamos a mirar una busqueda basica con nslookup este comando nos muestra la direccion ip y cual es el nombre de nuestro servidor de nombre ejemplo:


nslookup www.google.com

server : ns7.etb.net.co
Adress : 200.23.25.78


Non-authoritative answer :

Name: www.l.google.com

Addresses: 64.233.169.99, 64.233.169.103, 64.233.169.104, 64.233.169.147
Aliases: www.google.com

haciendo pings con nmap en linux

Nmap es una herramienta para el mapeo de redes en este post les voy a explciar lo que aprendi ahorita jejeje que es un barrido de pings con nmap.Ahora con nmap es muy facil ya que tiene incorpodaro un comando que es -sp y solo es nesesario pasarle la lista de direcciones .

ejemplo:

Nmap -sp 192.168.10.0/30

host(192.168.10.0) seems to be a subnet broadcast address

(returned 1 estra ping)

host kakaos (192.168.10.3)appears to be up.

haciendo un ping en linux

Una forma de hacer un ping a una maquina en linux es conectadose al puerto echo que es el puerto 7 con los paquetes usd y tcp . Como ya sabemos los datos que se devuelvan van a hacer de forma de eco por lo tanto si la respuesta es la esperada podemos decir que la maquina esta funcionando. Por ejemplo

telnet radical.com echo
Connected to radical.com
Escape character is '^'
mañana es viernes

mañana es viernes