UbuntuPhone - User contributions [en]

Debian Chroot

2017-11-22T20:34:55Z

Chris: /* 2) Using phone only */

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL. There is also [http://askubuntu.com/a/678031 a updated version on Ask Ubuntu], see also [https://askubuntu.com/questions/620740/recommended-way-to-install-regularcli-deb-packages-on-ubuntu-phone/623311 this thread on Ask Ubuntu].

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "<code>ls -l</code>" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

Or for stretch:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap debian-archive-keyring
mkdir /home/phablet/debian
cd /home/phablet
sudo debootstrap --arch=armhf stretch ./debian https://mirrorservice.org/sites/ftp.debian.org/debian
</syntaxhighlight>

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option <code>--foreign</code> to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the <code>--foreign</code> flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of <code>/dev/zero</code> and not <code>/dev/random</code> or <code>/dev/urandom</code> as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "<code>pwd</code>" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Debian Chroot

2017-11-22T19:56:02Z

Chris: /* 2) Using phone only */

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL. There is also [http://askubuntu.com/a/678031 a updated version on Ask Ubuntu], see also [https://askubuntu.com/questions/620740/recommended-way-to-install-regularcli-deb-packages-on-ubuntu-phone/623311 this thread on Ask Ubuntu].

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "<code>ls -l</code>" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

Or for stretch:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap debian-archive-keyring
mkdir /home/phablet/debian
cd /home/phablet
sudo debootstrap --arch=armhf stretch ./debian http://http.debian.net/debian
</syntaxhighlight>

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option <code>--foreign</code> to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the <code>--foreign</code> flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of <code>/dev/zero</code> and not <code>/dev/random</code> or <code>/dev/urandom</code> as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "<code>pwd</code>" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Resize Root

2016-06-01T22:10:00Z

Chris: Created page with "See this script: https://github.com/plasma-mobile/plasma-phone-dev-setup/blob/master/usr/bin/resize-root-partition"

See this script: https://github.com/plasma-mobile/plasma-phone-dev-setup/blob/master/usr/bin/resize-root-partition

Main Page

2016-06-01T22:09:27Z

Chris:

This wiki has been created to document things you can do on the command line on an Ubuntu Phone.

See also the [https://www.gitbook.com/book/gurucubano/bq-aquaris-e-4-5-ubuntu-phone/details BQ Aquaris E 4.5 Ubuntu phone book] on gitbooks.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel
# [[Debian Chroot]] — install a Debian system on an Ubuntu Phone
# [[Firewall]] — install and configure a firewall using iptables
# [[Resize Root]] — of course this isn't recommended!

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Debian Chroot

2016-05-18T07:45:05Z

Chris:

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL. There is also [http://askubuntu.com/a/678031 a updated version on Ask Ubuntu], see also [https://askubuntu.com/questions/620740/recommended-way-to-install-regularcli-deb-packages-on-ubuntu-phone/623311 this thread on Ask Ubuntu].

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "<code>ls -l</code>" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option <code>--foreign</code> to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the <code>--foreign</code> flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of <code>/dev/zero</code> and not <code>/dev/random</code> or <code>/dev/urandom</code> as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "<code>pwd</code>" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Main Page

2016-05-16T20:45:21Z

Chris:

This wiki has been created to document things you can do on the command line on an Ubuntu Phone.

See also the [https://www.gitbook.com/book/gurucubano/bq-aquaris-e-4-5-ubuntu-phone/details BQ Aquaris E 4.5 Ubuntu phone book] on gitbooks.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel
# [[Debian Chroot]] — install a Debian system on an Ubuntu Phone
# [[Firewall]] — install and configure a firewall using iptables

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Proxy Web Traffic

2015-10-16T21:29:58Z

Chris:

There is an [https://bugs.launchpad.net/canonical-devices-system-image/+bug/1497210 assigned bug] to sort out blocking webbugs and trackers, in the meantime there is Privoxy...

== Privoxy ==

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "/bin/bash $0 server-name-from-ssh-config-file"
exit
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>):

<syntaxhighlight lang="bash">
bash ~/bin/proxy your-ssh-server
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

<pre>
keep-alive-timeout 300
</pre>

Debian Chroot

2015-09-25T11:29:35Z

Chris: Added link to http://askubuntu.com/a/678031

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL. There is also [http://askubuntu.com/a/678031 a updated version on Ask Ubuntu].

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "<code>ls -l</code>" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option <code>--foreign</code> to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the <code>--foreign</code> flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of <code>/dev/zero</code> and not <code>/dev/random</code> or <code>/dev/urandom</code> as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "<code>pwd</code>" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Firewall

2015-09-18T10:48:45Z

Chris:

See [[Install Packages]] for notes on how to install <code>iptables-persistent</code>.

If you only want to accept <code>ssh</code> and pings edit <code>/etc/iptables/rules.v4</code>:

<pre>
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -d 127.0.0.0/8 ! -i lo -j REJECT --reject-with icmp-port-unreachable
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7
-A INPUT -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -j ACCEPT
COMMIT
</pre>

And reload the rules:

<syntaxhighlight lang="bash">
sudo iptables-restore < /etc/iptables/rules.v4
</syntaxhighlight>

== Disable IPv6 ==

If you are not using IPv6 you can disable it by first setting the root files system to be read-write and then running:

<syntaxhighlight lang="bash">
echo "net.ipv6.conf.all.disable_ipv6 = 1" >> /etc/sysctl.conf
echo "net.ipv6.conf.default.disable_ipv6 = 1" >> /etc/sysctl.conf
echo "net.ipv6.conf.lo.disable_ipv6 = 1" >> /etc/sysctl.conf
</syntaxhighlight>

And after the device has been rebooted it will only support IPv4.

Firewall

2015-09-18T10:48:22Z

Chris: Page created

See [[Install Packages]] for notes on how to install <code>iptables-persistent</code>.

If you only want to accept <code>ssh</code> and pings edit <code>/etc/iptables/rules.v4</code>:

<code>
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -d 127.0.0.0/8 ! -i lo -j REJECT --reject-with icmp-port-unreachable
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7
-A INPUT -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -j ACCEPT
COMMIT
</code>

And reload the rules:

<syntaxhighlight lang="bash">
sudo iptables-restore < /etc/iptables/rules.v4
</syntaxhighlight>

== Disable IPv6 ==

If you are not using IPv6 you can disable it by first setting the root files system to be read-write and then running:

<syntaxhighlight lang="bash">
echo "net.ipv6.conf.all.disable_ipv6 = 1" >> /etc/sysctl.conf
echo "net.ipv6.conf.default.disable_ipv6 = 1" >> /etc/sysctl.conf
echo "net.ipv6.conf.lo.disable_ipv6 = 1" >> /etc/sysctl.conf
</syntaxhighlight>

And after the device has been rebooted it will only support IPv4.

Main Page

2015-09-18T10:40:17Z

Chris:

This wiki has been created to document things you can do on the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel
# [[Debian Chroot]] — install a Debian system on an Ubuntu Phone
# [[Firewall]] — install and configure a firewall using iptables

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Main Page

2015-09-18T10:05:54Z

Chris:

This wiki has been created to document things you can do on the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel
# [[Debian Chroot]] — install a Debian system on an Ubuntu Phone

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Encrypted Home

2015-09-18T09:57:19Z

Chris: Added ramdon ~/tmp/ script

Create an encrypted <code>/home/user/</code> directory, this needs some additional packages to be installed, see [[Install Packages]], set the wanted username as an environmental variable first:

<syntaxhighlight lang="bash">
sudo -i
export NEWUSER="username"
</syntaxhighlight>

Create a file to use as a disk (set the size as required, it is 1G in this example) and encrypt
and format it:

<syntaxhighlight lang="bash">
fallocate -l 1G /home/$NEWUSER.img
cryptsetup luksFormat /home/$NEWUSER.img
cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER
mkfs.ext4 /dev/mapper/$NEWUSER
mkdir /home/$NEWUSER
mount /dev/mapper/$NEWUSER /home/$NEWUSER
</syntaxhighlight>

Add the new user and add them to the sudo group:

<syntaxhighlight lang="bash">
adduser --disabled-password $NEWUSER
addgroup $NEWUSER
adduser $NEWUSER $NEWUSER
usermod -a -G sudo $NEWUSER
</syntaxhighlight>

After doing the above you can su to the new user:

<syntaxhighlight lang="bash">
su - $NEWUSER
</syntaxhighlight>

And you now have a user account with an encrypted filesystem.

You can add the following to /home/phablet/.bash_aliases for mounting
the disk in future (change $NEWUSER to your username first!):

<syntaxhighlight lang="bash">
alias mnt-$NEWUSER='sudo cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER; sudo e2fsck /dev/mapper/$NEWUSER ; sudo mount /dev/mapper/$NEWUSER /home/$NEWUSER'
</syntaxhighlight>

== Random encrypted ~/tmp/ ==

If you would like a <code>~/tmp/</code> directory which is randomly encrypted and therefore impossible to decrypt after the device has been power cycled then you can create <code>/home/phablet/bin/mktmpfs</code> as follows:

<syntaxhighlight lang="bash">

#!/bin/bash

if [[ $1 ]]; then
USER=$1
else
echo "Please supply a username for the temp partition"
exit
fi

umount /home/$USER/tmp
cryptsetup luksClose $USER-tmp

RANDOM_FILE=/tmp/$(pwgen -n 12)
touch $RANDOM_FILE
chmod 600 $RANDOM_FILE
echo $(pwgen -n 128) > $RANDOM_FILE

dd if=/dev/urandom of=/home/$USER.tmp.img iflag=fullblock bs=1M count=6
#fallocate -l 10M /home/$USER.tmp.img
chmod 700 /home/$USER.tmp.img
cryptsetup luksFormat /home/$USER.tmp.img $RANDOM_FILE
cryptsetup luksOpen /home/$USER.tmp.img $USER-tmp --key-file $RANDOM_FILE
mkfs.ext2 /dev/mapper/$USER-tmp
mount /dev/mapper/$USER-tmp /home/$USER/tmp
chmod 700 /home/$USER/tmp
chown -R $USER:$USER /home/$USER/tmp
shred $RANDOM_FILE
</syntaxhighlight>

And then run it as the <code>phablet</code> user:

<syntaxhighlight lang="bash">
sudo bash ~/bin/mktmpfs USER
</syntaxhighlight>

Encrypted Home

2015-08-28T13:17:22Z

Chris:

Debian Chroot

2015-08-28T13:11:07Z

Chris: formatting...

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL:

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "<code>ls -l</code>" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option <code>--foreign</code> to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the <code>--foreign</code> flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of <code>/dev/zero</code> and not <code>/dev/random</code> or <code>/dev/urandom</code> as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "<code>pwd</code>" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Debian Chroot

2015-08-28T13:07:57Z

Chris: formatting...

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL:

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

# Comments on file systems and permissions
# Using phone only
# Using computer and phone (recommended)
# Unsing an image file (recommended)

== 1) Comments on file systems and permissions ==

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "ls -l" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

== 2) Using phone only ==

'''(not recommended since it breaks over the air updates)'''

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

== 3) Using computer and phone ==

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option --foreign to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the --foreign flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

== 4) Using an image file ==

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of /dev/zero and not /dev/random or /dev/urandom as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

<syntaxhighlight lang="bash">
sudo losetup -d LOOP
</syntaxhighlight>

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "pwd" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Debian Chroot

2015-08-28T13:05:28Z

Chris:

The following was written by Torsten Sachse and [https://lists.launchpad.net/ubuntu-phone/msg13344.html posted to the Ubuntu Phone email list on 16 Jun 2015] and reproduction was permitted under the terms of the GPL:

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

1. Comments on file systems and permissions
2. Using phone only
3. Using computer and phone (recommended)
4. Unsing an image file (recommended)

1) Comments on file systems and permissions

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "ls -l" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

2) Using phone only (not recommended since it breaks over the air updates)

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

3) Using computer and phone

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option --foreign to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the --foreign flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

