Recently I’ve experienced some odd SSH behavior, my connection is lost after not issuing a command for a while. Usually I get this message:

ME@SERVER:~% Read from remote host SERVER: Connection reset by peer
Connection to SERVER closed.

Nice, indeed. However, this can be fixed by creating the file ~/.ssh/config and pasting this into it:

TCPKeepAlive no
ServerAliveInterval 15

What happens here is that you overwrite the default SSH configuration usually found in /etc/ssh/ssh_config with a different behavior. A timeout interval is set after which your SSH client will request a response from the server. This is usually done via TCP keep-alive, which is unreliable (and insecure) and therefore turned off. So, no more timed-out connections here, great! Feel free to read the ssh_config manpage for more insight.

Transmission Control Protocol vs User Datagram Protocol, console-wise.

Xbox’s use UDP, which basically throws data packets at the CPU, doesn’t care if it catches them and only sends them once. Whereas a PS3 and a Wii use TCP, which catches every data packet and lets the computer know that it’s caught it.

I was taught this in college so don’t start flaming me if I’m wrong/inaccurate. It’s just a little something that I found interesting, perhaps Microsoft should consider TCP if it’s so much more reliable and efficient than UDP.

So if you’re playing a game on an Xbox (or PC) and you experience lag (especially online), you’re no doubt using UDP.

A MizinhaK  postou no twitter esse vídeo coisa de nerd, mas criativo sem dúvida e como toda música ruim fica na cabeça.

Espero no aburrir ni confundir a nadie con las dos entradas anteriores sobre puertos abiertos en windows. Para abreviar un poco hay una herramienta llamada tcpview descargable del link http://live.sysinternals.com/ solo esta herramienta o todo el conjunto de utilidades, muy básicas pero muy prácticas de http://download.sysinternals.com/Files/SysinternalsSuite.zip.

es entretenido el ir viendo como se van viendo y moviendo las conexiones y como van modificando su estado bajo el protocolo tcp/ip de desconexión o conexión con otro servicio.

Ya sería un motivo de preocupación el no saber o reconocer donde está conectado el ordenador o bajo que programa se encuentra conectado al exterior.

conexiones a ordenador remoto al puerto 80 o http significa simplemente que seguramente hay un navegador abierto y este el motivo. Tambien podría ser debido a alguna actualización del sistema operativo o antivirus. Aquí comenzará el análisis y el aprendizaje.

El comando válido para ver los puertos abiertos tanto en Linux como en Windows es netstat pero con diferentes parámetros en ambos casos.

si establezco conexíones con máquinas en la red local o por internet, el comando que me llevará a poder visionar

netstat -anpe | grep tcp

En este caso nos encontramos con 9 columnas. De ellas solo seran de mi interes en este momento 1, 4, 5, 6, 9.

La primera indica que la comunicación es tcp, la cuarta indica las conexiones que tiene establecida mi máquina y en que puerto, la quinta es con quien está conectada mi máquina y en que puerto, la sexta indica el estado de la conexión, ESTABLISHED significa que las máquinas remotas estan conectadas. Finalmente la última columna inica el número de proceso y el proceso que mantiene la conexión.

Si comentamos el resultado de la impresión de pantalla el resultado no indica que hay unas cuentas màquinas conectadas a mi ordenador en su puerto 80, se trata de un servidor web. Que la ip interna de mi servidor es 192.168.0.2. De la misma forma observo 2 conexiones en el puerto 22, puerto de conexión cifrado de openssl, ssh….  Por aquí sería posible el identficar si alguien nos está haciendo tunneling en el servidor…. ya llegaremos.

Realizaremos un par de pruebas en post distintos para determinar los puertos abiertos. La primera muy simple y que no necesita de ningún programa extra en el sistema operativos en que nos encontramos

Si vamos a Inicio – Ejecutar y escribimos cmd entramos en una pantalla de modo DOS. En ella escribimos netstat -ano
SEGURAMENTE A VOSOTROS NO APARECERAN TANTOS DATOS PERO VAMOS A ANALIZARLOS.

