ClockWorkMod

ROM Manager is a Android front end to the Clockwork Recovery image.
http://www.clockworkmod.com/rommanager
http://www.clockworkmod.com/

ROM Manager is a Android front end to the Clockwork Recovery image.

http://www.clockworkmod.com/rommanager

http://www.clockworkmod.com/

Information Systems Security

The Open Source Security Testing Methodology http://www.isecom.org/mirror/OSSTMM.3.pdf The Information Systems Security Assessment Framework (ISSAF) seeks to integrate the following management tools and internal control checklists: Evaluate the organizations information security policies & processes to report on their compliance with IT industry standards, and applicable laws and regulatory requirements Identify and assess the business dependencies on […]


The Open Source Security Testing Methodology

Click to access OSSTMM.3.pdf


The Information Systems Security Assessment Framework (ISSAF) seeks to integrate the following management tools and internal control checklists:

Evaluate the organizations information security policies & processes to report on their compliance with IT industry standards, and applicable laws and regulatory requirements
Identify and assess the business dependencies on infrastructure services provided by IT
Conduct vulnerability assessments & penetration tests to highlight system vulnerabilities that could result in potential risks to information assets
Specify evaluation models by security domains to :
Find mis-configurations and rectify them
Identifying risks related to technologies and addressing them
Identifying risks within people or business processes and addressing them
Strengthening existing processes and technologies
Provide best practices and procedures to support business continuity initiatives

Business Benefits of ISSAF

The ISSAF is intended to comprehensively report on the implementation of existing controls to support IEC/ISO 27001:2005(BS7799), Sarbanes Oxley SOX404, CoBIT, SAS70 and COSO, thus adding value to the operational aspects of IT related business transformation programmes.
Its primary value will derive from the fact that it provides a tested resource for security practitioners thus freeing them up from commensurate investment in commercial resources or extensive internal research to address their information security needs.
It is designed from the ground up to evolve into a comprehensive body of knowledge for organizations seeking independence and neutrality in their security assessment efforts.

It is the first framework to provide validation for bottom up security strategies such as penetration testing as well as top down approaches such as the standardization of an audit checklist for information policies.


The Open Web Application Security Project (OWASP) is an open-source application security project. The OWASP community includes corporations, educational organizations, and individuals from around the world. This community works to create freely-available articles, methodologies, documentation, tools, and technologies. The OWASP Foundation is a 501(c)(3)charitable organization that supports and manages OWASP projects and infrastructure. It is also a registered non profit in Europe since June 2011.

OWASP is not affiliated with any technology company, although it supports the informed use of security technology. OWASP has avoided affiliation as it believes freedom from organizational pressures may make it easier for it to provide unbiased, practical, cost-effective information about application security.[citation needed] OWASP advocates approaching application security by considering the people, process, and technology dimensions.

OWASP’s most successful documents include the book-length OWASP Guide,[1] the OWASP Code Review Guide OWASP Guide [2] and the widely adopted Top 10 awareness document.[3][citation needed] The most widely used OWASP tools include their training environment,[4] their penetration testing proxy WebScarab,[5] and their .NET tools.[6] OWASP includes roughly 190 local chapters [7] around the world and thousands of participants on the project mailing lists. OWASP has organized the AppSec [8] series of conferences to further build the application security community.

OWASP is also an emerging standards body, with the publication of its first standard in December 2008, the OWASP Application Security Verification Standard (ASVS).[9] The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially workable open standards that are tailored to specific web-based technologies. A Web Application Edition has been published. A Web Service Edition is under development.

the OWASP Top Ten Project – if you’re looking for the OWASP Top 10 Mobile Click Here
The Release Candidate for the OWASP Top 10 for 2013 is now available here: OWASP Top 10 – 2013 – Release Candidate

The OWASP Top 10 – 2013 Release Candidate includes the following changes as compared to the 2010 edition:

  • A1 Injection
  • A2 Broken Authentication and Session Management (was formerly A3)
  • A3 Cross-Site Scripting (XSS) (was formerly A2)
  • A4 Insecure Direct Object References
  • A5 Security Misconfiguration (was formerly A6)
  • A6 Sensitive Data Exposure (merged from former A7 Insecure Cryptographic Storage and former A9 Insufficient Transport Layer Protection)
  • A7 Missing Function Level Access Control (renamed/broadened from former A8 Failure to Restrict URL Access)
  • A8 Cross-Site Request Forgery (CSRF) (was formerly A5)
  • A9 Using Known Vulnerable Components (new but was part of former A6 – Security Misconfiguration)
  • A10 Unvalidated Redirects and Forwards

Please review this release candidate and provide comments to dave.wichers@owasp.org or to the OWASP Top 10 mailing list (which you must be subscribed to). The comment period is open from Feb 16 through March 30, 2013 and a final version will be released in May 2013.

If you are interested, the methodology for how the Top 10 is produced is now documented here: OWASP Top 10 Development Methodology

OWASP Appsec Tutorial Series

Uploaded on Jan 30, 2011
The first episode in the OWASP Appsec Tutorial Series. This episode describes what the series is going to cover, why it is vital to learn about application security, and what to expect in upcoming episodes.

Uploaded on Feb 8, 2011
The second episode in the OWASP Appsec Tutorial Series. This episode describes the #1 attack on the OWASP top 10 – injection attacks. This episode illustrates SQL Injection, discusses other injection attacks, covers basic fixes, and then recommends resources for further learning.

Uploaded on Jul 11, 2011
The third episode in the OWASP Appsec Tutorial Series. This episode describes the #2 attack on the OWASP top 10 – Cross-Site Scripting (XSS). This episode illustrates three version of an XSS attack: high level, detailed with the script tag, and detailed with no script tag, and then recommends resources for further learning.

Published on Sep 24, 2012
The forth episode in the OWASP Appsec Tutorial Series. This episode describes the importance of using HTTPS for all sensitive communication, and how the HTTP Strict Transport Security header can be used to ensure greater security, by transforming all HTTP links to HTTPS automatically in the browser.


DEFT 7 is based on the new Kernel 3 (Linux side) and the DART (Digital Advanced Response Toolkit) with the best freeware Windows Computer Forensic tools. It’s a new concept of Computer Forensic system that use LXDE as desktop environment and WINE for execute Windows tools under Linux and mount manager as tool for device management.

It is a very professional and stable system that includes an excellent hardware detection and the best free and open source applications dedicated to Incident Response, Cyber Intelligence and Computer Forensics.

DEFT is meant to be used by:

Military
Police
Investigators
IT Auditors
Individuals

DEFT is 100% made in Italy

rooting

Is the allure of being a superuser tempting you? Android rooting opens up a world of possibility, but it can also void your warranty, or even leave you with a bricked device. The important thing is to be careful. Read up about what you are going to do before you begin. Make sure that you […]

Is the allure of being a superuser tempting you? Android rooting opens up a world of possibility, but it can also void your warranty, or even leave you with a bricked device. The important thing is to be careful. Read up about what you are going to do before you begin. Make sure that you backup your data. Follow the instructions to the letter. Manufacturers and carriers have a vested interest in dissuading you from rooting. If you’re careful, the risk is minimal, and the potential benefits are impressive. Let’s take a closer look.

Around since the early days of the T-Mobile G1 (HTC Dream), rooting can add functionality to a phone and often extend the life of the device. The T-Mobile G1, for instance, was officially supported through Android 1.6 Donut, but if you rooted the phone, you could load an alternative developer-made version of the OS that offered most of Android 2.2 Froyo’s features.

I’m going to share some of rooting’s benefits and risks, where to find some great replacements for the default Android OS, and a few other tips. If you have any of your own that I haven’t covered here, please add them to the comments below.

What is rooting?

Rooting, in a nutshell, is the process that provides users with full administrator control and access to an Android smartphone or tablet. Similar to “jailbreaking” an iOS device, this is often done in order to bypass carrier or handset maker limitations or restrictions. Once you achieve “root access,” you can replace or alter applications and system settings, run specialized apps, and more.

One of the more common reasons to root a phone is to replace the operating system with a ROM, another developer’s version of the OS that also gives you more control over details. In rooting culture, we’d call that “flashing a custom ROM.”

The process of rooting an Android phone varies for each device, but seems to have been streamlined over time. Google’s Nexus line of phones, such as the LG-made Nexus 4, appeals to developers and techie types and are among the most often rooted models. With that in mind, you’ll also find that popular devices like the Samsung Galaxy S3 and HTC One X+ have plenty of custom ROMs to choose from.

Note that rooting will void the device warranty; however, flashing a stock ROM can revert things back to their original state.

Why root?

There are multiple reasons for you to consider rooting your Android handset, some more obvious than others. Chief among the benefits is the ability to remove any unwanted apps and games that your carrier or phone maker installs before you ever unwrap your phone. Rather than simply disabling these bloatware titles, which is often the best you can do within Android, rooting can grant you a full uninstallation. Deleting apps you’ll never use can also free up some additional storage capacity.

Another main benefit of rooting is to enable faster platform updates. From the time it takes for Google to announce a new version of Android to the time your carrier pushes it to your device can be on the order of weeks, months, or even longer. Once rooted, you can often get some of the new platform features through custom ROMs in short order. This could, for some users, add years of life to an Android handset — rather than buy a new phone, flash a new ROM.

Other reasons to root a phone include being able to perform complete device backups, integrate tethering and mobile hot-spot features, and extend the device’s battery life through newfound settings and controls.

How to root your Android

What are the risks?

As I mentioned above, rooting your device can void your warranty. This is perhaps the biggest risk associated with playing around with your phone. If you run into big trouble and you’ve added a custom ROM build, your manufacturer and carrier likely won’t help you out.

In most cases, you’ll be able to overturn any ROM you flash, returning to the phone’s stock Android OS with as much ease as you installed the new ROM in the first place. However, a word of caution. If you’re not careful, or don’t follow the steps properly, you could end up with a glorified paperweight. Yes, I’m talking about “bricking” your device. It’s vitally important that you exercise caution when attempting to root your phone and pay close attention to what you’re doing.

Stick to the more reputable sources for help and feedback, and look for the most recent news about ROMs and your particular Android device. Along those lines, you’ll also want to ensure that you read through everything you can before starting down this road. If you’re in a forum thread, skim the replies to see if there are issues or problems with your particular handset.

Helping hands

For help with rooting, I would first recommend XDA developers, AndroidCentral forums, Androidforums, and Rootzwiki. I also suggest checking Google+ as a good source for rooting and modding news and feedback. The rooting scene is not some secret underground Fight Club; you’ll find plenty of documented help for rooting your phone. Filter your results by date, read through the details, and understand what it is you are about to do.

CyanogenMod is one of the oldest and feature-rich ROMs available.(Credit: CyanogenMod)

More about ROMs

For all practical purposes, (custom) ROMs are replacement firmware for Android devices that provide features or options not found in the stock OS experience. Often built from the official files of Android or kernel source code, there are more than a few notable ROMs to consider. Among the more popular custom ROMs are CyanogenMod, Paranoid Android, MIUI, and AOKP (Android Open Kang Project). There are, of course, countless others to check out, with more arriving almost daily.

In terms of sheer support and development, CyanogenMod is the clear leader in this field. The number of supported devices is unparalleled and the community has long rallied around this ROM. This is not meant to say that it’s necessarily the “best” ROM; beauty is in the eye of the beholder.

Closely resembling the stock Android experience, CyanogenMod has been known to introduce features that later end up in official builds of Android. As of today there are more than 4.2 million active installations of CyanogenMod releases, with v10.1 (based on Android 4.2 Jelly Bean) being the latest.

Paranoid Android is one of the more popular custom ROMs for Android.(Credit: Paranoid Android)

Where to look for ROMs

Forums are going to be a great place to keep yourself plugged in, but the larger ROM developers will provide their own Web sites. Aside from the aforementioned custom ROMs, others that have gained a strong following include SynergyROM, Slim Bean, LiquidSmooth, RevoltROM, and Xylon. Be warned: talking about ROMs can often result in heated debate as to which is better or offers more options.

Noteworthy apps

Aside from installing custom ROMs, rooting your phone opens the door to installing new apps and gaining extended device management and security functionality beyond what comes with the usual Android OS experience.

Should you decide to not load a new ROM interface, you can still install apps that add new levels of functionality to your rooted Android phone. Today’s more popular titles include ROM Toolbox Pro, Titanium Backup, Touch Control, Cerberus anti-theft, and SetCPU. The appeal of each will vary depending upon on how much you want to tweak your Android experience.

For those of you who plan to flash ROMs on a regular basis, I recommend starting with ROM Manager. This utility lets users manage backups and recoveries, install ROMs, and other handy functions. While it is available as a free app, the premium client has ROM update notifications, nightly ROM downloads, set automatic backups, and other features.

ROM Toolbox Pro is a handy utility for rooted users.(Credit: JRummy Apps)

Backup plans

When it comes to rooting your phone, it is always a good idea to have backup plans in place. After all, you’ll need something to fall back on should you run into an issue with an untested or experimental ROM. While Titanium Backup seems to be the most popular, Carbon has gained quite a fan base of late. Regardless of which route you take, it’s important to create a backup and test it before you apply a custom ROM.

Become familiar with the process and make sure that you’ll be able to restore things in the event of a catastrophe. It might take some practice and you could spend more time than you’d like creating this backup, but it could be all that stands between you and expensive phone repair.

Indeed, there is plenty to consider when it comes to rooting your Android phone. Rest assured, though, that no matter how daunting the task might seem, there’s a large community of users out there who will have your back. And while the actual rooting process varies with each handset model, on the whole, it isn’t as difficult as it may sound.

If you’ve read through this post and still don’t know if rooting is for you, my suggestion is to give it more time and mull it over. Replacing the default Android OS certainly isn’t for everyone and there’s quite a bit more on the topic besides. For many people, myself included, the rewards of tweaking your Android phone to have it exactly the way you want it are worth the risk.

What is rooting?

If you’re an Administrator on a Windows machine, you have access to the entire operating system and you can do whatever you like. That’s essentially what happens if you root your Android device. With root access, you can get around any restrictions that your manufacturer or carrier may have applied. You can run more apps; you can customize your device to a greater degree; and you can potentially speed it up in a variety of ways.

The process involves backing up your current software and then flashing (installing) a new custom ROM (modified version of Android).

Why would you root?

One of the most obvious incentives to root your Android device is to rid yourself of the bloatware that’s impossible to uninstall. You’ll be able to set up wireless tethering, even if it has been disabled by default. You can also access your entire file system, install special apps that require a root, and flash custom ROMs, which can add extra features and streamline your phone or tablet’s performance. A lot of people are tempted by the ability to completely customize the look of their phones. You can also manually accept or deny app permissions.

You won’t find a lot of amazing must-have apps when you root, but there are enough to make it worthwhile. For example, some apps allow you to automatically backup all of your apps and all of their data, completely block advertisements, create secure tunnels to the Internet, overclock your processor, or make your device a wireless hotspot.

Why wouldn’t you root?

There are essentially three potential cons to rooting your Android.

  • Voiding your warranty: Some manufacturers or carriers will use rooting as an excuse to void your warranty. It’s worth keeping in mind that you can always unroot. If you need to send the device back for repair, simply flash the original backup ROM you made and no one will ever know that it was rooted.
  • Bricking your phone: Whenever you tamper too much, you run at least a small risk of bricking your device. This is the big fear everyone has. The obvious way to avoid it happening is to follow instructions carefully. Make sure that the guide you are following works for your device and that any custom ROM you flash is designed specifically for it. If you do your research and pay attention to feedback from others, bricking should never occur.
  • Security risks: Rooting may introduce some security risks. Depending on what services or apps you use on your device, rooting could create a security vulnerability. For example, Google refuses to support the Google Wallet service for rooted devices.

How to root your Android

Before you actually try to root your device, make sure that you do some reading. The best place to find discussions about rooting, guides, and custom ROMs is definitely the XDA Developers Forum. Look for a thread on your specific device and you’re sure to find a method that has worked for other people. It’s worth spending some time researching the right method for your device.

Preparation for root

You’ll want to ensure that your device is fully charged before you begin. You’ll also need to turn USB debugging on. On the Galaxy S3 you’ll find it in Menu > Settings > Developer options and then check the box next to USB debugging. You will likely be plugging your device into your computer in order to root it.

Most Android rooting methods require you to install some software on your computer. It’s likely you’ll need to install the Android SDK. You may find other software is required. Make sure you follow the instructions and install all of it before proceeding.

One-click rooting

One of the easiest methods of rooting, which also supports a long list of devices, is SuperOneClick. You’ll find clear instructions, including a video, on how to use it at this XDA Developers SuperOneClick thread.

You will need to install some software to prepare, but the actual rooting process is one click. It will only take a few minutes to complete and then you’ll need to restart your Android device.

There is software out there that claims to provide one click rooting with no extra installs, but you should not have to pay to root your device and it’s very important to be wary about the method you choose. If in doubt, do more research. The XDA Developers forum is the most trustworthy source for rooting guides.

Your specific device

The reason rooting isn’t more straightforward is that all Android devices are not created equal. There are significant differences between Android smartphones, between manufacturers, and even between carrier specific versions of the same phone model. Make sure that any rooting guide or custom ROM you intend to use does support your specific device or you are asking for trouble.

Once you have found the right guide for your phone or tablet, it’s simply a case of working through the listed steps methodically. It can be a complicated procedure and it can take a while. Here’s an example guide for rooting the Samsung Galaxy S3. It can appear intimidating at first glance, but provided you follow it step-by-step, it should be a pain-free process. You can post questions in the XDA Developers forum if you run into trouble.

To root or not to root

Gaining full root access to your Android device can be thrilling, especially if you want to tinker with settings and customize your device. How much it changes your experience depends largely on the device you have. If you have a shuttered device, like a Kindle Fire tablet, then it’s a great way to get the full Android experience.

The potential benefits for all Android users include improved battery life, root-only apps, custom ROMs, overclocking, an end to bloatware, improved performance, and the ability to upgrade your phone when you want. If you aren’t excited at the prospect of any of these things, rooting probably isn’t for you.

Read more: http://www.digitaltrends.com/mobile/how-to-root-android/#ixzz2VG0X985Z
Follow us: @digitaltrends on Twitter | digitaltrendsftw on Facebook

Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as “root access“) within Android’s subsystem.

Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device’s operating system, usually with a more recent release of its current operating system.

As Android derives from the Linux kernel, rooting an Android device is similar to accessing administrative permissions on Linux or any other Unix-like operating system such as FreeBSD or OS X.

What is Root?

Defined by Lininfo.org:

Root is the user name or account that by default has access to all commands and files on a Linux or other Unix-like operating system.

RootzWiki is dedicated to assisting you in gaining root access on your Android phone.

We are not responsible for any broken devices. This site is purely based on the idea of an “open” minded community. We strive for success and 100% accuracy and simplified methods in order to not confuse anyone. If you feel you have any questions pertaining to root, notice there is a discussions tab above next to the page name. We do not require anyone to register in order to download or view the content of these pages. In order for anyone to make a post or change to the content on ANY page you must first register and submit your changes. We do not guarantee your work to be posted on the site, you must link (cite) the source from where you got it first in order to make any changes (based on approval). If it is a new root tutorial, etc., you may post it in the respectable page.

This wiki is administered by DrMacinyasha.

 

In this article, I will discuss all kinds of aspects of rooting your Android phone and the benefits that come with it.

Maybe you’ve heard about “rooting” a phone from a friend or read about it somewhere on the Internet.  Maybe you even *kind of* know what it is but aren’t sure what you can do with it. Or maybe you are already running a rooted phone and looking for more ways you can utilize it. Whatever the case may be, this article is for you.

What Is Rooting?

First, for the newbies, let me clarify what rooting is. Getting root or rooting your phone is the process of modifying the operating system that shipped with your device to grant you complete control over it.

This means you can overcome limitations that the carriers and manufacturers put on your phone, extend system functionality, and even upgrade it to a custom flavor of Android.

The name root comes from the Linux operating system world, where the most privileged user on the system (otherwise known as Administrator on Windows) is called root.

Now, I’d like to take a moment to dispel a common misconception and clarify one thing: rooting does *not* mean installing a custom ROM (a ROM is a modified, “aftermarket” OS).Installing a ROM may require rooting first, but just rooting can be usually done in only a few minutes, keeping your stock OS otherwise completely intact.

Usually rooting is fairly simple – in most cases you can find several videos and articles on the web that explain how to do it on your specific phone model – just Google “YOURPHONEMODEL root”.

Rooting is not something manufacturers or carriers approve of but they can’t really prevent it from happening because the rooting process usually exploits a vulnerability in the operating system code or device drivers and allows the “hacker” to upload a special program called su to the phone. This program is the one that provides root access to programs that request it.

Contrary to popular belief, su stands for “switch user” and not “superuser.”

Another program called Superuser Permissions is usually bundled with all root methods. It gives you a chance to approve or deny requests from any application that wants to utilize root. Superuser Permissions essentially replaces the conventional root password with a simple Approve/Deny prompt, which isn’t as secure as having a password, but is far more convenient on a mobile device.

Now an obligatory warning: rooting your phone does run the risk of potentially bricking it (i.e. your phone could become nonfunctional) – so do your homework before attempting anything, unless you’re a fan of $500 paper weights.

Benefits Of Rooting

Let’s check out some of the benefits of rooting your Android phone.

Full Control Over Android

You have access to alter any system files, use themes, change boot images, delete annoying stock apps, such as Sprint‘s NFL Mobile live and Nascar Sprint Cup Mobile, and other various native applications that might drive you crazy (Footprints, Voice Dialer, etc).

There is plenty of information on the web on how to accomplish this, but our favorite way is by using Titanium Backup and freezing/deleting the apps from there (root required, of course).

Titanium Backup

Download Titanium Backup from Google Play
QR code for https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup

Titanium Backup ★ root

TOP APP
NEW
UPDATED
PRICE DROP
by Titanium Track
5,000,000+ downloads
162522 ratings (4.7 avg)

Back Up And Restore The Whole System

On most rooted Android devices, you can back up your entire system to an SD card, much in the same way you can image a hard drive. This is great if you’d like to try a new ROM, as you can back up your phone, wipe it completely, flash the new ROM, and if you don’t like it, just restore from your backup to get your device back to exactly how it was before you wiped it.

The easiest way to do this at the moment is by using ROM Manager, developed by famed Android developer Koush.

ROM Manager allows you to easily flash a custom recovery image which is what you will need in order to backup and restore your phone. The recovery image is a special program that can be booted into outside of the phone’s main operating system, sort of like an OS recovery console on a PC. By default, the recovery image on most Android phones only gives you a few options, mainly related to wiping the phone. Custom recovery images expand upon these options and usually include scripts that can do things like backup and restore your system, fix file permissions, or allow you to flash custom ROMs that the normal recovery image would otherwise reject.

Normally, flashing a custom recovery image requires some command line work, either on your PC, or on a terminal emulator directly on the phone, but Koush’s ROM Manager should automatically flash his custom recovery image (known as ClockworkMod Recovery) for you, provided you’re on one of the supported phones (<– the list in this link should be always up-to-date, as it’s maintained by Koush) and that it is already rooted.

Using ROM Manager is pretty simple. Download and install the application from the market, fire it up, and you’ll be prompted to allow the application superuser permissions – make sure you approve it.

The first thing you’ll need to do is flash the ClockworkMod recovery image that I mentioned earlier, which can be done right in the app (it’s the first option). ROM Manager should automatically find the latest version of the right image for your phone, download, and install it – the whole process is seamless.

After that is done, you can simply use the ‘Manage and Restore Backups’, and ‘Backup current ROM’ options to, well, backup your current ROM or restore from an existing backup. It’s that simple!

At Android Police, we always encourage supporting developers, so please check out ROM Manager Premium if you enjoyed the free version!

ROM Manager

Download ROM Manager from Google Play
QR code for https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager

ROM Manager

TOP APP
NEW
UPDATED
PRICE DROP
by ClockworkMod
5,000,000+ downloads
127965 ratings (4.5 avg)

ROM Manager Premium

Download ROM Manager Premium from Google Play
QR code for https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager.license

ROM Manager (Premium)

TOP APP
NEW
UPDATED
PRICE DROP
by ClockworkMod
100,000+ downloads
27710 ratings (4.5 avg)

Save Space On Your Phone

While Google did introduce Apps2SD (moving parts of applications to external storage) officially in the Froyo update, it remains up to developers to manually add support for it in their apps. Because of that, it’s still fairly easy to overflow your internal storage and run out of space.

The easiest way to alleviate this problem and enable most applications to be movable to SD would be to flash a custom ROM that enables just that. For example, CyanogenMod, the most popular Android custom ROM, allows the user to force most apps to SD even if developers of those apps didn’t enable this feature. See 13 Ways CyanogenMod 7 Makes My Android Phone Feel Future-Proof [Deep Review] for more info on this and other amazing features of CyanogenMod.

Note that this doesn’t work on all apps, notably keyboards and apps with widgets.

Run Special Applications

Update 6/26/11: Rather than list apps that are supercharged by having root access here, we started a series dedicated to them. Here are the first parts of Top Android Apps Every Rooted User Should Know About:

Install Custom ROMs

The Android custom ROM scene started growing shortly after the first Android phone, the T-Mobile G1, was released. The ROMs that were initially available just offered a few tweaks here and there – access to developer only sections of the operating system, debugging information, and things of that nature.

Now, a few years after the release of the G1, the Android ROM community has grown immensely, and ROMs have been developed for most of the Android phones currently on the market.

They’ve gone far beyond simple tweaks and can now give your phone an entirely new look and feel. There are ROMs that can make your phone fly by replacing the kernel with hyper-optimized versions or even overclocking the CPU. The possibilities are nearly limitless and attempting to cover all of the features of all the ROM’s available for all of the phones out there would be pretty much impossible.

If you’re interested in flashing a custom ROM on your phone, your best bet is to hit the Googles, search for “phonename custom ROM,” and see what comes up. You’ll likely find at least one forum dedicated to hacking your phone with plenty of information to get you started.

Here at AndroidPolice, we’re planning a series of custom ROM reviews for as many phones as we can get our hands on. Stay tuned for updates!

Check out our more detailed guide that dives a little deeper into the reasons to go custom: Custom ROMs Explained And Why You Want Them

 

Good luck and happy rooting!

Have you rooted your phone? If so, what are you running?

Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as “root access“) within Android’s subsystem.

Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device’s operating system, usually with a more recent release of its current operating system.

As Android was derived from the Linux kernel, rooting an Android device is similar in practice to accessing administrative permissions on Linux or any other Unix-like operating system such as FreeBSD or OS X.

The process of rooting varies widely by device, but usually includes exploiting a security bug(s) in the firmware (i.e. in Android) of the device, and then copying the su binary to a location in the current process’s PATH (e.g. /system/xbin/su) and granting it executable permissions with the chmod command. A supervisor application like SuperUser or SuperSU can regulate and log elevated permission requests from other applications. Many guides, tutorials, and automatic processes exist for popular Android devices facilitating a fast and easy rooting process.

For example, shortly after the HTC Dream was released, it was quickly discovered that anything typed using the keyboard was being interpreted as a command in a privileged (root) shell. Although Google quickly released a patch to fix this, a signed image of the old firmware leaked, which gave users the ability to downgrade and use the original exploit to gain root access. Once an exploit is discovered, a custom recovery image that skips the digital signature check of a firmware update package can be flashed. In turn, using the custom recovery, a modified firmware update can be installed that typically includes the utilities (for example the Superuser app) needed to run apps as root.

The Google-branded Android phones, the Nexus One, Nexus S, Galaxy Nexus and Nexus 4, as well as their tablet counterparts, the Nexus 7 and Nexus 10, can be boot-loader unlocked by simply connecting the device to a computer while in boot-loader mode and running the Fastboot program with the command “fastboot oem unlock”.[9] After accepting a warning the boot-loader will be unlocked so that a new system image can be written directly to flash without the need for an exploit.

Recently, Motorola, LG Electronics and HTC have added security features to their devices at the hardware level in an attempt to prevent retail Android devices from being rooted.For instance, the Motorola Droid X has a security boot-loader that will put the phone in “recovery mode” if unsigned firmware is loaded onto the device, and the Samsung Galaxy S II will display a yellow triangle indicator if the device firmware has been modified.

Until the early 2010s, the response of tablet and smartphone manufacturers and mobile carriers had typically been unsupportive of third-party firmware development. Manufacturers had expressed concern about improper functioning of devices running unofficial software[10] and related support costs. Moreover, firmware such as CyanogenMod sometimes offers features for which carriers would otherwise charge a premium, such as tethering. As a result, technical obstacles such as locked bootloaders and restricted access to root permissions have commonly been introduced in many devices. For example, in late December 2011, Barnes & Noble and Amazon.com, Inc. began pushing automatic, over-the-air firmware updates, 1.4.1 to Nook Tablets and 6.2.1 to Kindle Fires, that removed users’ ability to gain root access to the devices. The Nook Tablet 1.4.1 update also removed users’ ability to sideload apps from sources other than the official Barnes & Noble app store (without modding).[11][12]

However, as community-developed software began to grow popular in the late 2000s to early 2010s,[13][14] and following a statement by the Copyright Office and Librarian of Congress (US) allowing the use of “jailbreaking” mobile devices,[15] manufacturers and carriers have softened their position regarding CyanogenMod and other unofficial firmware distributions, with some, including HTC,[16] Samsung,[17] Motorola[18] and Sony Ericsson,[19] even actively providing support and encouraging development.

In 2011, the need to circumvent hardware restrictions to install unofficial firmware lessened as an increasing number of devices shipped with unlocked or unlockable bootloaders, similar to the Nexus series of phones. Device manufacturer HTC has announced that it would support aftermarket software developers by making the bootloaders of all new devices unlockable.[10]

On July 26, 2010, the United States Copyright Office announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.[21]

On October 28, 2012, the US Copyright Office updated their exemption policies. The rooting of smartphones continues to be legal “where circumvention is accomplished for the sole purpose of enabling interoperability of [lawfully obtained software] applications with computer programs on the telephone handset.” However, the U.S. Copyright office refused to extend this exemption to tablets, arguing that the term “tablets” is broad and ill-defined, and an exemption to this class of devices could have unintended side effects.[22][23]

As of March 5, 2013 it is illegal to unlock your phone under the Digital Millennium Copyright Act for use with other carriers without the consent of the manufacturer. Your carrier can still allow the unlock but if it is denied, there is no legal recourse to unlock the device.[24]

In this article I will share for you the link to download Z4root v1.3.0, it’s a powerful application that allows to root different Android devices in one easy way only with one click method.

If you want to root your Android device with the Z4root you need to know this application before was in the Market Store, but now was removed because violating the “terms and conditions” from there.

Z4root should be 100 % safe because nothing on disk is changed besides the root binaries, and in case something isn’t working then you simply reboot your device and the issues are fixed.

The temporary root option works on 99% Android devices, and below we will share a list, but you need know this list is created by users, with the compatible devices and incompatible devices for the permanent root option.

Android Devices compatible with the option for a permanent root:

Samsung Galaxy S (All variants), Sony X10, Motorola Defy, Xperia Mini, Droid 2, Galaxy Tab, Galaxy I5700, Hero, G1, Galaxy 3 I5800, Droid X, Samsung Acclaim, Cricket Huawei Ascend, Motorola Cliq, Huawei 8120, Optimus T, Droid 1, Garmin Asus, Backflip, A50,  LG Ally, Motorola Flipside, Motorola Milestone 2, Dell streak, X10 Mini Pro,Smartq v7 android 2.1

Android Devices incompatible with the option for a permanent root:

HTC Desire (requires nand unlock), HTC Desire HD (requires nand unlock), HTC Magic (unknown), HTC Evo (requires nand unlock), HTC G2 (requires nand unlock), Archos 70 (unknown), myTouch 3G (unknown), Wildfire, Droid Incredible.

Download Z4ROOT APK v1.3.0

How to use the Z4root- step by step tutorial

When you want to use the Z4root you need understand the root process is a complex operation, and that’s why you always take in consideration to get a full backup for all your data, never you don’t know what happening and is good to have a backup file with all your important data stored in your Android device.

  1. First download Z4root from above link and save it in your computer.
  2. Connect your device with your computer using the original USB cord.
  3. Transfer (copy and paste) the downloaded file .apk in your Android’s SD card, place this file in the root or somewhere when your file is easy to be accessible.
  4. Enable the USB debugging option from the next path: Settings-> Applications and there check “unknown sources”. Also, in Settings-> Applications-> Development and there check the USB debugging option.
  5. Now with one file manager like Astro file manager find the downloaded z4root.apk file and install it.
  6. Now, when the installation is done run the Z4root application directly in your Android device. When the application is opened you will see two options: Temporary Root and Permanent Root.
  7. Choose which option you want from the app main menu and your device will take a reboot.
  8. Now when you want to install applications that require the root access you can give the root permission.

Note: If you want to remove the root access, in the z4root menu select the unroot option, after you selected the un-root option your device will be unroot.

When you root the device the warranty device will get void, and that’s why the developer made available the unroot option which restore your warranty.

 

Note to some HTC Devices: z4root will root your device but you will need to use other methods for S-Off. Note: Z4root sometimes doesn’t work right away, reboot your device and try again if you have issues.

Instructions

Requirements: USB Cable, Z4Root (Download), (Alternate Download) file manager from the market or on your tablet and a computer.

Install

  • Connect Device to your computer and enable USB Mass Storage.
  • Place the Z4Root APK (application) in your storage directory of your choice.
  • Go to Settings, Applications and select “Unknown Sources”.
  • Properly unmount mass storage.
  • Go to your file manager and select z4root and install.
  • Run the z4root application.

Alternate Method (no file manager required)

  • Install ADB and get it working on your device.
  • type:
     adb install (location to apk)
  • Run the z4root application.

If all else fails

Motorola 1-Click Root

  • 1-Click Root: Download
  • Install Drivers
  • Enable USB Debugging
  • Put phone in Charge Mode Only
  • Click App; MotorolaOneClickRoot
  • Follow on screen instructions.

Manual Root

Download

  • psneuter: Download
  • Superuser: Download
  • busybox: Download
  • Unzip the downloaded files into the same folder
  • Open a terminal and change to the folder.

You need the android SDK and ADB working. To make sure type:

adb devices

if your device lists, then you are ready to go!

Gain Root

  • Run the following commands:
    adb push psneuter /data/local/temp/psneuter
    adb shell
    chmod 755 /data/local/temp/psneuter
    ./data/local/temp/psneuter
  • ADB should hang, wait a little while and then type:
    adb shell

NOTE: You should have the “#” sign instead of the “$”. If you do, you have temporary root, and can continue on.

  • Type:
    exit
    adb push busybox /data/local/temp/busybox
    adb shell
    chmod 755 /data/local/temp/busybox
    ./data/local/temp/busybox mount -o rw,remount /system
  • The last command should return nothing

Motorola MB525 – Another guide – http://forum.xda-developers.com/showthread.php?t=889133

DISCLAIMER: RyanZA and RootzWiki are not liable or responsible for any damages to your phones, this is solely the users decision to “root” their phone. Enjoy!

Android SDK

Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012[update], more than 700,000 applications have been developed for Android, with over 25 billion […]

Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012[update], more than 700,000 applications have been developed for Android, with over 25 billion downloads.[2][3] A June 2011 research indicated that over 67% of mobile developers used the platform, at the time of publication.[4] In Q2 2012; around 105 million units of Android smartphones were shipped which acquires a total share of 68% in overall smartphones sale till Q2 2012.[5]

The ADT Bundle provides everything you need to start developing apps, including a version of the Eclipse IDE with built-in ADT (Android Developer Tools) to streamline your Android app development. If you haven’t already, go download the Android ADT Bundle. (If you downloaded the SDK Tools only, for use with an existing IDE, you should instead read Setting Up an Existing IDE.)

Install the SDK and Eclipse IDE

  1. Unpack the ZIP file (named adt-bundle-<os_platform>.zip) and save it to an appropriate location, such as a “Development” directory in your home directory.
  2. Open the adt-bundle-<os_platform>/eclipse/ directory and launch eclipse.

That’s it! The IDE is already loaded with the Android Developer Tools plugin and the SDK is ready to go. To start developing, read Building Your First App.

Caution: Do not move any of the files or directories from the adt-bundle-<os_platform> directory. If you move the eclipse or sdk directory, ADT will not be able to locate the SDK and you’ll need to manually update the ADT preferences.

Additional information

As you continue developing apps, you may need to install additional versions of Android for the emulator and other packages such as the library for Google Play In-app Billing. To install more packages, use the SDK Manager.

Everything you need to develop Android apps is on this web site, including design guidelines, developer training, API reference, and information about how you can distribute your app. For additional resources about developing and distributing your app, see the Developer Support Resources.

There is a community of open-source enthusiasts that build and share Android-based firmware with a number of customizations and additional features, such as FLAC lossless audio support and the ability to store downloaded applications on the microSD card.[42] This usually involves rooting the device. Rooting allows users root access to the operating system, enabling full control of the phone. In order to use custom firmwares the device’s bootloader must be unlocked. Rooting alone does not allow the flashing of custom firmware. Modified firmwares allow users of older phones to use applications available only on newer releases.[43]

Those firmware packages are updated frequently, incorporate elements of Android functionality that haven’t yet been officially released within a carrier-sanctioned firmware, and tend to have fewer limitations. CyanogenMod and OMFGB are examples of such firmware.

On 24 September 2009, Google issued a cease and desist letter[44] to the modder Cyanogen, citing issues with the re-distribution of Google’s closed-source applications[45] within the custom firmware. Even though most of Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the Android Market and GPS navigation. Google has asserted that these applications can only be provided through approved distribution channels by licensed distributors. Cyanogen has complied with Google’s wishes and is continuing to distribute this mod without the proprietary software. He has provided a method to back up licensed Google applications during the mod’s install process and restore them when it is complete.[46]

The NDK is a toolset that allows you to implement parts of your app using native-code languages such as C and C++. For certain types of apps, this can be helpful so you can reuse existing code libraries written in these languages, but most apps do not need the Android NDK.

Before downloading the NDK, you should understand that the NDK will not benefit most apps. As a developer, you need to balance its benefits against its drawbacks. Notably, using native code on Android generally does not result in a noticable performance improvement, but it always increases your app complexity. In general, you should only use the NDK if it is essential to your app—never because you simply prefer to program in C/C++.

Typical good candidates for the NDK are self-contained, CPU-intensive operations that don’t allocate much memory, such as signal processing, physics simulation, and so on. When examining whether or not you should develop in native code, think about your requirements and see if the Android framework APIs provide the functionality that you need.


MobileGo is a life saver for those who love music and video, text a lot and juggle apps on their Android phones and tablets.

Android Fans:Backup everything to PC with 1 click & retain 100% quality.
Music Lovers:Instantly add fun stuff and enjoy media anytime, anywhere.
App Addicts:Download, install, uninstall and export apps quickly and easily.
Socialites:Transfer contacts from/to Outlook and send & reply SMS seamlessly from your PC.
The Android 3.1 platform (also backported to Android 2.3.4) introduces Android Open Accessory support, which allows external USB hardware (an Android USB accessory) to interact with an Android-powered device in a special “accessory” mode. When an Android-powered device is in accessory mode, the connected accessory acts as the USB host (powers the bus and enumerates devices) and the Android-powered device acts as the USB device. Android USB accessories are specifically designed to attach to Android-powered devices and adhere to a simple protocol (Android accessory protocol) that allows them to detect Android-powered devices that support accessory mode.[22]

Atrae capital de riesgo con innovación

Un proyecto sólido puede obtener inversiones de hasta 2,000 dólares

Para que los emprendedores y los empresarios atraigan la mirada de inversionistas es necesario que encuentren problemas sociales a los cuales dedicar tiempo y trabajo, para darles soluciones innovadoras, explicaron representantes de fondos de capital de riesgo internacionales durante el segundo día de actividades del EmTech 2013.

“Para conseguir una inversión, la principal característica con la que deben cumplir los empresarios es tener confianza en su idea de negocio, conocer el mercado en el que pretende integrarse y tener una buena estrategia para conseguir clientes, pues muchas veces los emprendedores se concentran en desarrollar las características de sus productos y en diferenciarse de la competencia”, dijo Deven Soni, inversionista de capital de riesgo de NEVEQ

Otra de las características que hacen atractivos los proyectos para los inversionistas , de acuerdo con Scott Hartley, socio del fondo Mohr Davidow Ventures (MDV), es que ofrezcan productos o servicios innovadores, ya sea porque no se encuentren en el mercado, porque presenten una innovación con respecto a lo que ya existe o porque ayudan a cambiar la conducta de los consumidores.

Una forma en que pueden lograr esta innovación en los bienes y servicios, propuesta por Sumeet Jain, inversor de capital de riesgo de Intel Capital, es a través de la generación de varias hipótesis o propuestas de solución a problemáticas sociales.

“Deben tomar en cuenta también en que momento van a lanzar la solución al mercado para que tenga una buena respuesta de parte de los consumidores y logren obtener una buena penetración en el mercado”, detalló Jain, quien agregó que en caso de que los proyectos sean atractivos, pueden proporcionar fondos por alrededor de 2,000 dólares para desarrollar las ideas.

De este modo, durante el segundo día de actividades del EmTech 2013, realizado en el Tec de Monterrey, campus Santa Fe, Juan Ángel Hernández, director de Capital Emprendedor del Instituto Nacional del Emprendedor (Inadem) recomendó a emprendedores y empresarios que deseen atraer la inversión de capitales privados, desarrollar proyectos que además de ser rentables, puedan perfeccionarse con el paso del tiempo para mantenerse actuales en el mercado.

“Y cuando tengan una oportunidad para reunirse con ellos, deben prepararse para presentar su proyecto en menos de 10 minutos, rescatar sus mejores ideas y mostrarles porque son rentables sus modelos de negocio”, comentó Hernández.

fabiola.naranjo@eleconomist.mx

CRÉDITO: 

Fabiola Naranjo

Un proyecto sólido puede obtener inversiones de hasta 2,000 dólares

Para que los emprendedores y los empresarios atraigan la mirada de inversionistas es necesario que encuentren problemas sociales a los cuales dedicar tiempo y trabajo, para darles soluciones innovadoras, explicaron representantes de fondos de capital de riesgo internacionales durante el segundo día de actividades del EmTech 2013.

“Para conseguir una inversión, la principal característica con la que deben cumplir los empresarios es tener confianza en su idea de negocio, conocer el mercado en el que pretende integrarse y tener una buena estrategia para conseguir clientes, pues muchas veces los emprendedores se concentran en desarrollar las características de sus productos y en diferenciarse de la competencia”, dijo Deven Soni, inversionista de capital de riesgo de NEVEQ

Otra de las características que hacen atractivos los proyectos para los inversionistas , de acuerdo con Scott Hartley, socio del fondo Mohr Davidow Ventures (MDV), es que ofrezcan productos o servicios innovadores, ya sea porque no se encuentren en el mercado, porque presenten una innovación con respecto a lo que ya existe o porque ayudan a cambiar la conducta de los consumidores.

Una forma en que pueden lograr esta innovación en los bienes y servicios, propuesta por Sumeet Jain, inversor de capital de riesgo de Intel Capital, es a través de la generación de varias hipótesis o propuestas de solución a problemáticas sociales.

“Deben tomar en cuenta también en que momento van a lanzar la solución al mercado para que tenga una buena respuesta de parte de los consumidores y logren obtener una buena penetración en el mercado”, detalló Jain, quien agregó que en caso de que los proyectos sean atractivos, pueden proporcionar fondos por alrededor de 2,000 dólares para desarrollar las ideas.

De este modo, durante el segundo día de actividades del EmTech 2013, realizado en el Tec de Monterrey, campus Santa Fe, Juan Ángel Hernández, director de Capital Emprendedor del Instituto Nacional del Emprendedor (Inadem) recomendó a emprendedores y empresarios que deseen atraer la inversión de capitales privados, desarrollar proyectos que además de ser rentables, puedan perfeccionarse con el paso del tiempo para mantenerse actuales en el mercado.

“Y cuando tengan una oportunidad para reunirse con ellos, deben prepararse para presentar su proyecto en menos de 10 minutos, rescatar sus mejores ideas y mostrarles porque son rentables sus modelos de negocio”, comentó Hernández.

fabiola.naranjo@eleconomist.mx

CRÉDITO: 

Fabiola Naranjo

Hardware Detection Tool

HDT (stands for Hardware Detection Tool) is a Syslinux com32 module that displays low-level information for any x86 compatible system. It provides both a command line interface and a semi-graphical menu mode for browsing.

HDT (stands for Hardware Detection Tool) is a Syslinux com32 module that displays low-level information for any x86 compatible system. It provides both a command line interface and a semi-graphical menu mode for browsing.

Impulsa tus ventas con el uso de Internet

Mexicanos invierten 67 minutos más en la red que el año pasado

En México, alrededor de 2.8 millones de personas cuentan con acceso a Internet y lo utilizan no sólo para realizar búsquedas de información, sino también para transferir archivos, cambiando así la forma en que se comunican.

Y es que de acuerdo con la intervención de John Farrel, director de YouTube Latinoamérica en EmTech México 2013, en la actualidad los usuarios de Internet en México invierten más de cinco horas todos los días a navegar en la web, esto es 67 minutos más que el año pasado, lo que enfatiza la necesidad de que los empresarios y emprendedores cambien sus estrategias de negocios para llegar de manera adecuada al mercado.

“Existen diversos factores que cambian el ritmo de los negocios en el mundo, el principal de ellos es la facilidad con que ahora la gente puede navegar en la web, pues a nivel mundial se realizan diariamente más de un millón 200 mil transacciones de comercio electrónico”, comentó Farrel.

No obstante, de acuerdo con Evan Hernshaw-Plath, director de tecnología de NEO, los empresarios tienden a subestimar el poder que tiene el uso de Internet y de otras herramientas tecnológicas dentro de los negocios, motivo por el cual enfatizó en la necesidad de que cambien sus ideas al respecto.

“En la actualidad la clave para tener éxito en un negocio ya no es trabajar más, sino hacer más rápidos sus servicios a través del uso de la tecnología”, explicó Evan Hernshaw-Plath

Por ello para lograr que los empresarios y emprendedores incorporen la tecnología en sus modelos de negocio, Farrel y Hernshaw proporcionaron los siguientes consejos a los asistentes al EmTech México:

  • Lanza campañas interactivas por Internet para que conozcas mejor a los potenciales clientes virtuales
  • Mide los resultados que tengan tus campañas para saber qué debes modificar en tu comunicación
  • Escucha los problemas de los consumidores para que puedas desarrollar productos y servicios que resuelvan sus necesidades
  • Busca resolver problemas de la localidad en la que te encuentres
  • Recuerda que el comercio a través de Internet requiere de aprendizaje constante

fabiola.naranjo@eleconomista.mx

CRÉDITO: 

Fabiola Naranjo

Mexicanos invierten 67 minutos más en la red que el año pasado

En México, alrededor de 2.8 millones de personas cuentan con acceso a Internet y lo utilizan no sólo para realizar búsquedas de información, sino también para transferir archivos, cambiando así la forma en que se comunican.

Y es que de acuerdo con la intervención de John Farrel, director de YouTube Latinoamérica en EmTech México 2013, en la actualidad los usuarios de Internet en México invierten más de cinco horas todos los días a navegar en la web, esto es 67 minutos más que el año pasado, lo que enfatiza la necesidad de que los empresarios y emprendedores cambien sus estrategias de negocios para llegar de manera adecuada al mercado.

“Existen diversos factores que cambian el ritmo de los negocios en el mundo, el principal de ellos es la facilidad con que ahora la gente puede navegar en la web, pues a nivel mundial se realizan diariamente más de un millón 200 mil transacciones de comercio electrónico”, comentó Farrel.

No obstante, de acuerdo con Evan Hernshaw-Plath, director de tecnología de NEO, los empresarios tienden a subestimar el poder que tiene el uso de Internet y de otras herramientas tecnológicas dentro de los negocios, motivo por el cual enfatizó en la necesidad de que cambien sus ideas al respecto.

“En la actualidad la clave para tener éxito en un negocio ya no es trabajar más, sino hacer más rápidos sus servicios a través del uso de la tecnología”, explicó Evan Hernshaw-Plath

Por ello para lograr que los empresarios y emprendedores incorporen la tecnología en sus modelos de negocio, Farrel y Hernshaw proporcionaron los siguientes consejos a los asistentes al EmTech México:

  • Lanza campañas interactivas por Internet para que conozcas mejor a los potenciales clientes virtuales
  • Mide los resultados que tengan tus campañas para saber qué debes modificar en tu comunicación
  • Escucha los problemas de los consumidores para que puedas desarrollar productos y servicios que resuelvan sus necesidades
  • Busca resolver problemas de la localidad en la que te encuentres
  • Recuerda que el comercio a través de Internet requiere de aprendizaje constante

fabiola.naranjo@eleconomista.mx

CRÉDITO: 

Fabiola Naranjo

Control de versión

Los repositorios administrados de documentos son importantes en el trabajo en equipo cuando varios miembros deben trabajar de manera simultánea o coordinada sobre los mismos documentos, pero también es útil en el caso de lobos solitarios. Control de versión es el arte de administrar cambios. Es una herramienta crítica en el desarrollo de software. Algunos […]

Los repositorios administrados de documentos son importantes en el trabajo en equipo cuando varios miembros deben trabajar de manera simultánea o coordinada sobre los mismos documentos, pero también es útil en el caso de lobos solitarios. Control de versión es el arte de administrar cambios. Es una herramienta crítica en el desarrollo de software.

Algunos sistemas de control de versión son administradores de software (Software Configuration Management). Estos sistemas están especí­ficamente diseñados para administrar árboles de código fuente y soportan el ciclo de vida de aplicaciones. Otros sistemas son repositorios generales de documentos.

Un repositorio de información para control de versión guarda un registro de los cambios hechos tanto a los datos como a la estructura misma de archivos. Un cliente puede no solo ver la última versión de los documentos guardados, sino también estados previos del sistema de archivos. Por ejemplo un cliente puede hacer consultas del tipo ¿Qué cambios se hicieron en un documento en la última semana?

El problema fundamental es por un lado ¿Cómo compartir información y coordinar modificaciones concurrentes a un grupo de documentos? Y complementariamente ¿Cómo recuperar estados anteriores de los documentos cuando una serie de cambios resultan inapropiados o se requieren variaciones de base común?

Un enfoque para evitar conflictos es reservar-modificar-cambiar (lock-modify-unlock). Este enfoque no siempre garantiza la integridad o coherencia de un sistema cuando se trabaja con múltiples documentos y serializa el trabajo innecesariamente cuando se pudiera hacer cambios independientes. Otro enfoque es copiar-modificar-integrar (copy-modify-merge). El repositorio puede asistir en el manejo de documentos y sus cambios, pero una persona necesita hacer el análisis de si un conjunto de cambios es valido y los miembros de un equipo deben mantener una buena comunicación.

En el caso particular del software algunas de las áreas que soporta un SCM son:

    • Administración de versiones múltiples, permitiendo a usuarios y desarrolladores reportas defectos y cambios con relación a versiones históricas.
    • Administración de equipos de desarrollo, permitiendo que varios programadores trabajen en un mismo archivo e integrando los cambios.
    • Auditorias de cambios.

Los sistemas de control de versión trabajan con dos elementos base: áreas de trabajo y repositorios. Las áreas de trabajo es donde se hacen cambios y el repositorio es el lugar donde se guardan los documentos de referencia que sincronizan el trabajo de todos y define el estado de la información. El repositorio guarda metadata que permite rastrear cambios y versiones.
El paradigma central de control de versión es Pedir/Aplicar (check out/commit). Todos los documentos se almacenan en el repositorio. El programador registra una copia en su área de trabajo y procede a aplicar cambios a su copia. Cuando los cambios son estables, se aplican al repositorio de acuerdo a polí­ticas de administración de cambios y resolución de conflictos.

Dos conceptos importantes en la administración de cambios son ramas (branches) y etiquetas (tags). La ramificación del código permite mantener el desarrollo del sistema y liberar versiones de acuerdo a plataformas, características y pruebas; O para pruebas de código experimental. Etiquetas son similares a ramas pero puntos de referencia en la misma línea de desarrollo, no a una variante del mismo.

El abuelito y punto de referencia de los sistemas de control de versión es CVS, referenciado a scripts escritos por Dick Grune y publicados en comp.sources.unix en diciembre de 1986.

Sistemas de control de versión:
CVS
Subversion
Perforce (p4)
BitKeeper
VOODOO Server
ClearCase
RCS (Revision Control System)

anonimized run

The Amnesic Incognito Live System or Tails is a Debian based Linux distribution aimed at preserving privacy and anonymity.[1] Actually, it is the next iteration of development on the previous Gentoo based Incognito Linux distribution.[2] All its outgoing connections are forced to go through Tor,[3] and direct (non-anonymous) connections are blocked. The system is designed […]

The Amnesic Incognito Live System or Tails is a Debian based Linux distribution aimed at preserving privacy and anonymity.[1] Actually, it is the next iteration of development on the previous Gentoo based Incognito Linux distribution.[2] All its outgoing connections are forced to go through Tor,[3] and direct (non-anonymous) connections are blocked. The system is designed to be booted as a live CD or USB, and leaves no trace on the machine unless explicitly told to do so. The Tor Project has provided most of the financial support for development.[4]

Tails is a live system that aims at preserving your privacy and anonymity. It helps you to use the Internet anonymously almost anywhere you go and on any computer but leave no trace using unless you ask it explicitly.

It is a complete operating-system designed to be used from a DVD or a USB stick independently of the computer’s original operating system. It is Free Software and based on Debian GNU/Linux.

Tails comes with several built-in applications pre-configured with security in mind: web browser, instant messaging client, email client, office suite, image and sound editor, etc.

Read about how you can help improving Tails documentation.

General information

Get Tails

First steps with Tails

Connect to the Internet anonymously

Encryption & privacy

Work on sensitive documents

Advanced topics

quantOS, based on Linux Mint 11, is a hardened Linux distro for secure daily use. quantOS leverages AppArmor application security profiles, Arkose Desktop Application Sandboxing and Vidalia for creating secure Tor connections for enhanced privacy.


The DemocraKey was invented by Kirk, in response to government snooping and censorship in China and the United States. Six months later, he started DemocraKey.com to promote the DemocraKey and get help with his project.
Read more here.

kaos.theory’s Anonym.OS LiveCD is a bootable live cd based on OpenBSD that provides a hardened operating environment whereby all ingress traffic is denied and all egress traffic is automatically and transparently encrypted and/or anonymized.

Liberté Linux is a secure, lightweight, and easy to use Gentoo-based Linux distribution intended as a communication aid in hostile environments. Liberté installs on a USB key, and boots on any computer or laptop.

Gentoo Linux, a special flavor of Linux that can be automatically optimized and customized for just about any application or need. Extreme performance, configurability and a top-notch user and developer community are all hallmarks of the Gentoo experience. To learn more, read our about page.
Continue reading “anonimized run”

cracking password hashes

Forgot your Windows admin password? Reinstall? Oh no… But not any more… This is a utility to reset the password of any user that has a valid local account on your Windows system. Supports all Windows from NT3.5 to Win7, also 64 bit and also the Server versions (like 2003 and 2008) You do not […]

Forgot your Windows admin password?

Reinstall? Oh no… But not any more…


  • This is a utility to reset the password of any user that has a valid local account on your Windows system.
  • Supports all Windows from NT3.5 to Win7, also 64 bit and also the Server versions (like 2003 and 2008)
  • You do not need to know the old password to set a new one.
  • It works offline, that is, you have to shutdown your computer and boot off a CD or USB disk to do the password reset.
  • Will detect and offer to unlock locked or disabled out user accounts!
  • There is also a registry editor and other registry utilities that works under linux/unix, and can be used for other things than password editing.

Windows stores its user information, including crypted versions of the passwords, in a file called ‘sam’, usually found in windowssystem32config. This file is a part of the registry, in a binary format previously undocumented, and not easily accessible. But thanks to a German(?) named B.D, I’ve now made a program that understands the registry.

This site provides CD and floppy images for end users to easily edit their forgotten passwords. But it also provides full source code and binary builds of the tools to allow others to use as they like for other purposes. Registry format documentation also available.

Latest release is 110511 (2011-05-11)

The following is available for download and information:

2011-05-11

  • Some major! new features for people using the registry utilites, but not much changes to password reset.

2009-12-01

  • New site, official URL is now: http://pogostick.net/~pnh/ntpasswd/
  • All releases still contains old mail address, please note NEW mailaddress is pnh@pogostick.net. Old mailaddress vil be invalid after January 1st 2010.
  • No new release, 2008-08-02 is still newest. Hope to release new early 2010.

A rainbow table is a precomputed table for reversing cryptographic hash functions, usually for cracking password hashes. Tables are usually used in recovering the plaintext password, up to a certain length consisting of a limited set of characters. It is a practical example of a space/time trade-off, using more computer processing time at the cost of less storage when calculating a hash on every attempt, or less processing time and more storage when compared to a simple lookup table with one entry per hash. Use of a key derivation function that employ a salt makes this attack infeasible.

Rainbow tables are an application of an earlier, simpler algorithm by Martin Hellman.[1]

Hash Sets are used in a data analysis technique called Hash Analysis, which uses the MD5, SHA1 and SHA256 hash of files to verify the files on a storage device. A hash uniquely identifies the contents of a file, regardless of filename and can be used to identify the presence of malicious, contraband, or incriminating files such as bootleg software, pornography and viruses. See this video of hash sets in use in OSForensics.

Rainbow tables are available for free from http://www.freerainbowtables.com/, approximately a 2.5TB (2500 GB) download.

The hash sets are available for free from the National Software Reference Library, approximately a 1.7GB download, and there is a OSForensics tutorial on how to convert them for use within OSForensics. Please note that conversion may take several days.

The hash sets and rainbow tables created by PassMark are also available from the OSForensics Download page.  We are not selling the tables, only the service of copying them onto a 3TB hard drive and shipping.

Any computer system that requires password authentication must contain a database of passwords, either hashed or in plaintext, and various methods of password storage exist. Because the tables are vulnerable to theft, storing the plaintext password is dangerous. Most databases therefore store a cryptographic hash of a user’s password in the database. In such a system, no one — including the authentication system — can determine what a user’s password is, simply by looking at the value stored in the database. Instead, when a user enters his or her password for authentication, it is hashed and that output is compared to the stored entry for that user (which was hashed before being stored). If the two hashes match, access is granted.

A thief who steals the (hashed) password table cannot merely enter the user’s (hashed) database entry to gain access since the authentication system would hash that a second time, producing a result which does not match the stored value, which was hashed only once. In order to learn a user’s password, the thief must reverse the hash to find a password which produces the hashed value. A good authentication system will make this process as difficult as possible by using a one-way hash function, that has a high ratio for the time to invert the function compared to the time to compute the function.

Rainbow tables are one tool that has been developed in an effort to derive a password by looking only at a hashed value.

Rainbow tables are not always needed, for there are simpler methods of hash reversal available. Brute-force attacks and dictionary attacks are the simplest methods available, however these are not adequate for systems that use large passwords, because of the difficulty of storing all the options available and searching through such a large database to perform a reverse-lookup of a hash.

To address this issue of scale, reverse lookup tables were generated that stored only a smaller selection of hashes that when reversed could generate long chains of passwords. Although the reverse lookup of a hash in a chained table takes more computational time, the lookup table itself can be much smaller, so hashes of longer passwords can be stored. Rainbow tables are a refinement of this chaining technique and provide a solution to a problem called chain collisions.

Ophcrack is a free Windows password cracker based on rainbow tables. It is a very efficient implementation of rainbow tables done by the inventors of the method. It comes with a Graphical User Interface and runs on multiple platforms.

The multi-platform password cracker Ophcrack is incredibly fast. How fast? It can crack the password “Fgpyyih804423″ in 160 seconds. Most people would consider that password fairly secure. The Microsoft password strength checker rates it “strong”. The Geekwisdom password strength meter rates it “mediocre”.

Why is Ophcrack so fast? Because it uses Rainbow Tables.

Features:

  • » Runs on Windows, Linux/Unix, Mac OS X, …
  • » Cracks LM and NTLM hashes.
  • » Free tables available for Windows XP and Vista/7.
  • » Brute-force module for simple passwords.
  • » Audit mode and CSV export.
  • » Real-time graphs to analyze the passwords.
  • » LiveCD available to simplify the cracking.
  • » Dumps and loads hashes from encrypted SAM recovered from a Windows partition.
  • » Free and open source software (GPL).

Note that all rainbow tables have specific lengths and character sets they work in. Passwords that are too long, or contain a character not in the table’s character set, are completely immune to attack from that rainbow table.

Unfortunately, Windows servers are particularly vulnerable to rainbow table attack, due to unforgivably weak legacy Lan Manager hashes. I’m stunned that the legacy Lan Manager support “feature” is still enabled by default in Windows Server 2003. It’s highly advisable that you disable Lan Manager hashes, particularly on Windows servers which happen to store domain credentials for every single user. It’d be an awful shame to inconvenience all your Windows 98 users, but I think the increase in security is worth it.

I read that Windows Server 2008 will finally kill off LM hashes when it’s released next year. Windows Vista already removed support for these obsolete hashes on the desktop.

The Ophcrack tool isn’t very flexible. It doesn’t allow you to generate your own rainbow tables. For that, you’ll need to use the Project Rainbow Crack tools, which can be used to attack almost any character set and any hashing algorithm. But beware. There’s a reason rainbow table attacks have only emerged recently, as the price of 2 to 4 gigabytes of memory in a desktop machine have approached realistic levels. When I said massive, I meant it. Here are some generated rainbow table sizes for the more secure NT hash:

Character Set Length Table Size
ABCDEFGHIJKLMNOPQRSTUVWXYZ 14 0.6 GB
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 14 3 GB
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()-_+= 14 24 GB
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()-_+=~`[]{}|:;"'<>,.?/ 14 64 GB

A rainbow table attack is usually overkill for a desktop machine. If hackers have physical access to the machine, security is irrelevant. That’s rule number 3 in the 10 Immutable Laws of Computer Security. There are any number of tools that can reset passwords given physical access to the machine.

But when a remote hacker obtains a large list of hashed passwords from a server or database, we’re in trouble. There’s significant risk from a rainbow table attack. That’s why you should never rely on hashes alone– always add some salt to your hash so the resulting hash values are unique. Salting a hash sounds complicated (and vaguely delicious), but it’s quite simple. You prefix a unique value to the password before hashing it:

hash = md5('deliciously-salty-' + password)

If you’ve salted your password hashes, an attacker can’t use a rainbow table attack against you– the hash results from “password” and “deliciously-salty-password” won’t match. Unless your hacker somehow knows that all your hashes are “delicously-salty-” ones. Even then, he or she would have to generate a custom rainbow table specifically for you.

To begin, password storage 101: servers don’t usually store actual passwords. Instead, they hash the password, store the hash, and discard the password. The hash can verify a password from a login page, but can’t be reversed back to the text of the password. So when you inevitably lose your SQL password table, you haven’t exposed all the passwords; just the crappy ones.

Now let’s re-explain rainbow tables:

  1. take a “dictionary” —- say, of all combinations of alphanumerics less than 15 characters
  2. hash all of them
  3. burn the results onto a DVD.

You now have several hundred billion hash values that you can reverse back to text —- a “rainbow table”. To use,

  1. take your stolen table of hashes
  2. for each hash
  3. find it in the rainbow table.

If it’s there, you cracked it.

 

.

Here’s what you need to know about rainbow tables: no modern password scheme is vulnerable to them.

Rainbow tables are easy to beat. For each password, generate a random number (a nonce). Hash the password with the nonce, and store both the hash and the nonce. The server has enough information to verify passwords (the nonce is stored in the clear). But even with a small random value, say, 16 bits, rainbow tables are infeasible: there are now 65,536 “variants” of each hash, and instead of 300 billion rainbow table entries, you need quadrillions. The nonce in this scheme is called a “salt”.

Cool, huh? Yeah, and Unix crypt —- almost the lowest common denominator in security systems —- has had this feature since 1976. If this is news to you, you shouldn’t be designing password systems. Use someone else’s good one.

 

.

No, really. Use someone else’s password system. Don’t build your own.

Most of the industry’s worst security problems (like the famously bad LANMAN hash) happened because smart developers approached security code the same way they did the rest of their code. The difference between security code and application code is, when application code fails, you find out right away. When security code fails, you find out 4 years from now, when a DVD with all your customer’s credit card and CVV2 information starts circulating in Estonia.

 

.

Here’s a “state of the art” scheme from a recent blog post on rainbow tables and salts:

hash = md5('deliciously-salty-' + password)

There are at least two problems with this code. Yeah, the author doesn’t know what a salt is; “deliciously-salty-” is not a nonce (also, Jeff, your computer really doesn’t care if you seperate the password from the nonce with a dash; it’s a computer, not a 2nd grade teacher).

But there’s a much bigger problem with this code: the letters “md5”.

Two reasons.

1.

You’re expecting me to go off on a rant about how there is no redeeming quality to justify using MD5 in 2007. That’s true (MD5 is broken; it’s too slow to use as a general purpose hash; etc). But that’s not the problem.

2.

The problem is that MD5 is fast. So are its modern competitors, like SHA1 and SHA256. Speed is a design goal of a modern secure hash, because hashes are a building block of almost every cryptosystem, and usually get demand-executed on a per-packet or per-message basis.

Speed is exactly what you don’t want in a password hash function.

Modern password schemes are attacked with incremental password crackers.

Incremental crackers don’t precalculate all possible cracked passwords. They consider each password hash individually, and they feed their dictionary through the password hash function the same way your PHP login page would. Rainbow table crackers like Ophcrack use space to attack passwords; incremental crackers like John the Ripper, Crack, and LC5 work with time: statistics and compute.

The password attack game is scored in time taken to crack password X. With rainbow tables, that time depends on how big your table needs to be and how fast you can search it. With incremental crackers, the time depends on how fast you can make the password hash function run.

The better you can optimize your password hash function, the faster your password hash function gets, the weaker your scheme is. MD5 and SHA1, even conventional block ciphers like DES, are designed to be fast. MD5, SHA1, and DES are weak password hashes. On modern CPUs, raw crypto building blocks like DES and MD5 can be bitsliced, vectorized, and parallelized to make password searches lightning fast. Game-over FPGA implementations cost only hundreds of dollars.

Using raw hash functions to authenticate passwords is as naive as using unsalted hash functions. Don’t.

 

.

What is the state of the art here?

1.

First, what your operating system already gives you: a password scheme “optimized” to be computationally expensive. The most famous of these is PHK’s FreeBSD MD5 scheme.

The difference between PHK’s scheme and the one you were about to use for your social shopping cart 2.0 application is simple. You were just going to run MD5 on a salt and a password and store the hash. PHK runs MD5 for thousands of iterations. That’s called “stretching”.

PHK’s MD5 scheme is straightforward to code and comes with Linux and BSD operating systems. If you have to choose between the PHP code you have now and PHK’s scheme, you choose PHK’s scheme or you fail your PCI audit. [â??]

2.

The best simple answer is “adaptive hashing”, which Neils Provos and David Mazieres invented for OpenBSD in 1999. Their original scheme is called “bcrypt”, but the idea is more important than the algorithm.

There are three big differences between Provos-Mazieres and PHK’s scheme:

  1. Bcrypt was invented by two smart guys and PHK’s was only invented by one smart guy. That’s literally twice the smart.
  2. Bcrypt uses Blowfish instead of MD5. Blowfish is a block cipher with a notoriously expensive setup time. To optimize Blowfish to run much faster, you’d have to contribute a major advance to cryptography. We security practioners are all “betting people”, and we usually like to place our bets on the side that “demands major advances in cryptography”.
  3. Provos and Mazieres extended Blowfish. They call theirs “Eksblowfish”. Eksblowfish is pessimized: the setup time takes even longer than Blowfish. How long? Your call. You can make a single password trial take milliseconds, or you can make it take hours.

Why is bcrypt such a huge win? Think of the problem from two perspectives: the server, and the attacker.

First, the server: you get tens of thousands of logins per hour, or tens per second. Compared to the database hits and page refreshes and IO, the password check is negligable. You don’t care if password tests take twice as long, or even ten times as long, because password hashes aren’t in the 80/20 hot spot.

Now the attacker. This is easy. The attacker cares a lot if password tests take twice as long. If one password test takes twice as long, the total password cracking time takes twice as long.

Get it?

The major advantage of adaptive hashing is that you get to tune it. As computers get faster, the same block of code continues to produce passwords that are hard to crack.

3.

Finally, as your attorney in this matter, I am required to inform you about SRP.

SRP is the Stanford Secure Remote Password protocol. It is a public key cryptosystem designed to securely store and validate passwords without storing them in the clear or transmitting them in the clear.

That design goal is cooler than it sounds, because there’s usually a tradeoff in designing password systems:

  1. You can store a hash of the password. Now if you lose the password database, you haven’t exposed the good passwords. However, you also don’t know the password cleartext, which means that to validate passwords, your customers need to send them to you in the clear.
  2. You can use a challenge-response scheme, where both sides use a math problem to prove to each other that they know the password, but neither side sends the password over the wire. These schemes are great, but they don’t work unless both sides have access to the cleartext password —- in other words, the server has to store them in the clear.

Most practitioners will select the hashing scheme. Both attacks —- stolen databases and phished passwords —- happen all the time. But stolen databases compromise more passwords.

SRP resolves the tradeoff. It’s an extension of Diffie-Hellman. The salient detail for this post: instead of storing a salted password hash, you store a “verifier”, which is a number raised to the (obviously very large) power of the password hash modulo N.

If you understand DH, SRP is just going to make sense to you. If you don’t, the Wikipedia will do a better job explaining it than I will. For the test next Wednesday, you need to know:

  • SRP is related to Diffie-Hellman.
  • SRP is a challenge-response protocol that lets a server prove you know your password without your password ever hitting the wire.
  • SRP doesn’t require you to store plaintext passwords; you store non-reversable cryptographic verifiers.
  • “Cracking” SRP verifiers quickly would involve a significant advancement to cryptography.
  • SRP is simple enough to run out of browser Javascript.

Awesome! Why aren’t you using SRP right now? I’ll give you three reasons:

  • SRP is patented.
  • To make it work securely in a browser, you have to feed the login page over SSL; otherwise, like Meebo, you wind up with a scheme that can be beaten by anyone who can phish a web page.
  • SRP is easy to fuck up, so the first N mainstream Rails or PHP or Pylons SRP implementations are going to be trivially bypassable for at least the first year after they’re deployed.

 

.

What have we learned?
We learned that if it’s 1975, you can set the ARPANet on fire with rainbow table attacks. If it’s 2007, and rainbow table attacks set you on fire, we learned that you should go back to 1975 and wait 30 years before trying to design a password hashing scheme.

We learned that if we had learned anything from this blog post, we should be consulting our friends and neighbors in the security field for help with our password schemes, because nobody is going to find the game-over bugs in our MD5 schemes until after my Mom’s credit card number is being traded out of a curbside stall in Tallinn, Estonia.

We learned that in a password hashing scheme, speed is the enemy. We learned that MD5 was designed for speed. So, we learned that MD5 is the enemy. Also Jeff Atwood and Richard Skrenta.

Finally, we learned that if we want to store passwords securely we have three reasonable options: PHK’s MD5 scheme, Provos-Maziere’s Bcrypt scheme, and SRP. We learned that the correct choice is Bcrypt.

The Rainbow Table Is Dead

Well ok, not really.  But you should not be securing hashes against rainbow tables anymore, you need to secure them against brute forcing.  Rainbow tables are still very effective for simple hashes (md5($password)), but just because an algorithm is hard to use for a rainbow table doesn’t mean that it is safe, because the rainbow table is dead…

What Is A Rainbow Table?

Generically, a rainbow table is nothing more than a time-storage trade-off.  Instead of recomputing a function every time you want to attack it, a rainbow table is generated by pre-computing a large number of input permutations to that function.  Then, given a result, it should be easy to look-up the result in a table to determine which input(s) generate it.  That way, you can effectively reverse a non-reversible function…

Applied to hashing (and in this particular context, password hashing), a rainbow table is generated by generating a large number of candidate passwords (typically random, but may be dictionary based as well), and storing the password->hash mapping in a database or data file.  Then simply look-up the hash that you have to get the plain text password that may have generated it.

The First Problem: Storage Space

For a rainbow table to be effective, it must have a lot of candidate passwords in it.  Let’s take a look at an MD5 rainbow table, and see how much storage space it will require.  Let’s also assume that it will be stored in MySQL with a char(10) column for the password, and binary(16) column for the hash (storing it in a binary format).  So each row will have approximately 26 bytes of data (not including any overhead).  And lets look at source passwords of all printable non-control ASCII characters (there are 77 of them).

Length Of Password Number Of Possibilities Size Of Table
4 characters 35,153,041 913 MB
5 characters 2,706,784,157 70 GB
6 characters 208,422,380,089 5.4 TB
7 characters 16,048,523,266,853 417 TB
8 characters 1,235,736,291,547,681 32 PB (PetaBytes, 10^15)

As you can see, the number of possibilities goes up quite fast as you support longer passwords. So that means for a rainbow table to be effective, it must actually reduce the number of possible candidates that it stores.  After all, who would want to download 32 Petabytes to crack a hash?  Sure, you could use a dictionary and permutations on the words to try to reduce the search space significantly without cutting down on effectiveness much (statistically speaking).  But that also means a much greater resistance to strong-but-short passwords.

The Second Problem: Hash Algorithms

Hash algorithms are designed with two things in mind: security and speed.  Their typical role is to create a MAC (message authentication code) for a document.  So by hashing the document, you can tell if the original document is the same as long as the generated hashes match.  So since they need to process a lot of data (potentially gigabytes or more), a key requirement is speed.  In fact, most modern “secure” algorithms are even faster than their predecessors on modern hardware (for example, sha256 is several times faster than md5 which is much older).

The faster the hash function is, the less reason there is to use a rainbow table.  After all, the rainbow table is just a time-storage trade-off (you’re reducing time by using more storage).  So since hash functions are only getting faster, the benefit of a rainbow table is diminished.

The Third Problem: Salts

Salts are a random token (usually used only once) that is combined with the password before hashing.  They are specifically used to prevent the use of a rainbow table.  Note that using a salt doesn’t directly prevent a rainbow table from being used, it just reduces its effectiveness.  It artificially increases the length of a password in the rainbow table (so to crack a 4 character password with a 4 character salt, you’d need to generate an 8 character rainbow table).  In practice, most usual lengths of salts are too big to generate a universal rainbow table (for a 32 character salt and 8 character password, the rainbow table would need to be 2.8*10^75 bytes).  So another method that attackers use is to steal the salt along with the hash, and then generate a new rainbow table for each salt.  That’s why it’s so important to use a unique salt for each stored password (it reduces the return on investment that the new rainbow table will provide).

Why Were They Popular?

Rainbow tables were popular for one key reason: Up until very recently, disk was significantly cheaper than CPU time.  It was easier to pre-compute the rainbow table (which can take a very long time) than to do hashes as needed.

The Reality Today

I know what you’re thinking…  ”Isn’t disk space even cheaper today than it was a few years ago?”…  Yes it is.  But CPU time is even cheaper by several orders of magnitude.  In 2000, the cost of a hard drive was about $13 per gigabyte.  Today, the cost of a hard drive is about $0.10 per gigabyte.  That’s 2 orders of magnitude!  But if we look at a Pentium 3, it could achieve about 300 mflops (millions of floating point operations per second) for $825, for an average of $2.75 per mflop.  A modern Intel i7 can do about 107,000 mflops for $999, averaging about $0.0093 per mflop.  That’s a 4 order or magnitude difference!

But wait; we have a reasonably new contender!  Enter, the GPU.  A single Radeon HD 6990M can achieve approximately 1,600,000 mflops for about $700.  Computed down, that’s a whopping $0.00043 per mflop.  That’s about an order of magnitude less than the Intel i7, and 5 orders of magnitude less than the P3.  Not to mention the raw performance is 4 orders of magnitude greater!

How Many Hashes Per Second?

Well, there’s a password cracking tool called John the Ripper.  Currently, it can hash up to 514 million (DES crypt()) hashes per second (abbreviated mhps from here out) on a modern 4 core CPU (Intel x7550).  When using a more modern algorithm such as sha256, John the Ripper can do a rather measly 200,000 hashes per second.  At that rate it would take 3 minutes to generate a 4 character rainbow table.  Fast, but not fast enough for our purposes.

Now, let’s look at what a GPU can do.  Bitcoin currently uses 2 internal sha256 rounds to compute a single “hash”.  So when we look at the performance numbers they are reporting, we need to realize that’s for 2 sha256 hashes.  If we look at the fastest single card setup (an ATI 5970), it does over 860 million bitcoin hashes per second.  That’s over 1.720 billion sha256 hashes per second!  And a 3 card setup can hit almost 4.2 billion sha256 hashes per second.  So let’s take a look at our chart again, this time for a salted sha256 password:

Length Of Password Number Of Possibilities CPU GPU
4 characters 35,153,041 3 minutes 0.0083 seconds
5 characters 2,706,784,157 3.75 hours 0.64 seconds
6 characters 208,422,380,089 12 days 49 seconds
7 characters 16,048,523,266,853 2.5 years 1.06 hours
8 characters 1,235,736,291,547,681 195 years 3.4 days

So, for about $2100, we can have a set of 3 GPUs that can brute force any printable 8 character password possible in about 3.4 days. And that’s at the absolute worst case possible.  If we started to do intelligence things such as using a dictionary as the base for our search, we could likely find that password much, much faster.

The Other Benefit To Brute Forcing

The other benefit to brute forcing, is you invest practically nothing in the algorithm.  For a rainbow table you need to provide both cpu time to generate (a lot of it) and storage space (a lot of it). Not to mention thinks like disk seek time.  An average high end hard drive has a seek time of around 4ms.  So to merely read the data stored in a rainbow table for a 4 character password, you’re spending about 1/2 the time taken by the gpu just seeking in the database file.  Then, the computer needs to do a full scan of all of the data to search for the hash value.  So in the end, for a 4 character password, it’s likely cheaper in all accounts just to brute force it on a GPU than it is to generate a rainbow table.

A Word On Entropy

All of the numbers that I’ve used in this article are based off the assumption that password choice is fully random.  That’s the worst case situation.  That means that given n bits of data, it would take on average 2^(n-1) tries to have a 50% chance of guessing it.  So for a pure random 8 character password (printable characters), you’d need on average about 1.7 days on a GPU to brute force it.  Each character in our pure random password has about 6.26 bits of entropy (due to the 77 possible characters, instead of 256).  So an 8 character password has about 50 bits of entropy (and this is true, since 2^50 is about 10^15, which is what we calculated above).

But that’s not the way of the world.  The vast majority of passwords are user generated.  And user generated passwords tend to have significantly less entropy.  In fact, according to NIST (Appendix A), a 8 character password with symbols and numbers would only have about 18 bits of entropy.  It could be 24 bits if there existed both upper-case and lower-case characters.  But 2^24 is only about 16 million.  So notice that our 4 character random password is actually on average twice as strong as a user-selected 8 character password.  In the worst case, it would take the full 2^50 tries to guess a user selected 8 character password, so that’s the same.  But the 50% chance occurs much sooner at 2^23 than the random password at 2^49.

Speaking of entropy, we’re going to revisit the concept in another post soon (specifically about what a recent web-comic pontificated)…

Finally

The overall point is simple.  A rainbow table is a useful tool.  But it’s also an outdated tool that doesn’t mean nearly as much as it used to.  In the era of the cheap GPU, brute forcing is more than a possibility, it’s a fact.  Using an algorithm because it’s resistant to a rainbow table is not only obsolete, it bypasses the bigger problem.  You need to hash your passwords so that they are hard to brute force.  If they are hard to brute force, they will be hard to rainbow table as well.

Presently, there are about 3 algorithms for PHP that will provide adequate defense against brute forcing. BCrypt (called Blowfish in PHP’s docs), PBKDF2 and PHPASS‘s internal function (in order from strongest to weakest).  It’s worth noting that projects such as Drupal, PHPBB and WordPress have all implemented either PHPASS or a derivative thereof.  All of the algorithms accept a “work factor” which controls how much CPU time the algorithm takes.  By artificially slowing down the hash, brute forcing is made significantly harder (but not impossible).

Use an algorithm that has protections against brute forcing, as protecting against rainbow tables alone is a lost battle…

Posted by Anthony Ferrara at 8/16/2011 10:00:00 AM