Hacking_and_Penetration_Testing_with_Low_Power_Devices

Recommendations

Info

Remote control via python 183 Merely adding a start-up script to /etc/init.d is not enough to cause the MeshDeck client daemon to start automatically when the system boots. Symbolic links to the start-up script must be created in the subdirectories for each of the target run levels. The update-rc.d utility allows these symbolic links to be easily created. The appropriate command is sudo update-rc.d meshdeckd defaults. An install script can be used to automatically install all of the prerequisites for running the MeshDeck as either a client or a server. The script can also set up the appropriate start-up scripts. The following start-up script will install the MeshDeck and ask if it should be configured as a drone daemon. The latest version of this script and associated files can be obtained from my GitHub site by executing the command git clone https://github.com/ppolstra/MeshDeck: #! /bin/bash # Install script for the MeshDeck addon to The Deck # Initially created for a presentation at Blackhat EU 2013 # This version 2.0 was created for the book # Hacking and Penetration Testing With Low Power Devices # by Dr. Phil Polstra # # Public domain, no warranty, etc. etc. # # first check if you are root if [ "$UID" !¼ "0" ]; then echo "Ummm... you might want to run this script as root"; exit 1 fi # check to see if they have Python command -v python >/dev/null 2>&1 jj { echo "Sorry, but you need Python for this stuff to work"; exit 1; } # extract XBee Python module to /tmp then install echo "Installing XBee Python module" tar -xzf XBee-2.1.0.tar.gz -C /tmp jj { echo "Could not install XBee module"; exit 1; } currdir¼$PWD cd /tmp/XBee-2.1.0 python setup.py install jj { echo "XBee module install failed"; exit 1; } echo "XBee Python module successfully installed"
184 CHAPTER 7 Building an army of devices # setup the files echo "Creating files in /usr/bin, /usr/sbin, and /etc/init.d" cd $currdir (cp meshdeck.py /usr/bin/MeshDeck.py && chmod 744\ /usr/bin/MeshDeck.py) jj { echo "Could not copy MeshDeck.py to /usr/bin"; exit 1; } # create symbolic link in /usr/sbin if [ ! -h /usr/sbin/meshdeckd ]; then ln -s /usr/bin/MeshDeck.py /usr/sbin/meshdeckd jj { echo "Failed to create symbolic link in /usr/sbin"; exit 1; } ; fi # create file in /etc/init.d (cp meshdeckd /etc/init.d/. && chmod 744 /etc/init.d/meshdeckd)\ jj { echo "Failed to create daemon script in /etc/init.d"; exit 1; } # is this a drone? if so should be automatically start it? read -p "Set this to automatically run as a drone?" yn case $yn in [Nn]* ) exit;; * ) update-rc.d meshdeckd defaults; read -p "start daemon now?" yn case $yn in [Nn]* ) exit;; * ) /etc/init.d/meshdeckd start;; esac ;; esac SAVING POWER A Series 2 XBee modem that is sending or receiving data uses approximately 40-50 mA of current at 3.3 V. The extended range Series 2 XBee-PRO adapters consume approximately 55 and 250-295 mA of current when receiving and transmitting, respectively. Significant power savings can be realized by reducing transmission times and by putting the modems to sleep whenever possible. Buffering information and transmitting data in batches of packets of maximum size allow the transmission circuit in an XBee modem to be energized for a shorter period of time. This is how the previously described MeshDeck Python module operates. The transmit power can also be reduced by setting the PL (power level) variable
Page 2 and 3:
Hacking and Penetration Testing wit
Page 4 and 5:
Hacking and Penetration Testing wit
Page 6 and 7:
Dedicated to my favorite wife, my f
Page 8 and 9:
Contents Foreword..................
Page 10 and 11:
Contents ix Network Hubs and Switch
Page 12 and 13:
Foreword So I will start out this f
Page 14 and 15:
Author Biography Dr. Philip Polstra
Page 16 and 17:
Acknowledgments First and foremost,
Page 18 and 19:
CHAPTER Meet the deck 1 INFORMATION
Page 20 and 21:
The deck 3 FIGURE 1.1 Collection of
Page 22 and 23:
The deck 5 FIGURE 1.4 Fern WiFi Cra
Page 24 and 25:
The deck 7 MODES OF OPERATION One o
Page 26 and 27:
The deck 9 stores data only on a lo
Page 28 and 29:
Summary 11 I knew that The Deck, wh
Page 30 and 31:
CHAPTER Meet the beagles 2 INFORMAT
Page 32 and 33:
Texas instruments devices 15 FIGURE
Page 34 and 35:
Texas instruments devices 17 proces
Page 36 and 37:
Page 38 and 39:
Texas instruments devices 21 The AD
Page 40 and 41:
Texas instruments devices 23 WHY NO
Page 42 and 43:
Page 44 and 45:
CHAPTER Installing a base operating
Page 46 and 47:
Introduction 29 FIGURE 3.2 QNX smar
Page 48 and 49:
Introduction 31 FIGURE 3.4 Android
Page 50 and 51:
Introduction 33 (http://openembedde
Page 52 and 53:
Introduction 35 FIGURE 3.6 Arch Lin
Page 54 and 55:
Introduction 37 Sabayon In the phys
Page 56 and 57:
Introduction 39 Table 3.7 Fedora Pe
Page 58 and 59:
Introduction 41 tar xJf debian*.xz
Page 60 and 61:
Ubuntu options 43 supportive commun
Page 62 and 63:
Creating a microSD Card 45 Device t
Page 64 and 65:
Chapter 3 Appendix: digging deeper
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
CHAPTER Filling the toolbox 4 INFOR
Page 74 and 75:
Adding a graphical environment 57 b
Page 76 and 77:
Adding a graphical environment 59 W
Page 78 and 79:
Adding a graphical environment 61 t
Page 80 and 81:
Adding tools the easy way 63 The li
Page 82 and 83:
Adding tools the easy way 65 check_
Page 84 and 85:
Adding tools the easy way 67 echo -
Page 86 and 87:
Adding tools the hard way 69 # chec
Page 88 and 89:
Adding tools the hard way 71 descri
Page 90 and 91:
Adding tools the hard way 73 FIGURE
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Adding tools the hard way 85 dl_src
Page 104 and 105:
Starter set of tools 87 and possibl
Page 106 and 107:
Starter set of tools 89 #get John w
Page 108 and 109:
Starter set of tools 91 The company
Page 110 and 111:
CHAPTER Powering The Deck 5 INFORMA
Page 112 and 113:
Power requirements 95 the city and
Page 114 and 115:
Power sources 97 WALL POWER When it
Page 116 and 117:
Power sources 99 Thanks to commonly
Page 118 and 119:
Power sources 101 Table 5.2 Duracel
Page 120 and 121:
Reducing power consumption 103 REDU
Page 122 and 123:
Penetration testing with a single b
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Summary 121 site. In-depth testing
Page 140 and 141:
CHAPTER Input and output devices 6
Page 142 and 143:
Display options 125 FIGURE 6.1 LCD7
Page 144 and 145:
IEEE 802.11 wireless 127 The Alfa A
Page 146 and 147:
BeagleBone capes 129 FIGURE 6.4 UAR
Page 148 and 149:
BeagleBone capes 131 pull-up resist
Page 150 and 151: BeagleBone capes 133 FIGURE 6.7 XBe
Page 152 and 153: BeagleBone capes 135 Newly created
Page 154 and 155: BeagleBone capes 137 Table 6.1 Cape
Page 156 and 157: BeagleBone capes 139 If you don’t
Page 158 and 159: Penetration testing with a single r
Page 170 and 171: Summary 153 if "done" in status.ite
Page 172 and 173: CHAPTER Building an army of devices
Page 174 and 175: Using IEEE 802.15.4 networking 157
Page 176 and 177: Configuring IEEE 802.15.4 modems 15
Page 184 and 185: Remote control the easy way 167 FIG
Page 186 and 187: Remote control via python 169 seria
Page 188 and 189: Remote control via python 171 impor
Page 190 and 191: Remote control via python 173 elif
Page 192 and 193: Remote control via python 175 dnum
Page 194 and 195: Remote control via python 177 rc_na
Page 196 and 197: Remote control via python 179 The M
Page 198 and 199: Remote control via python 181 } [ "
Page 202 and 203: Saving power 185 on the modem. The
Page 204 and 205: Adding security 187 a different cha
Page 206 and 207: Expanding Your Reach 189 FIGURE 7.1
Page 208 and 209: Penetration testing with multiple d
Page 220 and 221: Summary 203 # if IP and MAC aren’
Page 222 and 223: CHAPTER Keeping your army secret 8
Page 224 and 225: Hiding devices 207 FIGURE 8.2 At fi
Page 226 and 227: Hiding devices 209 FIGURE 8.4 Car d
Page 228 and 229: Hiding devices 211 FIGURE 8.7 Wirel
Page 230 and 231: Hiding devices 213 FIGURE 8.11 Unde
Page 232 and 233: Hiding devices 215 FIGURE 8.14 Unde
Page 234 and 235: FIGURE 8.17 Inside the Dalek Desk D
Page 236 and 237: FIGURE 8.21 The haxtar. The haxtar
Page 238 and 239: Installing devices 221 example, wea
Page 240 and 241: CHAPTER Adding air support 9 INFORM
Page 242 and 243: Building the AirDeck 225 Latte is s
Page 244 and 245: Building the AirDeck 227 what you a
Page 246 and 247: Using your aerial drone 229 Power i
Page 248 and 249: Using your aerial drone 231 Install
Page 250 and 251:
Alternative aircraft 233 else { //
Page 252 and 253:
CHAPTER Future directions 10 INFORM
Page 254 and 255:
Closing thoughts 237 For reasons me
Page 256 and 257:
Index Note: Page numbers followed b
Page 258 and 259:
Index 241 configuration, 77-79, 83f
Page 260:
Index 243 Python scripts, 143-144 w
show all

Hacking_and_Penetration_Testing_with_Low_Power_Devices

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?