4) Using an image file

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of /dev/zero and not /dev/random or /dev/urandom as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

sudo losetup -d LOOP

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "pwd" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Debian Chroot

2015-08-28T13:03:53Z

Chris: Copied from https://lists.launchpad.net/ubuntu-phone/msg13344.html

The following was written by Torsten Sachse and posted to the [https://lists.launchpad.net/ubuntu-phone/msg13344.html Ubuntu Phone email list on 16 Jun 2015] and reproduction was allowed on the terms of the GPL:

== Debian Chroot ==

This is a simple guide describing how to set up a chroot on a Ubuntu touch device. It also explains how to set it up so that the chroot is located on the SD-card to save internal storage space and goes into some detail about why simply installing the chroot on an SD-card is not possible.

The guide is structured as follows:

1. Comments on file systems and permissions
2. Using phone only
3. Using computer and phone (recommended)
4. Unsing an image file (recommended)

1) Comments on file systems and permissions

Only some file system types support file permissions in a way the chroot needs them. An SD-card likely uses FAT32 which does not support any type of permissions and, hence, the chroot can't run on it. The permissions reported by commands like "ls -l" do not have any significance on such file systems. Some Android handsets for instance support EXT3 or ECT4 on their SD-cards making installing a chroot a lot easier.

2) Using phone only (not recommended since it breaks over the air updates)

