Tester Jobs Requirements (VIDEO GAME)

Vente a crear tecnología con nosotros en Telefónica We are hiring at LUCA D3 11Paths 4th Platform AURA

Figura 1: We are hiring at LUCA D3, 11Paths, 4th Platfom & AURA

Figura 2: Resumen de posiciones abiertas

Figura 3: Jobs at Telef�nica en el �rea de Inteligencia de Negocio y Big Data

Ya sabes que en nuestros equipos esto va de crear clavos, de hacer tecnolog�a, y de pas�rselo bien. Eso s�, te prometo que vas tener deadlines, que hacer deliveries, que lo que crees es para que sea utilizado, y que te vamos a pedir que lo hagas mucho mejor cada d�a. Si buscas un trabajo en el que no te vayas a ver retado y se te vaya a exigir que seas mejor cada d�a... este NO es tu sitio.

Figura 4: Vente a crear tecnolog�a a la f�brica de caramelos

Sigue Un inform�tico en el lado del mal - Google+ RSS 0xWord

download file now

TinyCore A Mighty Platform Part 2

TinyCore Linux is an ideal platform for building a light weight forensics distribution with the purposes I have in mind (See Part 1 of this post).  It is only a 10mb download for the base distribution and boots to a simple GUI desktop.  It boots and loads entirely into a ram disk as small as 48mb, but allocates as much ram as possible.  The ram disk makes TinyCore very fast because the entire operating system resides in ram and there are no drive seek time delays.

TinyCore uses a modern kernel with good hardware support and an xvesa video driver which all but insures a working GUI.  Applications are installed as modules (called extensions) that can be run at boot time or on demand.  The root file system and the applications are read-only and are renewed on every boot eliminating file corruption that can creep into installed software.

The Basic Structure

At its most rudimentary level, TinyCore consists of two files, the kernel (bzimage) and a compressed file system (tinycore.gz).  Add to that a means to boot the operating system, such as isolinux, and your full file tree is a simple:

./boot
./boot/isolinux
./boot/isolinux/isolinux.cfg
./boot/isolinux/isolinux.bin
./boot/isolinux/f4
./boot/isolinux/f2
./boot/isolinux/boot.msg
./boot/isolinux/f3
./boot/isolinux/boot.cat
./boot/bzImage
./boot/tinycore.gz

Making the Read-Only Environment

Attached storage devices detected by the kernel are identified by the udev daemon. Udev applies rules to the devices based on their type.  In the case of TinyCore, udev calls the /usr/sbin/rebuildfstab script to build the /etc/fstab file which contains the mounting options for the attached devices.  When the device is subsequently mounted (devices are not automatically mounted in TinyCore when attached), the mount options in the fstab file are applied.  One need only modify rebuildfstab mounting options to make the system mount devices read-only.

I have been able to modify the rebuildfstab file to mount devices read only and address other forensic mounting issues, like mounting ext3/4 devices as ext2 to avoid any possible journal changes and mounting physical devices as loopback devices to avoid attempted repairs of corrupted file systems on mount.

The process of modifying, adding, or removing files in the core file system is well documented here.  It involves decompressing the tinycore.gz file extracted from a TinyCore iso, making the desired changes, and zipping it back up.  The new tinycore.gz can then be remastered into a new iso.

Making Application Modules (Extensions)

Though new applications can be remastered into the core file system, I favor the modular approach implemented by the TinyCore developers.  Applications are compiled and the stored in a read-only squashfs file system.  The application, when installed, is mounted into the core file system.  Applications can be triggered to mount at boot time, or on demand.  On demand ensures quicker boot times and frees more space in the ram disk if the application is not needed in the session.  Though there is not gui method for this, installed applications can be "uninstalled" in the middle of the session by simply unmounting them and thus freeing ram allocated to them.

Though TinyCore has some suitable modules for forensics, like foremost for example, it lacks libraries and application such as libewf (Expert Witness imaging format), afflib (Advanced Forensics imaging Format), and sleuthkit (disk investigation tool) that a forensics practitioner would desire.  If you are familiar with building application from source, however, then building TinyCore application modules is a snap.  I have already built libewf, afflib, aimage, and sleuthkit modules and will submit them to the repository once I complete testing.  You can take a look at the building method here.

Persistence

Everything Ive mentioned about TinyCore so far mentions "read-only."  The rebuildfstab script can be modified to ensure devices are mounted read-only, a must for live forensic examinations.  The core file system and application modules are mounted read-only ensuring a "clean" operating system and software environment with each boot.  But how does a user save evidence from examinations?