La primera columna indica el tipo de protocolo, tcp o udp. La segunda columna indica el ordenador local, en el que hacemos netstat, la tercera columna con quien estamos estableciendo la comunicación, la cuarta columna el estado de la comunicación y la quinta columna el proceso que realiza dicha conexión. Uff veamos más información.

127.0.0.1 es la maquina en la que uno se encuentra. Hay programas que establecen la comunicación consigo mismo dentro del ordenador de ahí que aparezca la misma ip en las dos columnas, local y remota. Para mi la primera preocupación es determinar las que pone ESTABLISHED, por que significa que la comunicación está establecida en ese momento.

Ahora nos queda el determinar en la última columna que aparece el número de proceso, a que proceso corresponde. Para ello con la combinación de teclas Crlt+Alt+Supr o con el botón derecho en la barra inferior escoger Administrador de tareas.

Nada que no me deja seguir añadiendo imagenes. Cierro este post y continuo con el siguiente en el punto que lo dejé.

Antes de nada, el paso que iba a explicar estaba relacionado con asociar el proceso con su número identificador, pero hay quien prefiere la opción netstat -anb donde la ‘b’ ya responde con la ruta de donde está el proceso que ejecuta aquella conexión.

For the last few days I’ve been writing a simple IRC bot in Ruby. I have noticed however that the documentation for Ruby Sockets is quite poor, so I thought I’d post a bit about using Ruby Sockets here.

These are all the main classes that deal with sockets, with the exception of IO.

BasicSocket
This is the base socket class which defines a few simple methods, pretty useless on its own.

Socket
This class contains everything you need to work with sockets, however if you intend to use a TCP, UDP, SOCKS or UNIX socket you will probably be better off using one of the other classes.
http://en.wikipedia.org/wiki/Internet_socket

UNIXSocket & UNIXServer
These two classes make it easy to quickly work with UNIX sockets.
http://en.wikipedia.org/wiki/Unix_socket

IPSocket
This is the base class for working with IPv4 and IPv6 addresses.
http://en.wikipedia.org/wiki/Internet_Protocol

UDPSocket
As the name suggests this provides everything you need to work with UDP.
http://en.wikipedia.org/wiki/User_Datagram_Protocol

TCPSocket & TCPServer
Everything you need to deal with TCP is in these two classes as TCP is the most common internet protocol, this will probably be the class you will most use.
http://en.wikipedia.org/wiki/Transmission_Control_Protocol

SOCKSSocket
http://en.wikipedia.org/wiki/SOCKS

For the most part you will only ever make use of TCPSocket, TCPServer and UDPSocket. In my next post I’ll show some examples of using these and Socket.

Mengirim surat urusannya mudah; surat dilipat, masukkan ke amplop, tutup rapat, beri alamat dan kode pos, tempel perangko, antarkan ke kantor pos. Selesai (bayar dulu). Bagaimana  bisa sampai ke si alamat, itu urusan  kantor pos.

Mengirim informasi melalui internet mirip meski tidak sesederhana surat. Berkas yang hendak dikirim ditangani “kantor pos”, yang menerapkan  tata cara kirim dan terima berkas di komputer. Tata cara ini disebut protokol, yang mengatur berkas supaya sampai dalam waktu secepat-cepatnya. Ada  2 jenis protokol, protokol pengendali transmisi dan protokol internet sendiri. Keduanya membentuk kesatuan, Transmission Control Protocol/Internet Protocol disingkat TCP/IP.

Kecepatan pengiriman ditentukan oleh 2 hal, besar berkas dan kapasitas saluran atau jalan. Berkas yang besar tidak mungkin melewati saluran atau jalan kecil. Karenanya, muatan harus dipotong dulu atas serpihan-serpihan kecil, disebut paket data. (Contoh paket data “merah”, “kuning”, “hijau” pada gambar di atas.) Paket data lebih mudah (dan gesit) melewati lorong-lorong “tikus”.