It is possible to install debootstrap on the phone by remounting the system as read-write and executing the following commands. At least it worked on my BQ on r22. Imagine you want to install your chroot into the directory "jessie" which should reside in the current working directory:

<syntaxhighlight lang="bash">
sudo mount / -o remount,rw
sudo apt-get update
sudo apt-get install debootstrap
sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

This only works on the internal storage without what's explained in section 4).

3) Using computer and phone

The problem with this debootstrap-command failing your average computer is that your computer cannot execute binaries compiled for the ARM architechture. This is why you have to add the option --foreign to debootstrap which tells it to only download all packages and leave anything that needs executing of any of the installed binaries to another system. So do (sudo might not be needed):

<syntaxhighlight lang="bash">
sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
</syntaxhighlight>

If you were to install an i386 architechture on a x86_64 system, you would not have to specify the --foreign flag as both should be able to run on an ordinary 64-bit processor although they're different architechrures.

Now best create a tar archive from this which you then copy to your phone. It does not matter whether the archive is put on the SD-card or the internal storage. The second command is needed to turn on ssh support, which is reset upon every reboot.

<syntaxhighlight lang="bash">
tar -cvzf jessie.tar.gz jessie
sudo service ssh start
scp jessie.tar.gz phablet@ubuntu-phablet:DIRECTORY_OF_YOUR_CHOICE
</syntaxhighlight>

