Wednesday, 29 December, 2010

Running Android Applications on Ubuntu

Step 1 - Installing the requirements

Until the download is over, make sure that you have Java installed and the 32-bit libraries (for the x86_64 users ONLY). If you don't have Java (or the 32-bit libraries), go to System -> Administration -> Synaptic Package Manager...



...search for openjdk and double-click on the openjdk-6-jre entry...




...then, search for ia32-libs (ONLY if you are on a x86_64 machine), and double-click on the ia32-libs entry...



Now, click the "Apply" button to install the packages. Wait for the packages to be installed and close Synaptic when the process is finished.

Step 2 - Android Setup

When the Android SDK download is over, right-click on the file and choose the "Extract Here..." option...



Enter the extracted folder, then enter the tools folder and double click the android file. Click on the "Run" button when you will be asked what you want to do, and the Android SDK and AVD Manager interface will appear...



Go to the "Settings" section and make sure you check the "Force https://..." box. Click the "Save & Apply" button....



Now go to the "Installed Packages" section and click the "Update All" button. A window will appear with all the available updates. Click the "Install Accepted" button...




...and wait for the packages to be downloaded and installed. It will take a while if you have a slow bandwidth, so go see a movie or something until it finishes...



Close the update window when it's done and you will see all the installed SDKs in the "Installed Packages" section.

And now, let's create the virtual device. Go to the "Virtual Device" section and click the "New" button. In the new window do the following:

- put a name to the device;
- select a target (Android system);
- put the size for the SD Card;
- add the hardware you want have in the emulator.

It should look something like this...




Click the "Create AVD" button when you're done setting up the virtual device and wait for it to finish. It takes about 1 minute, and you'll be notified by a pop-up...



Note: In the above setup, we've created a virtual device for Android 2.0.1 with a 2 GB SD card and the following hardware components: SD Card, GPS, Accelerometer, Track-ball and touch-screen.

Now click the "Start" button, and the "Launch" button from the next dialog, and the emulator will start...








To make things a lot simpler let's create a desktop shortcut, so you won't have to open the terminal every time and type some command, in order to start the Android emulator. Therefore, right-click on your desktop and choose the "Create Launcher..." option...




In the Create Launcher window, type "Android Emulator" (without quotes) in the Name field, and paste the below line in the Command field. Optionally, you can also put a nice icon if you click the icon button on the left...

/home/YOURUSERNAME/android-sdk-linux_86/tools/emulator @softpedia




Note: Please replace YOURUSERNAME and the name of the Android Virtual Device (softpedia in our case) with your USERNAME and the name you gave to the virtual device. DO NOT REMOVE the @ sign.

Step 3 - Run applications in Android

All you have to do now is double-click that desktop shortcut you've just created. The Android emulator will start. Wait for the operating system to load...



When the Android operating system has loaded, you can install and test applications. If you are used with the Android platform, you already know how to do that, but if this is your first time... follow the next instructions.






Click the Browser icon, wait for the browser to load and click Menu -> Go to URL. Enter the address from where you can download an Android application with the apk extension. For example, we've easily installed Android's Fortune from Launchpad...
















...all you have to do is follow the on-screen instructions!

Have fun, and do not hesitate to comment if you want to know more about Android, or if you're stuck somewhere in the tutorial.


Reference : http://news.softpedia.com/news/How-to-Run-Android-Applications-on-Ubuntu-115152.shtml

Sunday, 13 September, 2009

USB BackTrack

BackTrack is a Live Linux distribution based on SLAX that is focused purely on penetration testing. Distributed by remote-exploit.org, BackTrack is the successor to Auditor. It comes prepackaged with security tools including network analyzers, password crackers, wireless tools and fuzzers. Although originally designed to Boot from a CD or DVD, BackTrack contains USB installation scripts that make portable installation to a USB device a snap. In the following tutorial, we cover the process of installing BackTrack to a USB flash drive from within a working Windows environment.



How to install BackTrack to a USB device:

Note: USB installation of BacktTack performs like the Live CD. Currently a persistence BackTrack feature is outside the scope of this tutorial.