Bagian “IP” dari pasangan TCPI/IP bertugas menulisi alamat tujuan di paket data, sedang “TCP” memberi nomor urut , biar tidak nyasar dan juga mudah dalam penyusunnya kembali nanti. Paket data siap disebar, berpencar memasuki semua lorong sempit yang lowong berlomba mencapai tujuan.

Dalam perjalanannya, paket data akan menemui banyak persimpangan jalan. Lihat gambar. Bingung, tidak tahu dan tidak bisa menentukan lintasan mana selanjutnya yang harus ditempuh. Komputer di sini bertindak sebagai router yang mengarahkan paket data menempuh lintasan tertentu setelah menerima sinyal “hijau” dari router berikutnya. Router sangat sibuk karena harus mengatur lintasan yang dipakai beramai-ramai oleh paket data lain. Kalau penuh, ya harus cari lintasan lain. Lintasan paket selalu berubah.

Begitulah pengiriman dilaksanakan secara estafet (berantai) hingga semua paket data sampai di komputer tujuan. Sebagian paket mungkin sudah tiba lebih dulu. Protokol TCIP/IP  di komputer tujuan bertugas menyusun paket data dan mengembalikannya menjadi informasi utuh seperti semula. Paket data di”absen”, dan horee.. paket semua hadir lengkap, tidak ada yang hilang. Paket disambung kembali dan jadilah informasi.

Hebatnya, proses pengiriman ini tuntas hanya dalam orde per ribu detik saja! (Padahal dikirim dari ujung dunia sana.)

Sebagai pengetahuan tambahan lalulintas internet, kita akan melakukan ekpserimen kecil-kecilan  mengetahui seberapa sibuk lalu lintas internet itu. Hasil yang didapat menurut “Internet Traffic Report” adalah seperti gambar di samping.

Indeks angka tinggi berarti kecepatan (keandalan, kesibukan) internet tinggi. Menarik, mengapa benua Asia ‘kok rendah, ya.

Satu contoh lagi, di bawah, memperlihatkan saluran interkoneksi yang dipakai menghubungkan “VisualRoute” di Amerika dengan misalnya “Kompas” di Indonesia.

Belum puas bereksperimen? Coba gunakan kata kunci “traceroute” di browser untuk melihat dan mencoba program terkait lalu lintas internet.

Selamat mencoba!

Al 1961, un alumne de l’Institut Tecnològic de Massachussets (MIP), Leonard Kleinrock inicià un projecte sobre la possibilitat d’enviar informació d’un ordinador a un altre anomenat teoria de la commutació de paquets d’informació. La primera xarxa interconnectada data de finals de 1969, concretament el 29 d’octubre, el científic i professor en Ciències de la Computació de la Unversitat d’UCLA, Leonard Kleinrock, aconseguint connectar la computadora de la seva universitat amb un de la Universitat d’ Stanford, creant així el primer node. ARPANET, aquest és el nom que rep la xarxa, és l’origen del que avui entenem com Internet. Com a curiositat, indicar que la velocitat de transferència rondava els 0,9 kilobits per segon. Les Universitats de Santa Bàrbara i la de Utah també van aconseguir connectar-se, formant d’aquesta manera una xarxa de quatre nodes entre les universitats citades.

Al 1971 va néixer el correu electrònic. Raymond Samuel Tomlinson dissenyà la primera aplicació del que ara coneixem com e-mail per ARPANE. Incorporà l’arroba, símbol que prové de l’àrab per separar el nom de l’usuari i el del servidor. Una arroba equival a 25 lliures de pes, uns 12 kilograms. Al mateix temps, altres universitats van aconseguir afergir-se a ARPANET. La idea d’una xarxa universal anava agafant forma: es van assentar els protocols com el Transmission Control Protocol (TCP), possibilitant d’aquesta manera la comunicació entre ordinadors.

