Hacking_and_Penetration_Testing_with_Low_Power_Devices

Adding tools the hard way
69
# check the file extension
extension¼$(echo ${fname} j tr "." "\n" j tail -1)
if [ "$extension" !¼ "deb" ] ; then
echo "${fname} does not appear to be a Debian package file"
echo -n\
"Enter a command to uncompress or rename it or press Enter for none >"
read resp
if [ "$resp" !¼ "" ] ; then
# run the command
'$resp'
# fix the filename
fname¼$(echo $fname j sed "s/\.${extension}$/\.deb/")
fi
fi
command¼"dpkg -i /tmp/${fname}"
${command}
}
# interate over the download list
# read whole file into an array
declare -i count¼0
while read line
do
pkg¼$(echo ${line} j awk '{print $1}')
pkg_list[$count]¼${pkg}
url¼$(echo ${line} j awk '{print $2}')
url_list[$count]¼${url}
count+¼1
done < "packages-to-download.txt"
# now actually download and install
count¼0
for pkg in ${pkg_list[@]}
do
url¼${url_list[$count]}
dl_pkg
install_pkg
count+¼1
done
ADDING TOOLS THE HARD WAY
If packages are not available for a tool, building from source might be the only
option. There are a number of different ways to build tools for the Beagles. The most
straightforward method is to download the code and build it directly on the Beagle.
Code can also be built from another Linux desktop system, a process known as cross