Lecciones Prácticas

Archive for the ‘Informática – utilidades internet’ Category

A modo de chuleta, una vez más, os pongo los pasos necesarios para trabajar con Eclipse, EGit y PyDev.

1. Instalar Eclipse Classic.

2. Iniciar Eclipse, y deberías ver una pantalla similar a:

3. Instalar PyDev desde Eclipse. Para ello, en la pantalla anterior, pulsa sobre la flecha de la derecha. Aparecerá una pantalla de este tipo:

A continuación ve al menú Help -> Install new software.

Selecciona “Add” y añade la siguiente URL en el campo “Location”:

http://pydev.org/updates

Selecciona la opción “PyDev for Eclipse”. No selecciones la opción “PyDev Mylyn Integration”. Solo queda pulsar “siguiente, siguiente, siguiente” y reiniciar eclipse.

4. Configurar PyDev desde Eclipse:
Ve al menú “window -> preferences”, expande “PyDev” y selecciona “Python Interpreter”. Deberías ver algo asi:

Debes añadir un nuevo intérprete, indicando la ruta donde tienes instalado python:

Selecciona todos MENOS el PySrc y python31.zip. Pulsa ok tantas veces como sea necesario y termina el proceso. Ya estás listo para programar en python usando eclipse.

5. Instalar EGit desde Eclipse
El proceso para instalar egit es muy similar al descrito en el paso 3, simplemente usa la siguiente url en el campo “location”:

http://download.eclipse.org/egit/updates

6. Escribiendo tu primer programa python:
Ve al menú “Window > Open Perspective > Other…” y elige “Pydev”, entonces haz click en ‘ok’. Si te fijas en la esquina superior derecha verás que la perspectiva ha cambiado de “java” a “pydev”

7. Creando un proyecto nuevo:
Ve a “File > New > Pydev Project” para empezar un asistente.
En la siguiente pantalla, introduce el nombre del proyecto y selecciona como tipo “python 3.0″. Asegúrate de que las opciones “create default ‘src’ folder” y “add it to the pythonpath?” están seleccionadas. Haz click en Finish.

8. Creando un módulo nuevo:
“File → New → Pydev Module”

Si miras en el “Package Explorer” verás un icono con tu nuevo fichero dentro de la carpeta ‘src’ (carpeta que creó Eclipse cuando hiciste el proyecto en el paso anterior).

9. Ejecución de tu primer programa:
Vamos a hacer un “hello world” en python. Para ello simplemente escribe print(‘Hello, World!’) en tu fichero. Guárdalo (ctrl+S) y para ejecutarlo, simplemente ve a “run as > python run”:

10. Añadir tus ficheros a repositorio GIT:

Seleccionado el proyecto que deseamos añadir, pulsamos botón derecho y “Team -> Share Project”

Marcamos la opción GIT y pulsamos “next”:

Seleccionamos el proyecto a añadir y pulsamos Create para crear el nuevo repositorio GIT:

A continuación pulsamos “Finish”:

El proyecto está marcado ahora con el texto “[MASTER]“, que indica que los ficheros pertenecen a la rama principal del repositorio GIT. Los interrogantes al lado de algunos archivos (en la imagen los archivos .classpath y .project) indican que esos archivos no pertecen aun al repositorio git:

Para hacer que pertenezcan (y se cambie el interrogante por un signo “+”) debemos trackear el proyecto. Para ello seleccionamos el proyecto, botón derecho, “Team > Track”

Es muy probable que tengamos ficheros que NO deseemos que se añadan al track. Para ello creamos un fichero llamado .gitignore e introducimos aquéllos ficheros que NO deseamos que pertenezcan. Imaginemos que todos ellos estan en una carpeta llamada ignoredfolder. Pues en el fichero .gitignore escribiremos ignoredfolder. A continuación añadimos .gitignore al control de versiones.

Podemos añadir exclusiones más generales (por ejemplo si nuestra configuración de una BD, nombres de usuarios y passwords estan en un fichero llamado .settings en todos nuestros proyectos, o queremos excluir todos los ficheros .zip) podemos utilizar el menu: Preferences > Team > IgnoredResources

Ahora debemos hacer un commit de los cambios. Para ello Team > Commit:

Debes insertar un mensajes explicando tus cambios. La primera linea (separada por una linea en blanco) se convertirá en el “short log” para este commit. Por defecto el autor y el committer se cogen del fichero .gitconfig de tu directorio home del proyecto. Puedes, además, marcar “Add Signed-off-by” para añadir un tag Signed-off-by. Al enviar cambios de otros autores puede ser conveniente alterar el campo autor para insertar los datos de nombre y mail del autor. Pulsa commit para enviar los cambios.

Ahora han cambiado los “+” que aparecían al lado de los archivos por otro icono:

Para mostrar el HISTORIAL de un fichero, puedes pulsar botón derecho y luego “Team > Show Local History”:

Esto es lo básico. Podéis leer mucho más en los enlaces de abajo

___________
Más información sobre pydev y eclipse (en inglés) en http://www.rose-hulman.edu/class/csse/resources/Eclipse/eclipse-python-configuration.htm.

Más información sobre egit para eclipse (en inglés) en http://wiki.eclipse.org/EGit

Currently I am attending a workshop on Designing Secure Wep Apps and there I learned about Burp suite and Foxy proxy (standard).

What is Burp Suite?

Burp Suite is an integrated platform for attacking web applications. It contains all of the Burp tools with numerous interfaces between them designed to facilitate and speed up the process of attacking an application. All tools share the same robust framework for handling HTTP requests, persistence, authentication, upstream proxies, logging, alerting and extensibility.

Burp Suite allows you to combine manual and automated techniques to enumerate, analyse, scan, attack and exploit web applications. The various Burp tools work together effectively to share information and allow findings identified within one tool to form the basis of an attack using another.

Key features unique to Burp Suite include:

* Detailed analysis and rendering of requests and responses.
* One-click transfer of interesting requests between tools.
* Site map showing information accumulated about target applications in tree and table form.
* Ability to “passively” spider an application in a non-intrusive manner, with all requests originating from the user’s browser.
* Suite-level target scope configuration, driving numerous individual tool actions.
* Fully fledged web vulnerability scanner. [Pro version only]
* Ability to save and restore state. [Pro version only]
* FIPS-compliant statistical analysis of session token randomness.
* Utilities for decoding and comparing application data.
* A range of engagement tools, to make your work faster and more effective. [Pro version only]
* Suite-wide search function. [Pro version only]
* Support for custom client and server SSL certificates.
* Extensibility via the IBurpExtender interface.
* Centrally configured settings for upstream proxies, web and proxy authentication, and logging.
* Tools can run in a single tabbed window, or be detached in individual windows.
* Runs in both Linux and Windows.

What is Foxy Proxy?

FoxyProxy is a set of proxy management tools for Firefox, Thunderbird, Seamonkey, and Songbird. There are three editions available (basic, standard, plus). Both basic and standard are free. I use standard.

More coming next days!

De cara al desarrollo de aplicaciones es muy interesante tener algún software de control de versiones, tipo Subversion o GIT.

Os comento a modo de “chuleta” cómo hacer esto desde las fuentes.

Para ello, algunas consideraciones preliminares:

Servidor y SO: Linux myserver.com 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Archivos de código: /soft/cds-invenio
Versión de GIT: git-1.6.6.2 (instalado desde las fuentes)

Asumo que la instalación de GIT es simple y podéis hacerla vosotros mismos sin ayuda. Hay muchísimos manuales indicando cómo hacerlo (usad google).

Una vez instalado GIT, procedemos:

# Creamos el archivo de configuracion del gitweb....
[root@aneto cds-invenio]#vi /etc/gitweb.conf
# ----------------------------------------------------------------------------
#
# gitweb.conf
#
# Configuration file for the web interface to GIT.
#
# This file is a Perl script that is executed by the gitweb interface
# after the defaults are set.  To override a setting, just uncomment
# it here and set it to the appropriate value.
#
 
# Core git executable to use.
# This can just be "git" if your webserver has a sensible PATH.
#our $GIT = "/path/to/git";
 
# Absolute fs-path which will be prepended to the project path.
# This is where your GIT repositories live in.
# ESTA VARIABLE ES FUNDAMENTAL!!!
our $projectroot = "/soft/git";
 
# Target of the home link on top of all pages.
#our $home_link = $my_uri || "/";
 
# String of the home link on top of all pages.
our $home_link_str = "view projects";
 
# Name of your site or organization to appear in page titles.
# Replace this with something more descriptive for clearer bookmarks.
#our $site_name = ""
 
# Filename of HTML text to include at top of each page.
# Must be an absolute filename (i.e., not relative to htdocs).
#our $site_header = "";
# HTML text to include at home page.
# Must be an absolute filename (i.e., not relative to htdocs).
#our $home_text = "/gitweb/indextext.html";
# Filename of HTML text to include at bottom of each page.
# Must be an absolute filename (i.e., not relative to htdocs).
#our $site_footer = "";
 
# URI of the stylesheet to use.
our $stylesheet = "/git/gitweb.css";
# URI of GIT logo (72x27 size).
our $logo = "/git/git-logo.png";
# URI of GIT favicon, assumed to be image/png type.
our $favicon = "/git/git-favicon.png";
 
# URI and label (title) of GIT logo link.
#our $logo_url = "http://git.or.cz/";
#our $logo_label = "git homepage";
 
# Source of projects list.
#our $projects_list = "";
 
# Show repository only if this file exists.
# Only effective if this variable evaluates to true.
#our $export_ok = "";
 
# Only allow viewing of repositories also shown on the overview page.
#our $strict_export = "";
 
# List of git base URLs used for URL to where fetch project from,
# i.e. full URL is "$git_base_url/$project"
#our @git_base_url_list = grep { $_ ne '' } ("/some/url");
# --------------------------------------------------------------------------------

Entonces añadimos al archivo de configuración de Apache algunas líneas útiles (el directorio /var/www/cgi-git/gitweb y /var/www/html/git deben existir):

[root@aneto cds-invenio]# vi /etc/httpd/conf/httpd.conf
# Añadir:
Alias /gitweb "/var/www/cgi-bin/gitweb/"
<Directory "/var/www/cgi-bin/gitweb">
            Options Indexes FollowSymlinks ExecCGI
            AllowOverride None
            Order allow,deny
            Allow from all
</Directory>
Alias /git "/var/www/html/git"
<Directory "/var/www/html/git">
            Options None
            AllowOverride None
            Order allow,deny
            Allow from all
</Directory>

Y procedemos a reinicar apache y crear el nuevo repositorio GIT…

[root@aneto cds-invenio]#/etc/init.d/httpd restart
 
[root@aneto cds-invenio]# cd /soft/cds-invenio
[root@aneto cds-invenio]# git init
[root@aneto cds-invenio]# git add .
[root@aneto cds-invenio]# git commit -m "inicialización del repositorio"

Una vez hecho esto, editamos algunos archivos de los que GIT ha creado (añadir información a ‘description’ y a ‘config’).

[root@aneto cds-invenio]# vi /soft/cds-invenio/description 
[root@aneto cds-invenio]# vi /soft/cds-invenio/config
--------------------------------------------------------
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
        worktree = /soft/cds-invenio
        owner = "Miguel Martin"

A continuación clonamos sólo los datos de GIT en un fichero .git:

[root@aneto cds-invenio]# cd /soft/cds-invenio/
[root@aneto cds-invenio]# git clone --bare cdsinvenio cdsinvenio.git

Podemos probar a cargar en nuestro servidor esta url: http://myserver.com/cgi-bin/gitweb.cgi y ver si aparece algo… Puede que se produzcan fallos con gitweb.js si está en el directorio /cgi-bin/gitweb… si es el caso podemos editar gitweb.cgi y modificar la RUTA al gitweb.js.

# Editamos el gitweb.cgi porque hay fallos en el JS:
[root@aneto cds-invenio]# vi /var/www/cgi-bin/gitweb/gitweb.cgi
 
 # URI of stylesheets
 our @stylesheets = ("/var/www/cgi-bin/gitweb/gitweb.css");
 # URI of a single stylesheet, which can be overridden in GITWEB_CONFIG.
 our $stylesheet = undef;
 # URI of GIT logo (72x27 size)
 our $logo = "/var/www/cgi-bin/gitweb/git-logo.png";
 # URI of GIT favicon, assumed to be image/png type
 our $favicon = "/var/www/cgi-bin/gitweb/git-favicon.png";
 # URI of gitweb.js (JavaScript code for gitweb)
 our $javascript = "/git/gitweb.js";
 
 # URI and label (title) of GIT logo link
 #our $logo_url = "http://www.kernel.org/pub/software/scm/git/docs/";
 #our $logo_label = "git documentation";
 our $logo_url = "http://git-scm.com/";
 our $logo_label = "git homepage";

Y ahora copiamos el js a su lugar…

#Copiamos el Js a /var/www/html/git
cp /var/www/cgi-bin/gitweb.js /var/www/html/git/

# Hacemos un PUSH de todo…
[root@aneto teresa]# git push –all /soft/git/cdsinvenio.git

Y voilá! Nuestro repositorio git con todo accesible desde http://myserver.com/cgi-bin/gitweb.git

Algunos enlaces interesantes…
link 1 (en)
link 2 (en)
link 3 (es)
link 4 (es)

We are developing a photographic website (with an SMF 2.0 RC3 forum) and most of our users have their photos hosted in Flickr.

(Note: I have installed WYSIWYG Quick Reply v2 RC3 package)

So I’d like to make their lifes easier when sharing their photos by adding a custom button (here in the post wysiwyg editor) which converts this html structure (the code snippet flickr shows to the user):

<a href="URL1" title="this_is_the_title"><img src="IMGURL" width="342" height="500" alt="alt_text" /></a>

To something like:

[url=URL1][img]IMGURL[/img][/url]

How to do this?

* Edit your Themes/default/GenericControls.template.php
* Locate:

function template_control_richedit($editor_id, $smileyContainer = null, $bbcContainer = null)
{
	global $context, $settings, $options, $txt, $modSettings, $scripturl;
 
	$editor_context = &$context['controls']['richedit'][$editor_id];

* Add after:

?>
	<script language="javascript">
	    function convierteCode(){
	    	// dado un codigo tipo flickr lo convierte a BBCode (def en GenericControls.template.php)
                        var flickr = document.getElementById("flickrcodeinput").value;
			flickr = flickr.replace('<a href="','[url=');
			flickr = flickr.replace('" /></a>','[/img][/url]');
			flickr = flickr.replace(/"(.)+title(.)*><img(.)+src="/,'][img]');
			flickr = flickr.replace(/"(.)+width(.)*\[/,'[');
			flickr = flickr.replace('[/url]','[/img][/url]');											 
			document.getElementById("message").value += flickr;
			window.frames[0].document.write(flickr);
	    }
	</script>
<?php

*Locate:

echo '
		<div>
			<div>
				<textarea class="editor"

* Replace with:

echo '
		<div>
			<div>
			    <!-- flickr input and button-->
                               <input type="text" id="flickrcodeinput" width="100px"></input>&nbsp;
                               <input type="button" value="Inserta IMG flickr" onClick="convierteCode();"></input>
                               <br /><br />
                            <!--flickr input and button end -->
				<textarea class="editor"

* Upload the new GenericControls.template.php

(Note for curious people: I also tried this by adding a custom button which would produce a new bbcode like [flickr][/flickr] and blahblahblah, but I could not make it work. More details here)

Currently, only up to 500 rows of Analytics table data can be exported at a time into CSV format. If you need to export larger data sets, like exporting all keywords that sent traffic to your site, you can export multiple times as long as each batch contains at maximum 500 rows.

If you have thousands of rows that require multiple exports, you can use the convenient workaround below to export all your rows in one go.

1. Go the report that contains the data you want to export.

2. Append the query parameter ‘limit’ to the url (to the end of URL!), and hit enter to reload the report. The limit parameter is needed prior to every report export.
For example:

3. Hit ‘Enter’ and visually confirm that the report now has the new parameter appended to it. While there won’t be any visible difference in user interface, exporting will now yield more rows.

4. Select the Export tab, and click ‘CSV’ (not the option that says ‘CSV for Excel’).
5. The exported data should contain all the rows from your Analytics table.

Via: Google Analytics FAQ’s

httpwatch is an HTTP viewer and debugger that integrates with IE and Firefox to provide seamless HTTP and HTTPS monitoring without leaving the browser. This kind of software is usually known as sniffer.

Why do you need an HTTP Viewer or Sniffer?

All web applications make extensive use of the HTTP protocol (or HTTPS for secure sites). Even simple web pages require the use of multiple HTTP requests to download HTML, graphics and javascript. The ability to view the HTTP interaction between the browser and web site is crucial to these areas of web development:
* Troubleshooting
* Performance tuning
* Verifying the security of a site

How can HttpWatch help?

HttpWatch integrates with Internet Explorer and Firefox browsers to show you exactly what HTTP traffic is triggered when you access a web page. If you access a site that uses secure HTTPS connections, HttpWatch automatically displays the decrypted form of the network traffic.

Conventional network monitoring tools just display low level data captured from the network. In contrast, HttpWatch has been optimized for displaying HTTP traffic and allows you to quickly see the values of headers, cookies, query strings and more…

HttpWatch also supports non-interactive examination of HTTP data. When log files are saved, a complete record of the HTTP traffic is saved in a compact file. You can even examine log files that your customers and suppliers have recorded using the free Basic Edition.

OTRS is an Open source Ticket Request System (also well known as trouble ticket system) with many features to manage customer telephone calls and e-mails. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. Do you receive many e-mails and want to answer them with a team of agents? You’re going to love the OTRS!

It is distributed under the GNU Affero General Public License (AGPL) and tested on Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x and Windows.

The ((otrs)) company provides commercial services (e.g. support, consulting, training, prebuilt-systems, etc.) for the OTRS (English and German).

It is a great alternative to OSTicket.

I am currently testing this software and I will edit this post or create a new one comparing this two great programs.

edit: Almost forgot to share this full listing of opensource helpdesk / support / ticketing softwares.

The install process

There are several flavours of OTRS. For testing purposes only my choice was OTRS 2.4.7 for Windows.

Before installation my system already had a wamp installed. Wamp includes mysql, apache and php.

Anyway, OTRS tries to install a new instance of MySQL and Apache, if not present. I am not a big fan of this, to be honest.

Well, once the installation process is done (just press “continue, continue…”) a new icon is created in your desktop. Double clicking it leads to http://localhost/otrs/index.pl. And, of course, it crashes :-/

This has to do with the Kernel/Config.pm default configuration to access MySQL database. More precisely, to this lines:

1
2
3
4
5
6
7
8
9
10
11

    $Self->{DatabaseHost} = 'localhost';
    # Database
    # (The database name.)
    $Self->{Database} = 'otrs';
    # DatabaseUser
    # (The database user.)
    $Self->{DatabaseUser} = 'otrs';
    # DatabasePw
    # (The password of database user. You also can use bin/CryptPassword.pl
    # for crypted passwords.)
    $Self->{DatabasePw} = 'some-pass';

You must create a new user (called otrs), the database (otrs) and the access privileges. This can be done like:

mysql -h localhost -u root -p
# type your password when asked for it
 
mysql> CREATE USER otrs identified by 'otrs';
Query OK, 0 rows affected (0.00 sec)
 
mysql> CREATE DATABASE otrs;
Query OK, 1 row affected (0.00 sec)
 
mysql> GRANT ALL PRIVILEGES ON otrs.* to otrs@'localhost' identified by 'otrs';
Query OK, 0 rows affected (0.00 sec)
 
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

But there is a better way to do it, just calling the installer again and letting it do what it has to:
Re-run the installer. Open a web browser and type:

http://localhost/otrs/installer.pl

then restart your web server:

httpd.exe -k restart

Already installed, how do I log into the system?

Go to http://localhost/otrs/index.pl
Now you can access the backend with root@localhost / otrs.

If your web server uses PHP and you need to use IMAP take a look at this post.

When do i need to install IMAP support for PHP

If you want to use imap_open function you need to do it.

How do I check if my PHP is actually configured to use IMAP?

Two ways:
- Check the output of phpinfo(); info. More precisely, the additional .ini files parsed part. There should be something like /etc/php.d/imap.ini if you already have imap in your php.

- Make a doihaveimap.php like the following and run it:

<?php
if(!function_exists('imap_open'))
    echo "I DO have it installed";
else
    echo "I do NOT";
?>

I need to install it: how do I proceed?

My system is a
Linux 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux.

So I proceed with the installation using yum.

yum install libc-client.x86_64
yum install libc-client-devel.x86_64
yum install php-imap.x86_64
/etc/init.d/httpd restart

Does it work? How to check it

Write a simple php program like the following and run it.

Been there, done that… it does not work!

Most of us get this error:

Array ( [0] => [CLOSED] IMAP connection broken (server response) )

You should make a

telnet yourimapserver 143

If it does not connect, there you have the problem. Fix it before continue reading. If you are kind of desperate, read this post.

Well, lets suppose it connects but the “Invalid credentials” error message pops. Common mistakes are typos when defining username/password. Also check if the username must contain “@yourdomain.com”. Again, telnet is your friend. If it does not work in telnet it won’t work in php either…

Would you like to read more about PHP-IMAP? Check this link.

Do you need to install php-imap in another platform? Check this FTP

osTicket is a widely-used open source support ticket system. It seamlessly integrates inquiries created via email, phone and web-based forms into a simple easy-to-use multi-user web interface. Manage, organize and archive all your support requests and responses in one place while providing your customers with accountability and responsiveness they deserve.

osTicket is configured by default like the following: the client (user) fills in a form with information related to the issue he is having and then submits it. osTicket processes that info and shows it to the staff team so that the support can be given.

In our institution people are used to tell about their tech issues using email (suppose this email is support@yourinstitution.com) and we did not want to change this. So we thought there might be a trick to forward all the support@yourinstitution.com mails to osticket. And there is indeed!

There are two ways of achieving this:

1. Use pipes to forward the mails to osTicket system (original post talking about this and another post talking about this).

2. Configure osTicket to use POP/IMAP (check this post)

I have tried both options. The steps you should follow are:

OSTicket with pipes

Enable Email Piping:
Admin Panel -> Preferences -> Email Settings -> Enable Email Piping

chmod the file pipe.php in the api folder:

# cd /var/www/html/osticket/buz/api/
# chmod 764 pipe.php

Edit your aliases file

# vi /etc/aliases

and add the pipe line (supportusername is the name of the user to which the email will be forwarded):

supportusername: "|/usr/bin/php -q /var/www/html/osticket/buz/api/pipe.php"

Regenerate aliases file

# newaliases

Find php:

# whereis php
php: /usr/bin/php

Configure your email program (mine is sendmail). Spanish readers can refer to this sendmail guide

Enable your supportusername to run php:

#chmod 764 /usr/bin/php

Send an email to check it works:

# mail -s "Checking osticket piping" supportusername
This is a test
.
CC:

If something does not work as expected check the logs (tail -f -n 100 /var/log/maillog)

When everything is working as expected…
Forward your support@yourinstitution.com email to the server hosting osticket.

** Edit: I have noticed several problems with this configuration. When the emails are piped to osticket the headers are rewriten so the support staff does not know the client’s email!!

So I decided to try the IMAP configuration.

The IMAP/POP configuration

First of all, configure php-imap.

Then go to Settings -> Email Settings and:
For Incoming Emails:
* disable Enable email piping (You pipe we accept policy)
* enable Enable POP/IMAP email fetch (Global setting which can be disabled at email level)
For Outgoing Emails my config is like:
* Use PHP mail function

Now go to Email tab.
Create a new email account. Mine is configured as shown in the image:

————–NO REGALO INVITACIONES GRATIS A SPOTIFY, NO TENGO, NO ME ESCRIBAS UN EMAIL PIDIENDOME UNA.————————–
*** EDITADO 16/02/2010 *** Este método ya no funciona. Debido a la gran cantidad de peticiones formuladas el método ha dejado de ser válido.

¿Quieres una invitación a spotify? Para conseguir invitaciones a spotify de forma gratuita puedes visitar

http://www.qashqaiurbanlife.com/Login.aspx?redir=SpotifyInvitation.aspx

Allí, si te registras en qashqaiurbanlife, te mandan un código de invitación al email. Lo acabo de comprobar y funciona!