Aparagueren els primers problemes entre els científics que defensaven la idea d’una xarxa lliure per intercanviar informació i coneixements, i les empreses, que volien dominar la xarxa i proritzar per sobre de tot llurs interessos econòmics. L’expansió dels ordinadors personals van possibilitar el gran salt. És l’anomenda democratització de la Xarxa. La guerra de sistemes operatius d’Apple, IBM i Microsoft havia començat. Al 1989, Tim Berners-Lee, de l’Organització Mundial per la Investigació Mundial (CERN), va aplicar el projecte de l’hipertext (ideat al 1980), que consisteix en crear hipervincles i enllaços que relacionen texts compuratitzats. L’aparició de l’hipertext, és a dir, HTTP i HTML (recordem que http vol dir Hypertext Transfer Protocol) va coincidir amb la irrupció de la World Wide Web, primer sistema de documents d’hipertexts, i el WorldWideWeb, el primer navegador web, i HTTPD, el primer servidor de web.

Al 1993, la CERN afirma que la Web seria gratuïta per tothom. L’evolució des d’aquell dia ha estat imparable. Es calcula que aviat hi hauran 2000 milions d’usuaris. El que encara està a l’aire és que es mantingui el caràcter democràtic i lliure de la Web, respectant la idea original dels seus creadors. La lògica de la llibertat tremola davant dels interessos corporativistes, com sempre disposats a privatitzar i fer negoci, en lloc de potenciar les eines de coneixement. Així s’explica que els pressupostos en matèria de cultura i educació siguin ridículs en comparació, per exemple, als de defensa.

En aquest vídeo animat en V.O.S.E ens ho expliquen de manera més àmplia; i en només en vuit minuts:

Several weeks ago, I introduced the first in a series of posts that will explore various Internet protocols using Rhino JavaScript to create the supporting software.

Please see: http://jimlawless.wordpress.com/2009/09/03/internet-protocols-and-rhino-javascript/

In this installment, I want to introduce a small utility that we will use at the beginning of many of these posts as an initial testbed before we attempt to write any scripts. We’ll call this program tcp_cli.js ( or just tcp_cli ).

In tcp_cli, I intend to do these things:

• Prompt the user for a server name
• Prompt the user for a port number
• Connect to the specified service
• Create a thread that will continuously display any responses from the service
• In the main thread, wait for console input strings and send them to the service

Since I intend to obtain user input, I need to read from Java’s System.in object. Rhino JS already has a print() function, so I thought I’d make a counterpart function called readLine(). I created the readLine() function in a separate library called readline.js. Please see the source code below:

// Provide a function to read from the Java
// standard input object System.in.
//
// License: MIT / X11
// Copyright (c) 2009 by James K. Lawless
// jimbo@radiks.net http://www.radiks.net/~jimbo
// http://www.mailsend-online.com
//
// Permission is hereby granted, free of charge, to any person
// obtaining a copy of this software and associated documentation
// files (the "Software"), to deal in the Software without
// restriction, including without limitation the rights to use,
// copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the
// Software is furnished to do so, subject to the following
// conditions:
//
// The above copyright notice and this permission notice shall be
// included in all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
// EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
// OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
// NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
// HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
// WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
// FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
// OTHER DEALINGS IN THE SOFTWARE.

importPackage(java.io, java.lang);

var stdin=null;

   // We can't reference System.in because "in"
   // is a JS keyword, so we use the brackets to
   // dereference the "in" member of System.
function readLine() {
   if(stdin==null) {
		stdin=new BufferedReader(
			new InputStreamReader(
				System['in']));
   }
   return stdin.readLine();
}

Note that since in is a JavaScript keyword, I had to look up the property ‘in’ using the square-bracket syntax.

I chose to create a separate thread to monitor the responses we get back from the service to simplify the code at this time. Both of the calls to read data from either the standard console input device or to read data from the socket may block ( or halt processing until a read operation can complete ) which can be a bit unwieldy.

We will effectively have two running threads. One will be polling the service we are conversing with and will display that service’s responses. The other thread ( our main thread of execution ) will poll the standard input device and will send those entered strings of text to the service.

Some of you may be asking “Why are you reinventing ‘telnet’ ?”

