Below are the Steps that will unblock all the sites that are blocked by proxy server in your university or Office.

Assumptions:

I will be assuming you are up to date.

• Windows 7
• Firefox
• Sound working Mind

Tools to Download:

Download JAP from the Following Link

http://anon.inf.tu-dresden.de/win/jap_all/japsetup.exe

Installation:

• After Download, Install JAP
• In Installation Options, Select JAP and JAVA
• During installation it will prompt you to Install JAVA, Install it too.
• After Installation a wizard asking you to do some configuration and some other related stuff.
• Go ahead and cancel that wizard.
• You will be presented with a main screen of JAP.
• Do Not Close this Screen.

Firefox (Browser Settings):

• Open Firefox, go to tools -> Options -> Advance -> Network -> in connection section click the Setting button.
• In http proxy type 127.0.0.1 and enter the port 4001.  This setting is the same for all browsers.

JAB Configuration

• Click the CONFIG button on main screen of JAP
• In services Section Click infoServce.
• In setting tab click is.beneficium.de and the click set as default button.
• This will change the ports to port 80 and 443 which are never blocked by proxy servers and click Download List.
• Then go to Anonymity Section and click reload (Download List) button, this will download a list of servers, choose one of the server, check its speed and response time and look for what best works for you.
• Now go ahead and check the block sites, if they are working.
• If have are forced to enter a proxy server address, you can do by clicking the Network section (in JAP configuration), Enter 4001 in listen on port field. Your proxy address in host text field and port number in port field.
• Click Accept and OK.

Enjoy Browsing.

This is my First tutorial after one and half year since I posted my last tutorial, Its not actually a tutorial but its a Script for OpenERP 6 automatic Installation.

Yesterday I installed OpenERP 6.0.2, After Installation, I thought of why not to make a script of all the command that I issued so that its easy for me to reinstall again in future. I was using the methods provided in this site. I made a few of my own changes like I added the client as the site did not provided commands to do this.

Note:
ALL THE PASSWORDS ARE BY DEFAULT “pakistan” (without quotes, lower case), YOU CAN CHANGE THIS PASSWORD BY CHANGING IT IN OPENERP-SERVER.CONF.

Using the Script is simple.

• Download the Script from here
• Extract it
• Run the following Command to execute the Script
  #sh openerp-6.0.2-waqar.sh
• The rest of the process is self explatry, I guess there will be no problems
• The Script contains few errors but you can safly ignor them.
• Reboot your system after Installation
• After Installation run OpenERP client by going to /opt/openerp/client/openerp-client.py

This is the first version, I will try to improve it in the future

Enjoy…

After spending so many weeks on enabling GPRS on Openmoko, I finally found a way how to did.

I waisted more then 4 weeks on enabling GPRS on Openmoko, I hv flashed my Neo more then 70 times for different rootfs and kernels, Even compiled my own to add GPRS support to the kernel, Read every available tutorial on Openmoko GPRS, Did what ever I could, even ported android on it and in the last when couldn’t do any thing, Finally I corrupted one of our Openmoko.

But that was blessing in disguise.

To repair my openmoko, I was reading an article about how to Debug Openmoko using Debug board.

I don’t know what I click and saw a link, I Went to it,

http://www.opkg.org/package_205.html

Clicked the Nice Looking download button and in a fraction of second it got downloaded.

I copied it to my Phone and Installed it.

Added my Service provider’s APN (warid in my case).

Clicked ON and …. You know what happened next. The GPRS Modem was active, I could Browse the INTERNET and don’t ask how much I was happy.

If You want to ask more questions just leav the question in Comment…

1. Download the rootfs for Android, I recommend the one provided by koolu. Click the link below to download it.

http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2

2. Download the kernel for Android, My recommended kernel is given in the link below which is less then 2 mb, use it if you want do it without getting in to any trouble

http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin

3. Install dfu-utils from synaptic manager (recommended). and download neo tools if you like GUI (I like it).

4. Start your Neo FreeRunner in to NOR menu.

5. Start Neo-tools

• Double Click 2. Flash your Neo
• Select Kernel and rootfs
• In the Dialogue box point to your rootfs and then kernel.
• A strange looking dialogue box will appears, Just waist time reading it, Just click OK.
• If the above steps failed, Repeat it again