Now you only have to extract the archive wherever you want the new directory "jessie" to reside. Without what's expained in section 4), this will only work on your internal storage. Then, you only have to go into your chroot and finish the installation process. So do on the phone (the first command is needed since the terminal app is somehow restricted to execute binaries):

<syntaxhighlight lang="bash">
ssh localhost
tar -xvzf jessie.tar.gz
sudo chroot jessie /bin/bash
/debootstrap/debootstrap --second-stage
exit
</syntaxhighlight>

Now, you should be able to chroot into your new system using the third of the above commands.

4) Using an image file

First, create an image file on the system on which you execute the first debootstrap command. To create an 1GB image, do

<syntaxhighlight lang="bash">
dd if=/dev/zero of=IMAGE.img bs=1G count=1
</syntaxhighlight>

Note that the B in GB is left out. "if" stands for "input file", "of" for "output file" and "bs" for "block size". There are more efficient commands out there, but those only work on certain types of file systems, AFAIK. This one also works on an SD-card or a tempfs. Please note the use of /dev/zero and not /dev/random or /dev/urandom as that would take a lot longer and make it take a lot longer to transfer the image between devices.

Mount the image file to a loop-device and create a file system on it. Without a file system, you cannot yet mount the image to a directory, only to a block-device. So do

<syntaxhighlight lang="bash">
sudo losetup -f
</syntaxhighlight>

and remember the output. Replace every "LOOP" in the following commands by the output of the above command. First, assign the image to a block device:

<syntaxhighlight lang="bash">
sudo losetup LOOP IMAGE.img
</syntaxhighlight>

Next, create the file system on it:

<syntaxhighlight lang="bash">
sudo mkfs -t ext4 LOOP
</syntaxhighlight>

Next, detach the image from the loop device:

sudo losetup -d LOOP

If you get command not found errors, just install the missing programmes. Now, create the directory and mount the image file to it:

<syntaxhighlight lang="bash">
mkdir jessie
sudo mount -o loop IMAGE.img $(pwd)/jessie
</syntaxhighlight>

The command "pwd" will make sure you give mount an absolute path to your current working directory. Now, use the directory "jessie" with debootstrap as explained above (the command including the --foreign flag). After you're finished, umount the image via

<syntaxhighlight lang="bash">
sudo umount $(pwd)/jessie
</syntaxhighlight>

and create an archive of the image file (will compress all the zeroes in the archive to almost nothing) and transfer that to your phone. Both SD-card and internal storage are fine. On your phone, create the directory "jessie" somewhere on the internal storage, mount the image to it and perform the second stage.

You should now have a nice chroot on your phone that does not waste internal storage space.

Main Page

2015-08-28T12:57:33Z

Chris:

This wiki has been created to document things you can do with the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel
# [[Debian Chroot]] — install a Debian system on an Ubuntu Phone

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Proxy Web Traffic

2015-08-27T17:25:26Z

Chris: /* SSH tunnel */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "/bin/bash $0 server-name-from-ssh-config-file"
exit
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>):

<syntaxhighlight lang="bash">
bash ~/bin/proxy your-ssh-server
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

<pre>
keep-alive-timeout 300
</pre>

Proxy Web Traffic

2015-08-27T17:25:02Z

Chris: /* SSH tunnel */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "/bin/bash $0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>):

<syntaxhighlight lang="bash">
bash ~/bin/proxy your-ssh-server
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

<pre>
keep-alive-timeout 300
</pre>

Install Packages

2015-08-27T17:18:08Z

Chris:

Open the terminal client and sudo to root and then remount the root file system read-write:

<syntaxhighlight lang="bash">
sudo -i
mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages (you can use <code>apt-cache search</code> to find packages):

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget privoxy
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Proxy Web Traffic

2015-08-27T17:17:15Z

Chris: /* Troubleshooting */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "$0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>):

<syntaxhighlight lang="bash">
bash ~/bin/proxy
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

<pre>
keep-alive-timeout 300
</pre>

Proxy Web Traffic

2015-08-27T17:16:51Z

Chris: /* SSH tunnel */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "$0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>):

<syntaxhighlight lang="bash">
bash ~/bin/proxy
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

{{{
keep-alive-timeout 300
}}}

Proxy Web Traffic

2015-08-27T17:15:10Z

Chris: /* SSH tunnel */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "$0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code> after you <code>chmod 750 ~/bin/proxy</code>:

<syntaxhighlight lang="bash">
bash ~/bin/proxy
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

{{{
keep-alive-timeout 300
}}}

Proxy Web Traffic

2015-08-27T17:13:42Z

Chris: /* SSH tunnel */

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-write and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "$0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code>:

<syntaxhighlight lang="bash">
bash ~/bin/proxy
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

{{{
keep-alive-timeout 300
}}}

Proxy Web Traffic

2015-08-27T17:12:56Z

Chris: Page created

Follow [[Install Packages]] to install <code>privoxy</code>, then start it:

<syntaxhighlight lang="bash">
apt-get install privoxy
service privoxy start
</syntaxhighlight>

Edit <code>/etc/environment</code> and add:

<syntaxhighlight lang="bash">
ftp_proxy=http://localhost:8118/
http_proxy=http://localhost:8118/
https_proxy=http://localhost:8118/
FTP_PROXY=http://localhost:8118/
HTTP_PROXY=http://localhost:8118/
HTTPS_PROXY=http://localhost:8118/
</syntaxhighlight>

Reboot the phone to change the root filesystem to read-only and to ensure that sessions have the env vars above set (you can check in a terminal with <code>printenv</code>).

Visit http://config.privoxy.org/ to test it is working.

== SSH tunnel ==

Set the root file system to be read-writ and edit <code>/etc/privoxy/config</code> adding this line with the port the ssh tunnel will be on, in this case 3128:

<pre>
forward-socks5 / 127.0.0.1:3128 .
</pre>

Add a list of local networks you don't want the tunnel to be used for (so you can use the web browser to login to public wifi networks for example):

<pre>
forward 192.168.*.*/ .
</pre>

Create a script to start a ssh tunnel, eg <code>~/bin/proxy</code> containing something like this (remove the <code>v</code> for non-verbose output in the terminal):

<syntaxhighlight lang="bash">
#!/bin/bash

if [[ $1 ]]; then
REMOTE_SERVER=$1
else
echo "Run this script like this:"
echo "$0 server-name-from-ssh-config-file"
fi

ssh -vTnN -C -F "$HOME/.ssh/config" -D 3128 $REMOTE_SERVER
</syntaxhighlight>

This works best if you have short names for servers in your <code>~/.ssh/config</code> and have ssh keys set up.