Telnet is a TCP terminal client that is often used to perform the kinds of exploratory tasks that I intend to introduce in this series of posts. The only drawback to using telnet as a client is that one must type precisely what one intends to type … if you backspace over an error to correct it, the entire stream of characters including backspaces is sent to the service.

The service, more often than not, sees the backspace characters as noise and will yield some sort of error message.

By leveraging the console input device for input, we are afforded the luxury of correcting ourselves as we type before we send anything to the server.

An added bonus is that on many operating-systems, you simply have to press the cursor-up key to scroll through strings that you have already entered. One might find it easier to perform repetitive operations by using this feature.

So, to answer the question, I have not recreated telnet; I have created something similar that allows me to more readily send correct data to the given TCP service.

Here is the source code for tcp_cli:

tcp_cli.js

// TCP session interactive command
// prompt client.
//
// License: MIT / X11
// Copyright (c) 2009 by James K. Lawless
// jimbo@radiks.net http://www.radiks.net/~jimbo
// http://www.mailsend-online.com
//
// Permission is hereby granted, free of charge, to any person
// obtaining a copy of this software and associated documentation
// files (the "Software"), to deal in the Software without
// restriction, including without limitation the rights to use,
// copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the
// Software is furnished to do so, subject to the following
// conditions:
//
// The above copyright notice and this permission notice shall be
// included in all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
// EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
// OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
// NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
// HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
// WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
// FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
// OTHER DEALINGS IN THE SOFTWARE.

importPackage(java.io,java.lang);

load("tcplib.js");
load("readline.js");

   print("What server do you wish to connect to?");
   server=readLine();
   print("What port do you wish to connect to?");
   port=readLine();

   sock=tcpConnect(server,port);
	   // Start a thread to monitor the server's responses
	var mon = new Runnable() {
		run: function () {
         var s;
			for(;;) {
            try {
               if(sock.inp.ready()) {
                  s=sock.inp.readLine();
                  print(s);
               }
            }
            catch(e) {
               print("(monitor is ending...)");
               break;
            }
			}
		}
	};

	new Thread(mon).start();

   for(;;) {
      s=readLine();
      if(s=="alldone")
         break;
      tcpSendStringLine(sock,s);
   }
   tcpClose(sock);

This segment of code may look a little strange:

	var mon = new Runnable() {
		run: function () {
         var s;
			for(;;) {
            try {
               if(sock.inp.ready()) {
                  s=sock.inp.readLine();
                  print(s);
               }
            }
            catch(e) {
               print("(monitor is ending...)");
               break;
            }
			}
		}
	};

	new Thread(mon).start();

The first line instantiates a new Runnable object. Runnable objects are primarily objects capable of being scheduled by the Java thread-manager. When the thread-manager schedules a Runnable object for execution, it ultimately calls that object’s run() method.

We provide a body for the run() method as a JS function. The function loops indefinitely until an exception is thrown. Then, the message (monitor is ending…) is displayed and we drop out of the thread. The monitor thread then ceases execution.

After defining this object, we formally need to instruct the thread-manager to schedule the object for execution. The construction of a Thread object via the new operator followed by a call to that Thread object’s start() method schedules the execution.

We then drop into our console input loop.

Let’s test tcp_cli with the finger server we constructed in the last post. Start the finger server:

java -jar js.jar fingerSrv3.js


In a separate console window, invoke the tcp_cli script:

java -jar js.jar tcp_cli.js


You’ll be prompted for a server and port. Choose localhost and 79 respectively. A connection will then be made. A blank line will appear. You may type a string to send to the service. Enter ‘test’ with no quotes and hit ENTER.

Including the early conversation, you should see something like:

What server do you wish to connect to?
localhost
What port do you wish to connect to?
79
test
Heya! The time is Fri Oct 23 2009 19:55:21 GMT-0500 (CDT)


In the finger server window you should see something like:

test


To terminate tcp_cli enter the string ‘alldone’ in lower-case with no quotes:

alldone