The Flashing will going to take some time, so be patiant.

See Detail Below

To Install TPM On kernel 2.6.30

1.    Enable the TPM from BIOS

2.    Download the kernel from kernel.org (kernel 2.6.30 in my case), Extract it, enable TPM as module not as part of kernel, means M NOT as * (Didnt worked with *, dont know why), Patches should be Applied to the Kernel, Which are given as:

• Create a file By name “01-either_dataexpect_or_valid.patch” in Kernel Source Directory and paste the following in to it.

commit cca56d7b550bac0a00d6322b225f4d0a8d3e6b88
Author: David Smith <dds@google.com>
Date:   Tue Apr 28 18:56:39 2009 +0900

Fix tpm_tis driver to support either DATA_EXPECT or VALID status when uploading command data.

The TCG spec says that a VALID status implies that a DATA_EXPECT
status. This occurs in the real world with the iTPM in Intel’s Mobile 4
platform which never sets DATA_EXPECT, but sets VALID when expecting more
data.

Signed-off-by: David Smith <dds@google.com>

diff –git a/drivers/char/tpm/tpm_tis.c b/drivers/char/tpm/tpm_tis.c
index aec1931..be112ef 100644
— a/drivers/char/tpm/tpm_tis.c
+++ b/drivers/char/tpm/tpm_tis.c
@@ -293,7 +293,8 @@ static int tpm_tis_send(struct tpm_chip *chip, u8 *buf, size_t len)
wait_for_stat(chip, TPM_STS_VALID, chip->vendor.timeout_c,
&chip->vendor.int_queue);
status = tpm_tis_status(chip);
-        if ((status & TPM_STS_DATA_EXPECT) == 0) {
+        if ((status & TPM_STS_DATA_EXPECT) == 0 &&
+                    (status & TPM_STS_VALID) == 0) {
rc = -EIO;
goto out_err;
}
@@ -306,7 +307,8 @@ static int tpm_tis_send(struct tpm_chip *chip, u8 *buf, size_t len)
wait_for_stat(chip, TPM_STS_VALID, chip->vendor.timeout_c,
&chip->vendor.int_queue);
status = tpm_tis_status(chip);
-    if ((status & TPM_STS_DATA_EXPECT) != 0) {
+    if ((status & TPM_STS_DATA_EXPECT) != 0 &&
+            (status & TPM_STS_VALID) == 1) {
rc = -EIO;
goto out_err;
}

• Create a file By name “02-fix_acpipnp.patch” in Kernel Source Directory and paste the following in to it.

commit 7a553b4e7439ad0733da7da8663d32aa4865aa9e
Author: David Smith <dds@google.com>
Date:   Tue Apr 28 18:52:02 2009 +0900

Update ACPI PNP to support devices with EISA PNP CIDs but non-PNP HIDs
Signed-off-by: David Smith <dds@google.com>

diff –git a/drivers/pnp/pnpacpi/core.c b/drivers/pnp/pnpacpi/core.c
index 9496494..8bfddfb 100644
— a/drivers/pnp/pnpacpi/core.c
+++ b/drivers/pnp/pnpacpi/core.c
@@ -159,8 +159,8 @@ static int __init pnpacpi_add_device(struct acpi_device *device)
* driver should not be loaded.
*/
status = acpi_get_handle(device->handle, “_CRS”, &temp);

]]> http://waqarafridi.wordpress.com/2009/10/16/how-to-install-tpm-linux-kernel-2-6-30/feed/ 2 waqarafridi http://waqarafridi.wordpress.com/2009/10/15/iphone-security-analysis/ http://waqarafridi.wordpress.com/2009/10/15/iphone-security-analysis/#comments Thu, 15 Oct 2009 10:43:45 +0000 waqarafridi http://waqarafridi.wordpress.com/?p=44 ]]> It is presentation of the Paper written by Charlie Miller, Jake Honoroff, Joshua Maason at Indepandent Security Evaluators (ISE). This paper is about find vulnerability in Apple iPhone and a few suggestion how to fix them.

1. Summary of Apples iPhone

• Released by Apple Inc. on June 29, 2007
• Runs a customised version of MAC OS X
• Run on ARM 1176JZF-S Processor
• Has the Features like multi touch, accelerometer etc etc.
• Support QUAD-Band GSM and supports AT&T EDGE network.
• Apple walay says ”People Like our phone”