1. Download the (Portable Backtrack) USB BackTrack (Extended) version
2. Extract the Boot and BT3 folders to the root of your USB device
3. Navigate to the Boot folder on your "USB device" and click bootinst.bat (click continue if the following error appears)



4. Follow the onscreen instructions to make the device bootable
5. Once the USB install script has finished, reboot your computer and set your BIOS or Boot Menu to boot from the USB device

Reference : http://www.pendrivelinux.com

Sunday, 10 May, 2009

Internet Connection Sharing using "Firestarter " in LINUX

Firestarter is a GPL-licensed graphical firewall configuration program for iptables, the powerful firewall included
in Linux kernels 2.4 and 2.6. Firestarter supports network address translation for sharing an Internet connection
among multiple computers, and port forwarding for redirecting traffic to an internal workstation. Firestarter's
clean and easy to use graphical user interface takes the time out of setting up a custom firewall.

Firestarter has the ability to share the firew all host's Internet connection among all the computers on your
local netw ork. This is done through a technique called Netw ork Address Translation, or NAT. To the outside
w orld the cluster of machines w ill look like a single machine w ith a single IP address.

Step by Step How to Install "FIRESTARTER"

1. Synaptic Package Manager



Click on Firestarter --->MarkInstall--->APPLY

2. Running Firestarter as below



3. Choose Type Internet Connection base on your Network Method



Choose TOP one if your method such as ADHOC
Choose DHCP as below Method Setting

The physical setup and network device settings
==============================================
The procedure for setting up a netw ork using
connection sharing is essentially the same
w hether you have only tw o computers or a more
complex netw ork w ith hubs or sw itches
connecting multiple computers. For this example
w e w ill be assuming that the Internet connected
device on the firew all is an Ethernet card, but a
modem or ISDN w ill w ork too.
The Firew all/gatew ay machine connected to the
Internet w ill need tw o netw ork cards and the
clients need one each.
The first netw ork card in the firew all, the external interface, w ill be the one physically connected to the
Internet. This card is usually automatically configured w ith DHCP. The second netw ork card in the firew all,
the internal interface, w ill be connected to the client machines via either a crossover cable if the connection
goes directly to another computer, or regular cable if you have a hub or sw itch.
The internal interface of the firew all needs to be
statically configured. There are many w ays to
configure a netw ork interface depending on the
distribution you use. Fedora and Red Hat Linux ship
w ith a simple command line tool called netconfig and a
more sophisticated graphical tool called system-config-network. system-config-network w orks better w ith
multiple netw ork cards in the same machine, so w e recommend you try it. Other distributions include their
ow n configuration tools, for example in SuSE you w ould use the Yast program.
No matter how you decide to configure the netw ork cards, these are settings you should enter:

For the external device (usually eth0):

Enable dynamic IP configuration (DHCP)
That's it. You're done, don't touch this card further.
The internal device (usually eth1):
Disable dynamic IP configuration
IP address: 192.168.0.1
Netmask: 255.255.255.0
Default gatew ay (IP):
Any changes you make w ill take effect after a reboot, or more elegantly after a restart of the netw ork
services (run "/etc/init.d/network restart" as root in most distributions).

Configuring the clients
========================

There are tw o w ays to configure the clients. The more elegant and in the long run easier w ay is to run a
DHCP service on the firew all. A DHCP server distributes the netw ork settings such the IP address, the
default gatew ay, nameservers, etc. at run time to the each client. The alternative to using a DHCP server is
to configure every client manually.
Using the DHCP service is as easy as simply enabling it in Firestarter. For more information about the service
and how to configure it, refer to the section on configuring the DHCP server.
When using DHCP, the clients need only be configured to use dynamic IP configuration. No other settings
need to be changed.
Configuring the clients manually
If you do not w ish to use the DHCP service, configure the netw ork devices of the clients to use the follow ing
settings:
Disable dynamic IP configuration
IP address: 192.168.0.2 to 192.168.0.254, w ith each client using an unique IP
Netmask: 255.255.255.0
Default gatew ay (IP): 192.168.0.1
Primary nameserver: Set this to the same nameserver as used on the firew all. You can see the correct
setting in the /etc/resolv.conf file on the firew all.
Restart the network service and you're done.