You should then see the “(monitor is ending…)” message.

Now, we have a simple TCP command-line interface. In the next installment, I’d like to explore the POP3 protocol. ( We’ll learn how to read inbound Internet mail from a POP3 provider.)

The source tcp_cli.js can be downloaded at:
http://www.mailsend-online.com/wp/tcp_cli.zip

Save to del.icio.us
Digg it
Save to Reddit
Share on Facebook
Share on Twitter
More bookmarks

Unless otherwise noted, all code and text entries are Copyright © 2009 by James K. Lawless

The long wait is over. Ronin 0.3.0, code-named “big-push”, has finally been released.

DataMapper 0.10.0

Ronin was probably one of the first big Ruby apps to upgrade to DataMapper 0.10.0. As a result of this, we had to postpone the release of Ronin 0.3.0, until DataMapper 0.10.0 had finished it’s rigorous two month Q/A cycle.

Once DataMapper 0.10.0 had been released, the two months of Q/A and almost a complete rewrite of the code-base really showed itself. I think @dkubb, @dbussink, @snusnu, @xshay, @myabc, @rsim, @namelessjon, @knowtheory and everyone else who helped with 0.10.0 deserves applause for their hard work and dedication.

YARD

As of 0.3.0, Ronin has successfully moved to YARD based documentation. The new Ronin API docs can be found in the usual location. YARD really helped improve the detail of the Ronin API docs, allowing developers to specify method arguments, accepted object-types, yield arguments, possible exceptions and return-types.

Additionally, YARD handlers were added to Ronin that parsed and regenerated documentation for DataMapper properties/relations. These additional YARD handlers helped improve documentation coverage for Ronin models, such as Ronin::Arch or Ronin::Exploits::Exploit.

Ronin::UI::CommandLine

Ronin::UI::CommandLine was almost entirely refactored in 0.3.0. Ronin::UI::CommandLine::Command was rewritten to use Thor. Switching to Thor greatly simplified the ronin commands, making it easier to write new commands. A good example of this, is the source-code for the install command from before and after 0.3.0.

Another benefit to using Thor, albeit cosmetic, was being able to use Thor’s ANSI color-output. Normal output will now appear in green, warnings in yellow and error messages in red.

New convenience methods were also added to Ronin::UI::CommandLine::Command to help format and print various data: indent, print_title, print_array and print_hash.

Ronin::UI::Output

As of 0.3.0, Ronin::UI::Diagnostics and Ronin::UI::Verbose were replaced with the brand new Ronin::UI::Output module. Ronin::UI::Output is designed to delegate how output is handled. By default all output is sent to Ronin::UI::Output::Handler, which prints the output to the terminal. One can override the default output handler by using Ronin::UI::Output.handler=, to specify the new handler module; which must define print_info, print_debug, print_warning and print_error methods.

Ronin::UI::Output also provides the Helpers module, which can be included into any class and adds the print_info, print_debug, print_warning and print_error methods.

New Convenience Methods

New TCP and UDP networking methods were added to 0.3.0. Now one can easily create TCP/UDP servers using, Net.tcp_server, Net.tcp_server_session, Net.tcp_single_server, Net.udp_server and Net.udp_server_session.

Ronin::Network::HTTP::Proxy was also added to 0.3.0. The Ronin::Network::HTTP::Proxy helps parse and represent HTTP proxy addresses, and is now used by Ronin::Network::HTTP.proxy and all :proxy options.

proxy = Network::HTTP::Proxy.parse('148.233.239.24:80')
# => #<Ronin::Network::HTTP::Proxy: 148.233.239.24:80>

The Proxy class can also be used to test a proxy.

proxy.valid?
# => true
proxy.lag
# => 0.003881

Ronin::Platform

The overlay.xsl file got a make-over in 0.3.0. overlay.xsl is a XML StyleSheet, which helps render ronin.xml files from Overlays into proper XHTML when they are viewed in a web-browser. Now ronin.xml files should appear more like a standard "About" web-page.