2. iPhone as Close Phone

• iPhone Only works only on AT&T networks means no Warid and Jazz (I think).
• You can not install Third Party Applications.
• You are not access File System, you can access small portion in a ”SandBox”. That is mainly for adding  and removing Songs waghaira.
• Thats SandBoxed area can only be accessed by iTunes provided by Apple inc.

3. Weakness in iPhone

• Apple has mainly tried to Avoid attacks (by Making it close)
• Never tried to handle it.
• The Only user is root (The Power User)
• Attacks (will be discussed later) avoided through restricting user to access a portion of file system.
• No Address Randomization and Non – Executable Heap.

4. Attacks

4.1 Jail Breaking

• The process of gaining root access to filesystem to install 3rd party tools.
• The Access to File System is RW.
• Mainly The Owner of the Phone do the Attack
• Using jail breaking Leeds to Unlocking.
• Jailbreaking tool is avilble for download (If you have iPhone).

4.2 Unlocking

• Unlocking means to use service of any service provider other then ATT&T.
• The Following tools are available
  AnySIM ————– (Free of Cost)
  TurboSim———— (Paid)
  SimFree ————– (Paid)
• anySim use a patch to bypass the AT&T check.
• TurboSim hasn’t yet reveled their secret.
• SimFree tells the iPhone that current sim is of AT&T

4.3 Buffer overflow

• We can find vulnerability and use buffer overflow attack, due to my kindness I gave an Example.
• Suppose we a password function
  Void func(chat *passedStr)
  {
  Char localStr[4];
  strcpy(localStr, passedStr);
  }
• In above Function there is no check on Password length
• Lets suppose password should be four characters (abcd)
• If an attackers provide the password ”abcd\x12\x23\x56\x78”
• The value would be \x87654321 (little endian)
• The over write value \x87654321 will execute a function system() and passing desired values.

4.4 Other Attacks

• The Other attacks are return-to-libc and reverse engineering. (Need to study them)
• By Visiting a malicious website due the fact that mobile Safari (iPhone Browser) is not a full fledged browser.
• By Crashing the iPhone and studying the log.

1. Trusted Linux Client:

• The Main Goals are:
  • To Protect Desktop and Mobile Linux Clients from on-line and off-line attacks
  • Transparent to the user

• Major Components
  • Trusted Boot
  • Grub
  • TPM

• Integrity Measurement
  • EVM (Going to concentrate More on this)

• Integrity Protection
  • SLIM

• Integrity Attestation
  • Integrity Measurement Architecture

• Security Domains
  • PUID – Persistent User ID
  • Unionfs – stacked, copy-on-write, sandbox (Stony Brook)
  • Per-process filesystem namespaces

2. Extended Verification Module

• Purpose
  • Used to to verify all the files
  • Including executables and non-executables
  • Weither they are authentic and un-modified, current, and not known to malicious.
  • Trust Finding

• Working
  • Use extended file attributes to store authenticated file metadata
    • File data hash
    • Mandatory access control labels
    • Metadata integrity Key Hashed Message Authentication Control (HMAC)
  • Use tpm based symmetric kernel key to HMAC these attributes
  • Verify file once at open/execute, and cache verification (Adv over Previous Method)
  • “heavy lifting” done at install time, runtime is just file hash and HMAC
  • Extensible, policy based definition of attributes and actions (Point not clear to me, Use Which policy)

• EVM Extended Attributes
  • security.evm.hash ——————– hash of file data (from signed rpm)
  • security.evm.hmac ——————- hmac­sha1 of security.* attributes
  • security.evm.packager ————– signer of package
  • security.evm.version —————- version of package

• Operation
  • Executable is Installed
  • It is verified using all verification methods listed in the EVM Policy file.
  • Result + Hash + HMAC is stored in Extended Attributes
  • At Run time, kernel Compares verification attributes to current Policy.
  • Action taken Accordingly

• EVM for Non-Executables
  • The verification Headers are stored in file system not in ELF (like in case of DigSig)
  • So it can be used for any type of file
  • Executables are checked at run time while files are checked at open time
  • Rules for file can be restrict its mode (R,W)