Start the tunnel (note you might need to run it as follows unless you ssh to localhost first and have <code>~/bin/</code> in your <code>$PATH</code>, then you can simply type <code>proxy</code>:

<syntaxhighlight lang="bash">
bash ~/bin/proxy
</syntaxhighlight>

Visit a page that reports your IP address, eg https://parrot.transitionnetwork.org/myip.shtml

== Troubleshooting ==

If your network is very unreliable, try adding this to <code>/etc/privoxy/config</code>:

{{{
keep-alive-timeout 300
}}}

Main Page

2015-08-27T16:44:20Z

Chris:

This wiki has been created to document things you can do with the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

# [[SSH access through Wifi]] — How to get SSH access to the Ubuntu Phone via Wifi
# [[USB networking ]] — How to get SSH access through USB networking
# [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
# [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
# [[Encrypted Home]] — add an additional account and create an encrypted home directory for it
# [[Proxy Web Traffic]] — install privoxy to filter out adverts and optionally forward web traffic to a ssh tunnel

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Install Packages

2015-05-02T15:38:40Z

Chris:

Open the terminal client and sudo to root and then remount the root file system read-write:

<syntaxhighlight lang="bash">
sudo -i
mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages (you can use <code>apt-cache search</code> to find packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Install Packages

2015-04-18T08:38:20Z

Chris:

Open the terminal client and sudo to root and then remount the root file system read-write:

<syntaxhighlight lang="bash">
$ sudo -i
# mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages (you can use <code>apt-cache search</code> to find packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Install Packages

2015-04-18T08:36:44Z

Chris:

Open the terminal client and sudo to root and then remount the root file system read-write:

<syntaxhighlight lang="bash">
$ sudo -i
# mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Category:SSH

2015-04-18T08:07:42Z

Chris: Created page with "Pages related to configuring and using the secure shell (SSH) on the Ubuntu Phone."

Pages related to configuring and using the secure shell (SSH) on the Ubuntu Phone.

Install Packages

2015-04-18T08:00:12Z

Chris:

Open the terminal client and sudo to root and then remount the root files system read-write:

<syntaxhighlight lang="bash">
$ sudo -i
# mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Find Phone

2015-04-18T07:59:22Z

Chris:

If you want to ssh into your phone and you don't know it's IP address you can use this script to find it, note that you need to set a couple of environmental variables first and also you need to supply the subnet (automating this would be an improvement):

<syntaxhighlight lang="bash">
#!/bin/bash

# This is a script to find a device on a LAN by it's Mac address

if [[ $1 ]]; then
SUBNET=$1
else
/sbin/ifconfig
echo "Please supply the subnet, eg: $0 192.168.0.0/24"
exit
fi

if [[ $PHONE_MAC ]]; then
echo Mac: $PHONE_MAC
else
echo You need to set the PHONE_MAC environmental variable to
echo the Mac address of your phone, eg add the following to
echo your ~/.bashrc:
echo
echo export PHONE_MAC="10:10:10:10:10:10"
exit
fi

if [[ $PHONE_IFACE ]]; then
echo Iface: $PHONE_IFACE
else
echo You need to set the PHONE_IFACE environmental variable to
echo the network interface the phone can be reached on, eg add
echo the following to your ~/.bashrc:
echo
echo export PHONE_IFACE="wlan0"
exit
fi

# Nmap and arp scan the network
sudo nmap -sP $SUBNET > /dev/null
PHONE_IP=$(sudo arp-scan -I $PHONE_IFACE $SUBNET | grep $PHONE_MAC | awk '{print $1}')

if [[ $PHONE_IP ]]; then
echo IP: $PHONE_IP
else
echo "Sorry the phone couldn't be found"
fi

exit
</syntaxhighlight>

[[Category:Scripts]]
[[Category:SSH]]

SSH access through Wifi

2015-04-18T07:58:49Z

Chris:

How to get SSH access to the ubuntu-phone via Wifi:

Login via terminal app, you will be user 'phablet' (the password is the unlock number).

Enable SSH service with (remains after boot):

<syntaxhighlight lang="bash">
$ android-gadget-service enable ssh
</syntaxhighlight>

Fetch your public key to the Phone from some place:

<syntaxhighlight lang="bash">
$ wget http://www.from.your.site/id_rsa.pub
$ mkdir .ssh
$ chmod 0700 .ssh
$ mv id_rsa.pub .ssh/authorized_keys
</syntaxhighlight>

Now you can look up your IP on the phone and use ssh to connect:

<syntaxhighlight lang="bash">
$ ip addr show wlan0|grep inet
</syntaxhighlight>

from your workstation use:

<syntaxhighlight lang="bash">
$ ssh phablet@IP-addr-from-above-command
</syntaxhighlight>

SSH-in is even possible when the device is locked and black; don't know
if this is intention that it does not suspend; the configuration goes like this

See also:

* [http://askubuntu.com/questions/348714/how-can-i-access-my-ubuntu-phone-over-ssh/599041#599041 http://askubuntu.com/questions/348714/how-can-i-access-my-ubuntu-phone-over-ssh/599041#599041]
* [[Find Phone]]

[[Category:SSH]]

Main Page

2015-04-17T20:44:34Z

Chris:

This wiki has been created to document things you can do with the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

* [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
* [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
* [[Encrypted Home]] — add an additional account and create an encrypted home directory for it

== Getting started ==

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

Encrypted Home

2015-04-17T20:41:48Z

Chris:

Create an encrypted /home/user/ directory, this needs some additional packages to be installed, see [[Install Packages]], set the wanted username as an environmental variable first:

<syntaxhighlight lang="bash">
sudo -i
export NEWUSER="username"
</syntaxhighlight>

Create a file to use as a disk (set the size as required, it is 1G in this example) and encrypt
and format it:

<syntaxhighlight lang="bash">
fallocate -l 1G /home/$NEWUSER.img
cryptsetup luksFormat /home/$NEWUSER.img
cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER
mkfs.ext4 /dev/mapper/$NEWUSER
mkdir /home/$NEWUSER
mount /dev/mapper/$NEWUSER /home/$NEWUSER
</syntaxhighlight>

Add the new user and add them to the sudo group:

<syntaxhighlight lang="bash">
adduser --disabled-password $NEWUSER
addgroup $NEWUSER
adduser $NEWUSER $NEWUSER
usermod -a -G sudo $NEWUSER
</syntaxhighlight>

After doing the above you can su to the new user:

<syntaxhighlight lang="bash">
su - $NEWUSER
</syntaxhighlight>

And you now have a user account with an encrypted filesystem.

You can add the following to /home/phablet/.bash_aliases for mounting
the disk in future (change $NEWUSER to your username first!):

<syntaxhighlight lang="bash">
alias mnt-$NEWUSER='sudo cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER; sudo e2fsck /dev/mapper/$NEWUSER ; sudo mount /dev/mapper/$NEWUSER /home/$NEWUSER'
</syntaxhighlight>

Encrypted Home

2015-04-17T20:41:12Z

Chris:

Create an encrypted /home/user/ directory, this needs some additional packages to be installed, see [[Install Packages]], set the wanted username as an environmental variable first:

<syntaxhighlight lang="bash">
sudo -i
export NEWUSER="username"
</syntaxhighlight>

Create a file to use as a disk (set the size as required) and encrypt
and format it:

<syntaxhighlight lang="bash">
fallocate -l 1G /home/$NEWUSER.img
cryptsetup luksFormat /home/$NEWUSER.img
cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER
mkfs.ext4 /dev/mapper/$NEWUSER
mkdir /home/$NEWUSER
mount /dev/mapper/$NEWUSER /home/$NEWUSER
</syntaxhighlight>

Add the new user and add them to the sudo group:

<syntaxhighlight lang="bash">
adduser --disabled-password $NEWUSER
addgroup $NEWUSER
adduser $NEWUSER $NEWUSER
usermod -a -G sudo $NEWUSER
</syntaxhighlight>

After doing the above you can su to the new user:

<syntaxhighlight lang="bash">
su - $NEWUSER
</syntaxhighlight>

And you now have a user account with an encrypted filesystem.

You can add the following to /home/phablet/.bash_aliases for mounting
the disk in future (change $NEWUSER to your username first!):

<syntaxhighlight lang="bash">
alias mnt-$NEWUSER='sudo cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER; sudo e2fsck /dev/mapper/$NEWUSER ; sudo mount /dev/mapper/$NEWUSER /home/$NEWUSER'
</syntaxhighlight>

Encrypted Home

2015-04-17T20:40:58Z

Chris:

Create an encrypted /home/user/ directory, this needs some additional packages to be installed, [[Install Packages]], set the wanted username as an environmental variable first:

<syntaxhighlight lang="bash">
sudo -i
export NEWUSER="username"
</syntaxhighlight>

Create a file to use as a disk (set the size as required) and encrypt
and format it:

<syntaxhighlight lang="bash">
fallocate -l 1G /home/$NEWUSER.img
cryptsetup luksFormat /home/$NEWUSER.img
cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER
mkfs.ext4 /dev/mapper/$NEWUSER
mkdir /home/$NEWUSER
mount /dev/mapper/$NEWUSER /home/$NEWUSER
</syntaxhighlight>

Add the new user and add them to the sudo group:

<syntaxhighlight lang="bash">
adduser --disabled-password $NEWUSER
addgroup $NEWUSER
adduser $NEWUSER $NEWUSER
usermod -a -G sudo $NEWUSER
</syntaxhighlight>

After doing the above you can su to the new user:

<syntaxhighlight lang="bash">
su - $NEWUSER
</syntaxhighlight>

And you now have a user account with an encrypted filesystem.

You can add the following to /home/phablet/.bash_aliases for mounting
the disk in future (change $NEWUSER to your username first!):

<syntaxhighlight lang="bash">
alias mnt-$NEWUSER='sudo cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER; sudo e2fsck /dev/mapper/$NEWUSER ; sudo mount /dev/mapper/$NEWUSER /home/$NEWUSER'
</syntaxhighlight>

Install Packages

2015-04-17T20:40:12Z

Chris:

Open the terminal client and sudo to root and then remount the root files system read-write:

<syntaxhighlight lang="bash">
sudo -i
mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Then after upgrading you can simply run:

<syntaxhighlight lang="bash">
mnt-root-rw
apt-install-essential
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>

Encrypted Home

2015-04-17T20:36:02Z

Chris: Created page with "Create an encrypted /home/user/ directory, this needs some additional packages to be installed, see above, set the wanted username as an environmental variable first: <syntax..."

Create an encrypted /home/user/ directory, this needs some additional packages to be installed, see above, set the wanted username as an environmental variable first:

<syntaxhighlight lang="bash">
sudo -i
export NEWUSER="username"
</syntaxhighlight>

Create a file to use as a disk (set the size as required) and encrypt
and format it:

<syntaxhighlight lang="bash">
fallocate -l 1G /home/$NEWUSER.img
cryptsetup luksFormat /home/$NEWUSER.img
cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER
mkfs.ext4 /dev/mapper/$NEWUSER
mkdir /home/$NEWUSER
mount /dev/mapper/$NEWUSER /home/$NEWUSER
</syntaxhighlight>

Add the new user and add them to the sudo group:

<syntaxhighlight lang="bash">
adduser --disabled-password $NEWUSER
addgroup $NEWUSER
adduser $NEWUSER $NEWUSER
usermod -a -G sudo $NEWUSER
</syntaxhighlight>

After doing the above you can su to the new user:

<syntaxhighlight lang="bash">
su - $NEWUSER
</syntaxhighlight>

And you now have a user account with an encrypted filesystem.

You can add the following to /home/phablet/.bash_aliases for mounting
the disk in future (change $NEWUSER to your username first!):

<syntaxhighlight lang="bash">
alias mnt-$NEWUSER='sudo cryptsetup luksOpen /home/$NEWUSER.img $NEWUSER; sudo e2fsck /dev/mapper/$NEWUSER ; sudo mount /dev/mapper/$NEWUSER /home/$NEWUSER'
</syntaxhighlight>

Install Packages

2015-04-17T20:33:49Z

Chris:

Install Packages

2015-04-17T20:32:23Z

Chris:

Open the terminal client and sudo to root and then remount the root files system read-write:

<syntaxhighlight lang="bash">
sudo -i
mount -o rw,remount /
</syntaxhighlight>

As root update the package list and install some additional packages:

<syntaxhighlight lang="bash">
apt-get update
apt-get install cryptsetup git vim lynx screen subversion \
iptables-persistent whois nmap arp-scan mosh \
dnsutils wget
</syntaxhighlight>

'''Note it is important not to do <code>apt-get upgrade</code> as this could break things.'''

To return the phone root file system to being read-only you probably need to reboot the phone.

After the phone system has been upgraded using the GUI you will need to repeat the steps above, so to make this easier you can put the above into a <code>~/.bash_aliases</code> file, for example:

<syntaxhighlight lang="bash">
#!/bin/bash

# Mount the root file system read-write
alias mnt-root-rw='sudo mount -o rw,remount /'

# Install some extra packages and set vim as the
# default editor (edit this list as you wish)
alias apt-install-essential='sudo apt-get update ; sudo apt-get install cryptsetup git vim lynx screen subversion iptables-persistent whois nmap arp-scan mosh dnsutils wget;
</syntaxhighlight>

Note that after creating a <code>~/.bash_aliases</code> you need to source it before the aliases will work (or open a new terminal):

<syntaxhighlight lang="bash">
source ~/.bash_aliases
</syntaxhighlight>
source

Install Packages

2015-04-17T20:31:02Z

Chris:

Install Packages

2015-04-17T20:27:23Z

Chris:

Install Packages

2015-04-17T20:22:57Z

Chris: Created page with "Open the terminal client and sudo to root and then remount the root files system read-write: <syntaxhighlight lang="bash"> sudo -i mount -o rw,remount / </syntaxhighlight>"

Open the terminal client and sudo to root and then remount the root files system read-write:

<syntaxhighlight lang="bash">
sudo -i
mount -o rw,remount /
</syntaxhighlight>

Main Page

2015-04-17T20:21:22Z

Chris: /* Content */

This wiki has been created to document things you can do with the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

* [[Install Packages]] — make the filesystem read-write and install additional <code>.deb</code> packages
* [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
* [[Encrypted Home]] — add an additional account and create an encrypted home directory for it

== Getting started ==
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

Main Page

2015-04-17T20:20:58Z

Chris:

This wiki has been created to document things you can do with the command line on an Ubuntu Phone.

People with accounts with administrator permissions can [https://ubuntu-phone.host1.webarch.net/w/index.php?title=Special:UserLogin/signup create accounts for other people].

== Content ==

* [[Install Packages]] — make the filesystem read-write and install additional `.deb` packages
* [[Find Phone]] — this is a script to find your phone on the local network by it's Mac address
* [[Encrypted Home]] — add an additional account and create an encrypted home directory for it

== Getting started ==
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]

<syntaxhighlight lang="bash">
# this is a test of the syntax highlighting
echo "hello world!" | sed 's/world/Ubuntu phone/'
hello Ubuntu phone!
</syntaxhighlight>

Main Page

2015-04-17T20:19:53Z

Chris:

Find Phone

2015-04-17T20:17:52Z

Chris: