Yassine El Houm Weblog

GWT-Ext is a powerful widget library that provides rich widgets . It uses GWT and Ext.

Hello there ,

I think the best way to Do a CVS ( Concurrent versions system )  are using a CMS(Blog) on your local web server, like ” WordPress ” by creating categories (your projects) and writing articles every update  ( what did you do on this update ?) and joining a zipped file of your updated project , doing this you got a lovely version control system

1- you can find it easily ( tag , date , categories (project name))

2- clients , colleagues or project manager can comment your update

…

Data staging

Most data in OLAP applications originates in other systems. However, in some applications (such as planning and budgeting), the data might be captured directly by the OLAP application. When the data comes from other applications, it is usually necessary for the active data to be stored in a separate, duplicated, form for the OLAP application. This may be referred to as a data warehouse or, more commonly today, as a data mart. For those not familiar with the reasons for this duplication, this is a summary of the main reasons:

Performance
OLAP applications are often large, but are nevertheless used for unpredictable interactive analysis. This requires that the data be accessed very rapidly, which usually dictates that it be kept in a separate, optimized structure which can be accessed without damaging the response from the operational systems.

Multiple data sources
Most OLAP applications require data sourced from multiple feeder systems, possibly including external sources and even desktop applications. The process of merging these multiple data feeds can be very complex, because the underlying systems probably use different coding systems and may also have different periodicities. For example, in a multinational company, it is rare for subsidiaries in different countries to use the same coding system for suppliers and customers, and they may well also use different ERP systems, particularly if the group has grown by acquisition.

Cleansing data
It is depressingly common for transaction systems to be full of erroneous data which needs to be ‘cleansed’ before it is ready to be analyzed. Apart from the small percentage of accidentally mis-coded data, there will also be examples of optional fields that have not been completed. For example, many companies would like to analyze their business in terms of their customers’ vertical markets. This requires that each customer (or even each sale) be assigned an industry code; however, this takes a certain amount of effort on the part of those entering the data, for which they get little return, so they are likely, at the very least, to cut corners. There may even be deliberate distortion of the data if sales people are rewarded more for some sales than others: they will certainly respond to this direct temptation by ‘adjusting’ (ie distorting) the data to their own advantage if they think they can get away with it.

Adjusting data
There are many reasons why data may need adjusting before it can be used for analysis. In order that this can be done without affecting the transaction systems, the OLAP data needs to be kept separate. Examples of reasons for adjusting the data include:

• • Foreign subsidiaries may operate under different accounting conventions or have different year-ends, so the data may need modifying before it can be used.
  • The source data may be in multiple currencies that must be translated.
  • The management, operational and legal structures of a company may be different.
  • The source applications may use differenrt codes for products and customers.
  • Inter-company trading effects may need to be eliminated, perhaps to measure true added value at each stage of trading.
  • Some data may need obscuring or changing for reasons of confidentiality.
  • There may be analysis dimensions that are not part of the operational data (such as vertical markets, television advertising regions or demographic characteristics).

Timing
If the data in an OLAP application comes from multiple feeder systems, it is very likely that they are updated on different cycles. At any one time, therefore, the feeder applications may be at different stages of update. For example, the month-end updates may be complete in one system, but not in another and a third system may be updated on a weekly cycle. In order that the analysis is based on consistent data, the data needs to be staged, within a data warehouse or directly in an OLAP database.

History
The majority of OLAP applications include time as a dimension, and many useful results are obtained from time series analysis. But for this to be useful it may be necessary to hold several years’ data on-line in this way — something that the operational systems feeding the OLAP application are very unlikely to do. This requires an initial effort to locate the historical data, and usually to adjust it because of changes in organizational and product structures. The resulting data is then held in the OLAP database.

Summaries
Operational data is necessarily very detailed, but most decision-making activities require a much higher level view. In the interests of efficiency, it is usually necessary to store merged, adjusted information at summary level, and this would not be feasible in a transaction processing system.

Data Updating
If the application allows users to alter or input data, it is obviously essential that the application has its own separate database that does not over-write the ‘official’ operational data.

Continuer la lecture ‘OLAP architectures’

L’API Ext 2.0 est très vaste , se souvenir de toutes les fonctions, propriétés ou des configurations disponibles est pratiquement impossible. La documentation de l’API est très poussé, mais il serait bien que si Des IDEs permettrait d’assister a fournir du code en javascript comme ils le font dans d’autres langages tels que Java et C #. Heureusement, il existe des IDE et plugins disponibles avec aussi un soutien direct de Ext 2.0 .

Voici quelques-uns :

Aptana Studio :

Spket Eclipse Plugin & IDE

Komodo Edit

SpketDW (Dreamweaver MX 2004 or higher)

3G Mobile Network Security

White Paper

Executive Summary

Mobile operators need to recognize their newfound role as internet service providers
(ISPs). No longer do they just provide cellular voice services; now they also provide highspeed Internet Protocol-based (IP) data services. So as to offer a wider array of services
and content to their data subscribers, mobile operators are opening up their formerly
closed networks to numerous other mobile operators, data networks and the public
Internet.

As a result, mobile operator’s 3G networks are not only exposed to all the virtual
pathogens already in circulation, but also to mobile-specific viruses and Trojans, as well as
to direct attacks such as Denial of Service (DoS) on their networks from hackers and/or
criminal organizations. These types of attacks employ methods which wired ISPs have
been dealing with for a much longer period of time. There are also variations on these
attacks which exploit weaknesses in the architecture and some of the protocols used in
2.5G/3G cellular data networks.

To protect their networks and customers, then, mobile operators need to:

. Take an architecture approach to implementing security solutions in their network;
point solutions are not sufficient

. Deploy a variety of products in their networks, such as firewalls, intrusion
detection and prevention (IDP) and virtual private networks (VPNs)

. Make client-side anti-virus and firewall software readily available to their
subscribers who use data devices (e.g., feature phones with data capabilities,
smartphones, notebook computers)
Continuer la lecture ‘3g mobile network security whitepaper’

Le spoofing ARP est un type de spoofing très simple à mettre en oeuvre. Sa puissance vient du fait qu’il permettra d’obtenir une connection TCP active (blind spoofing). Il repose sur la couche 2 du modèe OSI (liaison).  s’appliquer qu’à des réseaux du fait même du protocole ARP. Dans cette article je vais expliquer comment réaliser un spoof grâce à ARP et aussi les moyen pour lutter contre ce type d’attaque.

Man in the middle attack

Denial of Service

Solution :

Il existe une méthode très simple pour pouvoir se prémunir du spoofing ARP, il suffit d’enregistrer de manière statique les adresse MAC des cartes réseaux. Une autre méthode pour se prémunir, essentiellement si l’on se trouve dans un réseau hétérogène est d’utiliser le programme ARPWATCH. Cette utilitaire vous informe par email dès qu’une adresse IP change d’adresse MAC. On peut télécharger ARPWATCH à http://ftp.su.se/pub/security/tools/audit/arpwatch/arpwatch-1.7.tar.gz

voici quelques démonstration de cette magnifique distribution linux :

WPA2 or WPA Hack with Backtrack V3

WEP Crack w/ Backtrack 2

Solution :

la configuration d’un Freeradius/TLS & PEAP (avec des certificats générés par openssl et windows2000) pour des clients winxp et linux .en gros une WPA/TLS authentication.
voici quelques liens :

http://oriol.joor.net/blog/?itemid=1631
http://www.dslreports.com/forum/remark,9286052%7Emode=flat
http://www.freeradius.org/doc/EAPTLS.pdf