• Advantage over previous Methods
  • DigSig stores verification headers in ELF (Extensible Linking format) which restrict it to Executables only, EVM uses File System Extended Attributes, make it suitable for all kind of Files.
  • Disadvantage of Public key signature verification has been removed through caching

• Known Issues
  • Extended attributes are not available on all File Systems
  • Problem occured due to pre-link (I honestly dont know What it is, I think its a tool that modifies the executable for faster performance, hence the hash changes)

3. Slim:

• For Integrity Protection
• Build Upon Caernarvon and Lomac models
• Gives trusted file authority to files verified by EVM
• All files are labeled with system.level

4. Runtime Output

• Attributes of “/bin/ping”:

[root@localhost safford]# getfattr ­d ­m “^security” /bin/ping
security.evm.hash=”\\1\265Ad6a4d94fb694cffd2847acf40dbc6485″
security.evm.hmac=0s8ZT9309FkQBag7HkqqieSeuya3s=
security.evm.packager=”\\1\265ARed Hat,  Inc. <http://bugzilla.redhat.com/bugzilla>”
security.evm.version=”\\1\265A20020927(rel16)”
security.selinux=”system_u:object_r:bin_t00″
security.slim.level=”SYSTEM”
evm_calc_hmac: ping ­ security.evm.hash included
evm_verify_xattr: verification of security.evm.hmac succeeded
evm_inode_permission: ‘ping’ HMAC verification succeeeded
evm_inode_permission: ‘ping’ HMAC verify xattr
evm_inode_permission: security.evm.hash is d6a4d94fb694cffd2847acf40dbc6485
evm_inode_permission: security.evm.hash succeeded
evm_analyze_cacheinfo success

]]> http://waqarafridi.wordpress.com/2009/10/15/extended-verification-module-evm/feed/ 0 waqarafridi http://waqarafridi.wordpress.com/2009/10/15/porting-ima-plus-selinux-on-openmoko/ http://waqarafridi.wordpress.com/2009/10/15/porting-ima-plus-selinux-on-openmoko/#comments Thu, 15 Oct 2009 07:26:29 +0000 waqarafridi http://waqarafridi.wordpress.com/?p=27 ]]> Below are the Steps that we preformed to port IMA plus SELinux on Openmoko. The main idea was to extract patches from the kernel 2.6.30 provided by Mimi Zohar.

See the Details Below.

1. Porting SELinux:

• We used kernel 2.6.29-rc3 because it is the latest being used by the OM kernel community and good support can be taken.
• We cross-compiled it for ARM architecture.
• To enable SELinux, the following modules were enabled in kernel
  • In Security menu we enabled [*] NSA SELinux Support
    [*]    NSA SELinux boot parameter
    (1)    NSA SELinux boot parameter default value
    [*]    NSA SELinux runtime disable
    [*]    NSA SELinux Development Support
    [*]    NSA SELinux AVC Statistics
    (1)    NSA SELinux checkreqprot default value
    [ ]    NSA SELinux maximum supported policy format version
  • Maximum policy support was not enabled because it hangs the system.
  • In file system we enabled <M> Second extended fs support
    Ext2 extended attributes
    Ext2 Security Labels
    Ext2 execute in place support<*> Ext3 journalling file system support
    Ext3 extended attributes
    Ext3 Security Labels

• The kernel was cross compiled using openmoko toolchain.$make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-

2. Porting IMA:

• To Add IMA support, IMA Patches were added to the kernel.
• These patches were extracted from kernel 2.6.30 which were provided by Mimi Zohar.
• Patches where extracted using git.
• The Command is#git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6 #git checkout -b v2.6.30_local v2.6.30
  #git log –since ”Feb 4” –grep ”Mimi Zohar” — reverse -p > ../ima.patch
• Now we get OM kernel#git clone git://git.openmoko.org/git/kernel.git linux-om-2.6#git-checkout -b andy-tracking origin/andy-tracking
• Patches were applied by using command#patch -p1 <../ima.patch
• We had namei.c Problem, which we solved, but i forgot how we did, Didnt documented it that time, If remember then I will post it here.
• After apply patches successfully we disabled selinux and enabled IMA for testing purpose.
• The kernel was cross compiled and was tested on openmoko.
• After checking that IMA is working fine, we also enabled selinux and was tested again.

3. Problems that we faced:

• First selected kernel 2.6.29-rc3 and patched it with 2.6.26-rc8 patch for LIM/IMA. The patches didnt applied automatically so we applied them manually.
• While compiling, the manual patches conflicted with original code and reported errors.
• Then we extracted LIM/IMA patch from 2.6.30 and applied to the same kernel.
• This time it worked.
• ”depends on ACPI” in Kconfig file in /security/integrity/ima was removed which is for x86 architecture (we are working on arm)and after its removal IMA appeared in the security list.

Below is a rough detail the we (me and shahbaz) did to port SELinux on Openmoko (on Neo Freerunner).

1. Obtaining source code

We decided to cross compile the code provided by Willis Vandevanter available at Google Summer of Code.

2. To Enable Auditing:

• The Device was storing all the messages in buffer. This was corrected by modify the file /etc/syslog.conf. In the entry buffer was replaced with file. And hence the problem was solved.

3. Compiling Libraries:

• We downloaded the tool chain for openmoko and was setup accordingly. to cross-compile we setuped the environment by running the script provided by tool-chain#/usr/local/openmoko/arm/setup-env
• The path was exported to to make available the tools provided by tool-chain.#export PATH=$PATHusr/local/openmoko/arm/bin/
• The following two well known commands were used used to compile#./configure
  #make
• libselinux: libselinux was CROSS COMPILED. The problems were with paths. The paths were specified in CFLAGS portion in Makefile by specifying the paths. The Makefile also contain some switches like def, and –z which produced errors, they were removed to solve the errors. The output files libselinux.a, libselinux.so and libselinux.so.1 were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm-angstrom-linux- gnueabi/usr/include.
• libsepol: It got the same problems as libselinux. The output files were libsepol.a, libsepol.so and libsepol.so.1 which were copied to /usr/local/openmoko/arm/arm-angstrom-linux- gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm- angstrom-linux-gnueabi/usr/include.
• libsemanage:It also got the same problems as above libraries. The output files were libsemanage.a, libsemanage.so and libsemanage.so.1 which were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/include.
• Busybox: The commands that were used are:$make menuconfig ARCH=armThen go to Selinux Utilities and enable all enteries. This was done to add additional Applets to busybox to handle SELinux.Busybox provides the following applets for selinux:

  Chcon
  getenforce
  Getsebool
  load_policy
  Matchpathcon
  restorecon
  Runcon
  selinuxenabled
  Setenforce
  setfiles
  Setsebool
  sestatus
  

  The output file was busybox. This file was then copied to /usr/bin folder of openmoko.

3. Compiling the Kernel:

• The Kernel was also CROSS COMPILED for the ARM Architecture. The Command is: $make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-
• To add support for EXT2 for using SELinux and Xttented attributes support was added to the Kernel by using the following command.$make menuconfig ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-
• Then in File System menu, the following were enabled.<M> Second extended fs support
  Ext2 extended attributes
  Ext2 Security Labels
  Ext2 execute in place support

  <*>Ext3 journalling file system support
  Ext3 extended attributes
  Ext3 Security Labels
  

• Then the Kernel was compiled using the above command. The result was a file called uImage.bin which was copied to the first partition of the SD Card.

4. Flashing Neo Free Runner:

• The Root FS was flashed using the utility called dfu-util. The ROOT FS was flashed using following steps:1. The Neo Free Runner was booted in NOR (AUX+PWR) until the boot menu arrive.
  2. The device was connected to PC via USB cable.
  3. To check whether dfu-util sees your device, run the command:

  $dfu-util –l

• If you get error messages from the dfu-util command then try again. Often it works on the second try.
  The usage of dfu-util is as following:

  $dfu-util -a <altsetting> -R -D <file_name>

  Where:

  -a:  altsetting: Specify the altsetting of the DFU interface by name or by number
  -R:  Issue USB Reset signalling once we’re finished
  -D:  filename: Write firmware from file_name into device

• Flashing the Kernel:Kernel can be flashed by using simple copy paste command as shown above or it can be done using dfu-util. The command format is: $dfu-util -a kernel -R -D /path/to/uImageWhen flashing succeeds the following will be shown:status(0) = No error condition is present
  Done!
• Flashing the Root Filesystem:The Root FS can be downloaded from its website (Given Below).If the file you downloaded is zipped or compressed (has a .gz, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first. And you can do simple copy paste into SD Card second partition. If the root filesystem is in image in jffs2 format, then you can flash it using the command given below $dfu-util -a rootfs -R -D rootfs_filename.jffs2The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing. When flashing succeeds the following will be shown:status(0) = No error condition is present
  Done!
• Alternative Way: An alternative and easy way to flash Neo Free Runner is by using a graphic utility called NEO TOOLS. Its self explainer in use.

5. Copying Compiled Libraries and other files to Device:

• The compiled libraries and include folder that were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr and include in previous step, were copied /usr/lib/ and /usr/include/ folder of the device. The files from /selinux-openmoko-read-only/bin were copied to /usr/bin folder of device.Missing files such as setfiles, sestatus and load_policy were provided as soft links from busybox by using the following command:
  
  $ln –s busybox setiles
  $ln –s busybox setstatus
  $ln –s busybox load_policy

6. Adding SELinux FS:

• To SELinux FS fstab file in /etc/ folder on device and the following lines were added to it.none /selinux      selinuxfs     noauto 0    0After that the folder /selinux was created using the following command.$mkdir /selinuxAnd then mounted using following command$mount /selinuxAfter that /selinux-openmoko-read-only/targeted/ folder along with its config file was copied to the /etc/selinux folder of device.
• Reloading and Building the Policy:To build and load the policy the following commands were used in /etc/selinux/targeted folder.To install the Policy:
  #make install

  To Relabel the File System:
  #make relabel

  To Load The Policy:
  #make load

  To Check whether selinux is running use the following command:
  #sestatus

  Also check the var/log/messages file for selinux entries.

7. Trouble Shooting:

• Auditing: When you don’t get messages file in /var/log/, this means they are saved in buffer, to fix this error, Go to /etc/syslog.conf and edit it, change the entry of buffer to file.
• Missing Core Files:When you flush new kernel, the first problem you get is missing core utilities like make, m4 etc. You can download the files from the website (site No. 9).Another way to do is download them directly to your device using opkg. Opkg will download, install and configure your package automatically. The Command to do this is:#opkg install make
  #opkg install m4
  

  For the above process you will need to set Internet on your device through USB Networking, refer to site link No.11 for USB Networking.
  Another easy way to do this is by using wifi, setting wifi is easy and self explainer.

• No selinuxfs: When this problem, it means that you haven’t added selinux support to your kernel, add selinux support to your kernel and then recompile it, for detail see section 3 for detail.
• Mls and other files missing: When you get this error, it means you haven’t mounted your /selinux filesystem.
• Setfiles, load_policy files missing:These files are provided by busybox, to set these files make soft links to set them. The following command shows how to do it#ln -s busybox setfiles
  #ln -s busybox load_policy

  For more information, see section 5.

• Busybox complains about missing applets such as setfiles: This means that you haven’t added selinux support to your busybox. See section 2 for detail.
• Clock skew: This means that the time of device is different then that of files, to fix this error, correct the date and time on your device.
• Policy not loading:
  

  This problem will occur when you try to load policy from ssh. Try loading policy directly from device.

• tmp/load error:This means that load_policy doesn’t take a policy file argument anymore (it always loads policy from the standard location and selects the appropriate version). So just modify your Makefile to omit the policy file or run load_policy by hand with no arguments. If your try this from ssh, your terminal will hang up. Try it directly on your device.

8. List of Websites for Openmoko:

Sites containing ROOTFS and Kernels:

http://downloads.openmoko.org/distro/releases/Om2008.12/
http://downloads.freesmartphone.org/fso-stable/milestone5.1/om-gta02/
http://build.shr-project.org/shr-testing/images/om-gta02/
http://wiki.openmoko.org/wiki/Download
http://downloads.openmoko.org/distro/obsoleteimages/Om2008.8/Om2008.8.rootfs.tar.gz
http://downloads.openmoko.org/distro/obsolete-images/Om2008.9/Om2008.9.rootfs.tar.gz
http://compartida.net/openmoko/FDOM/

Site containing utilities for Openmoko:

http://wiki.openmoko.org/wiki/MokoMakefile
http://downloads.openmoko.org/repository/Om2008.8/armv4t/

Openmoko Wiki:

http://wiki.openmoko.org/wiki/Neo_FreeRunner
http://wiki.openmoko.org/wiki/USB_Networking