Hola, estoy intentando instalar un programa en linux,  pero me dice que entre otras muchas cosas, que tengo que construir un controlador para linux de la siguiente forma:

    o  #> cd source/drivers/linux
    o   #> make

El resultado del primero:

k@y:~$ cd source/drivers/linux
bash: cd: source/drivers/linux: No such file or directory

¿Me falta algo, datos, estoy haciendolo mal??

El make ya no lo hago por que no funciona.


Luego hay que cargar el driver:

 o    #> cd source/drivers/linux
 o    #> sudo bash run.sh

Pero me estoy mirando dos manuales, difieren un poco, en otro manual me viene con más comandos para hacer esto, supongo que abrá diversas formas de hacerlo , no lo se.
Ha lo de cargar el driver, y finalmente iniciar el programa, no lo he hecho por que no puedo construir el controlador, pero hasta ese punto lo he hecho todo según el manual.
Por favor ayuda.
Si es menester, puedo poner el manual.
Un saludo.

Hola, necesitaria saber si con un programador JTAG flash seviria para actualizar todos los microcontroladores de una placa base y periferícos.

Según wikipedia:   https://es.wikipedia.org/wiki/JTAG

Una parte dice:

Una interfaz JTAG es una interfaz especial de cuatro o cinco pines agregadas a un chip, diseñada de tal manera que varios chips en una tarjeta puedan tener sus líneas JTAG conectadas en daisy chain, de manera tal que una sonda de testeo JTAG necesita conectarse a un solo "puerto JTAG" para acceder a todos los chips en un circuito impreso

He estado viendo programadores JTAG flash por la red, por ejemplo en está página:
http://es.rs-online.com/web/p/programadores/7055155/

Donde parece ser que es un usb, supongo que se conecta al pc y con algún programa especial , se podrán actualizar todos los controladores de la computadora simultaneamente, que no lo se.
He visto que hay varios modelos, desconozco si son para lo que pretendo o no, tampoco se que precios hay, ni si es relativamente facil utilizar este programador para reflashear todo el firmware de un computador.

Haber, yo tengo un willem usb programmer, pero con esto no se puede hacer lo que pretendo o si??

Agradeceria una aclaración, y si hay algo en el mercado para hacer esto que digo de una forma facil, si es que lo es.

Un saludo.

Hola, había olvidado el post este, hoy lo he recordado.

Entonces creeis que es normal  que salgan todos estos puertos por que desde una máquina windows zenmap no soporta el analisis de su propio host?

Todos los nombres de los servicios, que corren los puertos no me suena ninguno que haya en mi pc.

Hice scaner de puertos online y me salen cerrados, bueno, hace poco cerré todos los puertos del router, dejando solo abierto el 80.

Bueno, ahora un scan de mi propio pc como el anterior con zenmap  pero con una máquina linux, en el cual no sale como antes, y me da ahora 2 puertos abiertos que no tengo idea:

Gracias por responder, siento no haberme dado cuenta, como hacia ya algo de tiempo.
Un saludo.

El scan:


Starting Nmap 6.40 ( http://nmap.org ) at 2016-03-04 18:32 CET
NSE: Loaded 227 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 18:32
NSE: mtrace: A source IP must be provided through fromip argument.
Completed NSE at 18:33, 10.05s elapsed
Pre-scan script results:
| broadcast-eigrp-discovery:
|_ ERROR: Couldn't get an A.S value.
| http-icloud-findmyiphone:
|_  ERROR: No username or password was supplied
| http-icloud-sendmsg:
|_  ERROR: No username or password was supplied
| targets-asn:
|_  targets-asn.asn is a mandatory parameter
Initiating Parallel DNS resolution of 1 host. at 18:33
Completed Parallel DNS resolution of 1 host. at 18:33, 0.05s elapsed
Initiating SYN Stealth Scan at 18:33
Scanning 192.168.1.100 [1000 ports]
Completed SYN Stealth Scan at 18:33, 2.05s elapsed (1000 total ports)
Initiating UDP Scan at 18:33
Scanning 192.168.1.100 [1000 ports]
adjust_timeouts2: packet supposedly had rtt of -103458 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103458 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103386 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103386 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103324 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103324 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103221 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103221 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103160 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103160 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103089 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103089 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102927 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102927 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102866 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102866 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102805 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102805 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102746 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102746 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102689 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102689 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102628 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102628 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102565 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102565 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102506 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102506 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102445 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102445 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102370 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102370 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102309 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102309 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102250 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102250 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102187 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102187 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102127 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102127 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102066 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102066 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101992 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101992 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101934 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101934 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101841 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101841 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101780 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101780 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101722 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101722 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101662 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101662 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101600 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101600 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101539 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101539 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101477 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101477 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101106 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101106 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100997 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100997 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100934 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100934 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100872 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100872 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100811 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100811 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100748 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100748 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100683 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100683 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100618 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100618 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100557 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100557 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100463 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100463 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103953 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103953 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103875 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103875 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103677 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103677 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100001 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100001 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103661 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103661 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103599 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103599 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103539 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103539 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103479 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103479 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103416 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103416 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103355 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103355 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103281 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103281 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103219 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103219 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103154 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103154 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103035 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103035 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102971 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102971 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102909 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102909 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102844 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102844 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102784 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102784 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102725 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102725 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102667 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102667 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102607 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102607 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102548 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102548 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102484 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102484 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102422 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102422 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102362 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102362 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102303 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102303 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102245 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102245 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102186 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102186 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102124 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102124 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102047 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102047 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101927 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101927 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101867 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101867 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101808 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101808 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101746 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101746 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101687 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101687 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101607 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101607 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101545 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101545 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101485 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101485 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101427 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101427 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101364 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101364 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101298 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101298 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101128 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101128 microseconds.  Ignoring time.
Completed UDP Scan at 18:33, 2.54s elapsed (1000 total ports)
Initiating Service scan at 18:33
Scanning 2 services on 192.168.1.100
Service scan Timing: About 50.00% done; ETC: 18:35 (0:01:23 remaining)
Completed Service scan at 18:34, 82.60s elapsed (2 services on 1 host)
Initiating OS detection (try #1) against 192.168.1.100
Retrying OS detection (try #2) against 192.168.1.100
NSE: Script scanning 192.168.1.100.
Initiating NSE at 18:34
sendto in send_ip_packet_sd: sendto(7, packet, 65536, 0, 192.168.1.100, 16) => Message too long
Offending packet: TCP 192.168.1.100:10095 > 192.168.1.100:1 S ttl=128 id=0 iplen=0  seq=2049832030 win=3072 <mss 1460>
Completed NSE at 18:35, 30.72s elapsed
Nmap scan report for 192.168.1.100
Host is up (0.024s latency).
Not shown: 1998 closed ports
PORT     STATE         SERVICE  VERSION
68/udp   open|filtered dhcpc
5353/udp open|filtered zeroconf
Too many fingerprints match this host to give specific OS details
Network Distance: 0 hops

Host script results:
|_ipidseq: Unknown
|_path-mtu: 65535 <= PMTU < 65536

NSE: Script Post-scanning.
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 135.28 seconds
           Raw packets sent: 2131 (144.188KB) | Rcvd: 4238 (181.856KB)

Abre uno de marihuana anda, haber cuantos informáticos le pegan a la matuja jajaja.
Bueno, se pueden hablar muchas cosas de la marihuana.
Un saludo.

Hola , estoy  mirandome esto muy poco a poco.
He encontrado más buena información al respecto:
https://sites.google.com/site/iasoncs/home/system-fundamentals


Bueno, tengo problemas serios para hacer esto:

 Construir controlador de Windows chipsec (omita este paso si ya tiene controlador binario chipsec_hlpr.sys para su versión de Windows) Consulte las instrucciones en \ drivers \ Source \ Win7 \ readme. A continuación se muestra la instrucción para construir conductor chipsec_hlpr.sys:
a. Construir chipsec_hlpr.sys en Windows de 64 bits
- Instalar WDK 7600
Puede obtener WDK (por ejemplo WDK 7600.16385.1) de http://www.microsoft.com/en-us/download/details.aspx?id=11800
- Abrir WDK construir símbolo del sistema medio ambiente:
"X64 Free Build Medio Ambiente" (para la liberación de construcción)
-.. Cd <PATH_TO_CHIPSEC> \ source \ drivers \ win7 (Tenga en cuenta que <PATH_TO_CHIPSEC> es un marcador de posición para la ruta de acceso al directorio de instalación / descomprimido Chipsec La <PATH_TO_CHIPSEC> debe sustituirse por el directorio de instalación real Por ejemplo, si instala chipsec en C: \ dan \ proyectos \ Plab \ SystemFundamentals \ chipsec-1.1.0 \ chipsec-1.1.0, reemplace <PATH_TO_CHIPSEC> con C: \ dan \ proyectos \ Plab \ SystemFundamentals \ chipsec-1.1.0 \ chipsec-1.1 0.0)
- Construir -cZg
- Si la construcción completa sin errores, el controlador binario (chipsec_hlpr.sys) estarán en \ drivers de código \ Win7 \ sys directorio \ amd64
segundo. Firmar controlador en Windows de 64 bits
- Ejecutar en "x 64 Build Environment libre":
makecert -r -n "CN = Chipsec" -SS ChipsecCertStore -sr LocalMachine
- Señal de cd
- Ejecutar "sign64_sys.bat" para firmar el archivo .sys y tienen CHIPSEC instalar el controlador automáticamente
- Si devuelve cualquier error / advertencia, crear un nuevo almacén de certificados y modificar "sign64_sys.bat" en consecuencia
- Copiar el archivo * .sys firmado a la fuente / herramienta / chipsec / ayudante / ganar / win7_amd64 /
- Tendrá que permitir a los conductores modo kernel firmado de prueba de carga

Copiar conductor chipsec (chipsec_hlpr.sys) a la ruta correcta en CHIPSEC \ source \ herramienta \ chipsec \ ayudante \ win \ win7_ donde es "x 86" o "amd64" (ruta predeterminada es \ source \ herramienta \ chipsec \ ayudante \ win \ win7_amd64 )

He buscado algún tutorial o algo, pero no veo nada de como utilizar el programa WDK para construir el controlador para chipsec en windows 8.1 y hacer todo lo que dice.

Desde luego un poco más fácil podría ser este programa...

Haber si alguien puede hablarme un poco mejor para hacer esto.

Un saludo.

Coincido con los últimos comentarios, fumate un peta.
Y si quieres algo que si es saludable , vaporiza marihuana con un volcano, que no tiene nada de malo, solo aire caliente y vapor.

Los cigarros electronicos son kk igual que el p--o tabaco que engancha más que nada.

Un saludo.

Muchas gracias por responder.
Tengo el programa bajado e instalado python , pero hay no sale nada que entienda, salen muchos ejecutables de python, pero no veo ninguna herramienta, es decir no tengo ni idea de como va.
El programa para windows 64 bits será este:
https://github.com/chipsec/chipsec/raw/master/__install__/UEFI/chipsec_uefi_x64.zip

Bueno, ya se algo más.
Creo que no es tan sencillo el programa.
¿alguien a utilizado este programa o lo utiliza habitualmente??

Un saludo.

Hola, no se muy bien en que sección del foro poner el post,en fin.

Estoy intentando descargar este programa en windows que estoy ahora mismo, pero no se como hacerlo , tengo bastante información al respecto, pero no se donde descargar el programa, mejor dicho, no se que archivos descargar para el programa chipsec.

Enlaces del programa e información:
https://github.com/chipsec/chipsec
http://www.intelsecurity.com/advanced-threat-research/chipsec.html
https://github.com/chipsec/chipsec/wiki/Installing%20CHIPSEC%20in%20Windows

Rogaría una explicación  de como instalar el programa en windows, o en linux, me da igual, reinstalo el s.o. rápido.
No se si es mucho pedir, pero es que no se ni descargar el programa...

Si algún iluminado sabe como hacerlo, y arrancar el programa con todas las características , sería  muy bueno que me enseñara a hacerlo.

Es una herramienta para detectar rootkits de firmware....o eso creo haber entendido.

Un saludo y gracias por el tiempo.

jajaja buenisimo.

Esta el asunto bueno... ahora quieren atacar Siria los Turcos y arabia saudi junto otras coaliziones.... como se les ocurra entrar en Siria, ya han dicho las autoridades de ese país, que saldrán en ataudes... veremos que ocurre, pero esto va a más día sí día también...y lo peor que puede ocurrir es una gran guerra...

Ya están preparando cabezas nucleares especiales, con baja potencia, de las cuales no os extrañe que se lleguen a emplear...

Ojala se quede todo en anuncios.

Un saludo.

Si no tuvieran armas nucleares y lo que tenga, seguro ya lo habrían invadido, precisamente por que tiene las bombas, me da a mi que no lo atacan, si no se liaba gorda.

En Irak, sadam tenía bombas atómicas (supuestamente), por eso atacaron, pero me da a mi que atacaron por que sabían que  no tenía las bombas, siguiendo el ejemplo, no atacan a corea del norte... precisamente por que esta defendido.

Que si , que si quisieran lo quitarian al gordo, pero , a que precio??? se iba a liar una de muy gorda... corea del sur caia rápido...china apoyaria a corea del norte al igual que rusia, pero fijo,si no se abstendrían , con lo cual, no es muy buena idea atacar al gordo....mas aun cuando no paran de desarrollarse en militar.

Corea del norte, está muy militarizada, y preparada para la guerra en cualquier momento, de hecho,creo que continuan en guerra, o solo hay un alto el fuego con corea del sur.

En la actualidad, con la nueva crisis entre america, rusia, china, por no citar más, creo que el bando ruso-chino , apoyaria corea del norte, por intereses más que nada.


Un saludo.