Reloading Overlays/Extensions while ronin is running became possible with the addition of Ronin::Platform.reload!. Now if an Extension is modified, one can simply call Platform.reload! and get the updated version.

Ronin Extensions gained convenience methods for defining reader/writer methods to instance variables: attr_reader, attr_writer and attr_accessor. They can be used in Ronin Extensions, just as one would use them in a class.

ronin_extension do

  attr_accessor :var
  attr_reader :result

  setup do
    @var = 5
    @result = nil
  end
  ...
end

Ronin Extensions also gained their own on-demand temp directory. When Ronin::Platform::Extension#tmp_dir is called, a temp directory specifically for the extension will be created within ~/.ronin/tmp/, and the path of the new temp directory will be returned.

Upgrading

As always, the rubygem files for Ronin 0.3.0 are available on rubyforge.org. One can update Ronin using rubygems by simplying running:

$ gem update ronin

Likewise, one can also install Ronin using rubygems:

$ gem install ronin

Also, as of Ronin 0.3.0 all releases of Ronin will also be made available on gemcutter.org.

Package Switching Vs. TCP/IP

Founded in 1969 the Pentagon’s Advanced Research Projects Agency Network (or Arpanet) is where the creation of the internet is said to have taken place, however it’s intention was not to link people of to share information on a global scale, instead it was used for time sharing. This was to enable research institutions to use the power of other institution’s computers when performing large calculations or when another faculty had the ability to do the job better.

Prior to the existence of ARPANET an Englishman by the name of Donald Davies developed a concept known as packet switching (data transmission in which a message is broken into parts and reassembled at the destination. – source; www.askoxford.com). This is something ARPANET developed a variation of in 1969. Even though there were others in the USA developing their own packet switching techniques (Leonard Kleinrock and Paul Baran), it was the English version which ARPANET first adopted.

We can come to the reasonable conclusion that they initially failed in their intentions, however they did make some important discoveries along the way such as email developments, packet switching implementations, and the development of the (Transport Control Protocol – Internet Protocol) or TCP/IP, although TCP was not officially added to ARPANET unwil 1983.

Many would say the development of package switching is then the internet was officially born, on the other hand there are those who argue that TCP is the backbone of what we call the internet today and so therefore is what the internet really is.

Tim Berners-Lee

Source - www.tw.rpi.edu/launch/img/lee.jpg

If you were to go up to anyone in the street and ask who Mr Berners-Lee was, the majority would simply shrug their shoulders and continue their zombie like trance whilst starring into their blackberry/iphone checking their emails without even realizing that without this man checking your emails, using apps from the istore or browsing the interet from the comfort of a coffee shop (to name but a few of the possibilities) would not be possible.

During the 1980s whilst working for CERN (now known as the European Particle Physics Laboratory but still called CERN for old time sake) Berners-Lee developed his first hypertext system. In 1984 he joined the group full-time and began seeking a hypertext project approved for official funding which he finally got five years later in 1989. The  purpose behind this project was to help those of the High Energy Physics department at CERN who were having problems sharing information across a wide range of different networks, computers, and countries.

It was a year later that the program “WorldWideWeb” was available within CERN in December 1990 and then in the summer of 1991 it was on “the internet”. In the early ninties he contiuned his work on the design of the web which produced further developments of his earlier work on HTML, HTTP and URLs.

Through the years the internet has undergone many drastic changes which some see as improvements, others say differently, yet one fact remains – the internet is constantly evolving as the needs and desires of humans changes progressively through time. As long as we keep changing, so too will our internet.

Above – Tim Berners Lee discusses the freedom of the internet.

First World Software provides greater efficiency and more competitive operations, with benefits such as:

Reduced Costs

With the rise in costs of outsourcing and the current economy, First World will give you a competitive edge on the marketplace.

Scalable Professional Resources

From one to many, your project will have the number of top technology professionals that it needs to be completed on time in a cost effective manner. No need for you to have staff all year long that you only need for a few weeks. Complete projects faster with a larger IT development team ready to work when you need them.

Direct Management

Our clients choose First World Software because they prefer hands-on control through the development life cycle of their projects. Instead of relinquishing control to an outsourcing firm who does not understand your business as you do, First World Software allows your knowledge and direction to influence more effectively the development process.

English Language

All of our professionals are fluent in English. We pride ourselves in “Made in America”, there is no outsourcing to offshore software services.

Key Professional Talent

As companies look for a way to set themselves apart, they soon realize that the key to being at the top is to have stellar talent. With First World Software, you will have access to a rich supply of talented, quality professionals with diverse experience and skill sets.

Increased Company Profitability

With increased development resources at an affordable price, and faster development periods, First World Software clients can significantly increase profitability.

In short, First World Software provides Power, Speed, Flexability, Experience and Affordable Service to You.

Um dos criminosos mais procurados do Rio, o traficante Ney da Conceição Cruz, o Facão, 37 anos, foi preso em Guarujá, no litoral de São Paulo, por agentes da Superintendência de Inteligência do Sistema Penitenciário (Sispen), subordinada à Secretaria de Estado de Administração Penitenciária.

Evadido do Sistema Penal desde o último 13 de abril, quando recebeu do juiz o benefício de trabalho extramuros, Facão vinha sendo monitorado há cerca de um mês – através de escutas telefônicas autorizadas pela promotora Valéria Videira Costa, titular da 21ª Promotoria de Investigação Penal (PIP) e chefe do Núcleo de Monitoramento do Sistema Penitenciário no Ministério Público.

A equipe da Sispen, após identificar que ele se encontraria com a esposa no Centro do Guarujá, se deslocou para a cidade paulista e conseguiu prendê-lo no meio da rua. O criminoso não estava armado e também não resistiu à prisão. A mulher dele foi liberada. Segundo informações do órgão, o traficante acertava com a esposa a compra de um imóvel para que ela e os dois filhos se instalassem definitivamente no município do litoral de São Paulo.

O secretário de Estado de Administração Penitenciária, César Rubens Monteiro de Carvalho, reforçou a importância do Setor de Inteligência Penitenciária e ressaltou a importância da prisão.

“A Inteligência em qualquer segmento é importantíssima. Não temos que ficar brigando por domínio de equipamentos. Qualquer instituição séria pode ter recursos necessários para combater o crime. A prisão chegou em um momento muito importante, já que se questionava a existência da Sispen, que sempre apoiou o Ministério Público na elucidação de grandes delitos. A prisão do criminoso representa um baque significativo, já que ele e o Matemático (Márcio José Sabino Pereira, que também recebeu o mesmo benefício e não retornou ao presídio) queriam dar uma estrutura à facção criminosa com maior controle, o que seria um risco para a sociedade. Nosso próximo objetivo é o Matemático”, enfatizou César Rubens.

Durante uma entrevista coletiva, o secretário foi questionado sobre a progressão de regime de presos de alta periculosidade, como Facão – que obteve na Justiça o benefício de trabalho extramuros, após conseguir uma vaga como auxiliar administrativo em uma empresa chamada ADG Comércio de Metais e Ferragens Ltda., em Bonsucesso.

“Os critérios para avaliação da concessão de um benefício aos presos existem. Mas, na nossa concepção deveriam ser iguais a alguns países onde determinados presos começam e terminam a pena no mesmo regime. Entendemos que presos de alta periculosidade, se condenadas ao regime fechado, devem cumprir a pena integralmente. Nós somos a favor da ressocialização, da reintegração, da remissão da pena, mas a progressão automática deve ser repensada pela sociedade. Os magistrados, às vezes, ficam reféns das leis que vigem hoje. Eles não podem interferir na lei. Ninguém está acima da lei”, ressaltou.

Leia mais sobre o Facão:

Traficante teria se submetido à cirurgia plástica

____________________________________________________

Quer concorrer a ingressos do filme “Tá chovendo hambúrguer” ??

Saiba Mais Aqui: Brindes e Promoções para os Leitores