TinyCore allows the home directory to be saved to a storage device.  On shutdown, user data is written to the storage device designated by the user.  A boot option allows the device to be specified on the next boot to restore the user data, or it can be loaded after boot.

Putting it All Together

If you read Part 1 of this post, you know that my goal is the creation of a bootable disc/USB that an investigator with average computer skills (not a computer forensics practitioner) could use to search for and seize evidence from digital storage devices.  TinyCore, in my estimation, has it all:

1. Small size, loads entirely into ram, and fast with a simple GUI
2. Easily modified and remastered as a read-only environment
3. Easily add and created application modules with minimal ram impact
4. Means for easy creation and restoration of persistent storage

download file now

Download Mega Files Directly Through ADM or IDM All Platform

Le nostre guide sulla risoluzione di errori Android continuano, questa volta con lerrore 403 che come gi� visto con gli errori 906, 907, 963 e 905 si presenta nel Google Play Store.

Continuate nella lettura della guida per scoprire come fixare lerrore 403

download file now

TinyCore A Mighty Platform Part 1

Last week I rediscovered TinyCore Linux.  I had taken a look at it about 6 months ago and was intrigued, but didnt have the time to explore it further.  However, I have been seeking a small Linux distribution on which to build a specialized forensics distro, and last week I gave TinyCore another look.

Background

I believe there is a need in computer forensics for an investigator with limited training to be able to search for and seized digital evidence from storage devices.  Some of the reasons I believe this are:

1. There are not enough trained forensic computer examiners to keep pace with the number of cases involving digital evidence.
2. The backlog created by a lack of examiners means cases dont get filed for month or even years after the discovery of the crime.  Meanwhile, the perpetrator is free to commit more crimes.
3. Prosecutors are less likely to pursue older cases, in part because witness recall becomes unreliable.
4. The majority of charges filed against perpetrators are settled out of court through plea bargaining.  

1. Boot quickly (Criminal investigators may be in the field without the luxury of time.
2. Work in nearly any machine (basic video drivers, e.g., xvesa)
3. Not alter the media being examined (i.e., mount devices read-only)
4. Create an writeable storage location automatically (no command line or confusing the evidence device for the storage device)
5. Contain programs or scripts that are easily accessible to find evidence files (e.g., nautilus-scripts)
6. Create reports about files saved as evidence containing file metadata (so evidence can be commented upon by trained investigators, if needed)
7. Allow for the creation of forensic images (in the event the device cannot be seized).

download file now

Geekbench 4 Cross Platform Testing Analysis

Overview

Geekbench 4 was released at the end of August and has proved to be a welcome improvement over the previous revision 3, having been praised for accurately reflecting the industry standard SPEC results through a benchmark suite that is readily available on different platforms and is easy and quick to run.

As Geekbench 4 is comparable across platforms and is available for Windows, Android, iOS and others, I thought it would be interesting to test my server, desktop, laptop, tablet and phone to see how they perform relative to each other.

I am also interested in how different processors compare across platforms, so compare the scores of the fastest processors available in different platforms and segments, including the fastest Core i7, Core M, Apple A10 and Exynos 8890 / Snapdragon 820 on Android.

Single vs Multi-core scores

Before getting to the results of my test, it is worthwhile discussing the two results that are returned from the benchmark - the Single and Multi-core values

The Single-Core result provides a ranking of which processor has the fastest CPU core in a single threaded situation. Having a fast core indicates that an application will perform well in single-threaded situations. Writing well-threaded applications is more long winded and complex than writing a traditional single-threaded application, so developers are unlikely to put in the extra effort required unless a performance issue crops up in their testing, or their application is particularly suited to multi-threading.

The Multi-Core result shows what can be achieved if an application is both suited to, and optimised for, a multi-threaded environment. The Operating system itself and many core applications are generally well threaded and will take advantage of multi-core processors. Applications and Services running in the background also make good use of multiple cores.

Which result, therefore, is the most reflective of real world performance? Generally speaking, having a high single core score will ensure that all applications perform well, no matter how they are coded. Conversely, having more, slower cores may perform better in some situations but will also perform worse in others.

I would suggest, therefore, that having a high single core score will ensure performance consistency, and having a high multi-core score will show the maximum performance you can expect in ideal circumstances.

The operating system design also plays a part in this - the higher degree of true multi-tasking the OS provides, the more important the multi core score and the less important the single core. In terms of todays common platforms, the multi core score is most important in Windows, important in Android and less important in iOS.

In conclusion, neither the single or multi-core scores provide the whole picture - the real answer lies somewhere in the middle, with the bias being dependant on the host OS and the suite of applications you frequently use.

My Results

download file now