3. Adding Hardware Security with the CryptoCape | BeagleBone for Secret Agents

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

BeagleBone for Secret Agents

By : Joshua Datko

4 (2)

BeagleBone for Secret Agents

4 (2)

By: Joshua Datko

Overview of this book

If you have some experience with the BeagleBone or similar embedded systems and want to learn more about security and privacy, this book is for you. Alternatively, if you have a security and privacy background and want to learn more about embedded development, this book is for you. You should have some familiarity with Linux systems and with the C and Python programming languages.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Creating Your BeagleBone Black Development Environment

1. Creating Your BeagleBone Black Development Environment

Introducing the BBB

Creating an embedded development environment with Emacs

Finding additional background information

Summary

2. Circumventing Censorship with a Tor Bridge

2. Circumventing Censorship with a Tor Bridge

Learning about Tor

Installing Tor on BBB

Understanding Tor exit policies

Setting bridge-specific settings

Starting your new Tor bridge

Enabling port forwarding

Adding physical interfaces to the bridge

Determining your bandwidth with speedtest-cli

Controlling the bridge with the Stem library

Connecting to your obfuscated bridge

Continuing with Tor-related projects

Summary

3. Adding Hardware Security with the CryptoCape

3. Adding Hardware Security with the CryptoCape

Exploring the differences between hardware and software cryptography

Touring the CryptoCape

Discovering the I2C protocol

Understanding the benefit of cape EEPROMs

Creating an eLinux wiki site

Keeping time with a real-time clock

Trusting computing devices with a Trusted Platform Module

Providing hardware authentication with ATSHA204 and ATECC108

Encrypting EEPROM data with the ATAES132

Combining the BBB with an ATmega328p

Building a two-factor biometric system

Summary

4. Protecting GPG Keys with a Trusted Platform Module

4. Protecting GPG Keys with a Trusted Platform Module

History of PGP

Developing a threat model

Generating GPG keys

Protecting your GPG key with a TPM

Adding the keypad

Taking ownership of the TPM

Extending a PCR

Unlocking your key at startup

Iterating on the threat model

Summary

5. Chatting Off-the-Record

5. Chatting Off-the-Record

Communicating Off-the-Record – a background

Installing BitlBee on the BeagleBone

Adding OTR to your BitlBee server

Marshalling your IRC connections with a Bouncer

Extending the project

Summary

A. Selected Bibliography

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

Index

Index

Customer Reviews

4 (2)

5 star

50%

4 star

0

3 star

50%

2 star

0

1 star

0

Understanding the benefit of cape EEPROMs

At a glance, the CAT24C256 Electrically Erasable Programmable Read Only Memory (EEPROM) doesn't appear to add much value to the board. After all, the BeagleBone has a 2GB eMMC on the early revisions and a 4GB eMMC on revision C. An extra 256 kB of memory is hardly food scraps for the beagle. However, it serves a greater purpose; it's what enables automatic cape detection by the BBB.

The BBB has two 46 pin female expansion ports offering much more I/O capabilities than any other hobbyist board on the market. Certain pins can actually support eight different modes, mode 0 through mode 7. The mapping of pin features to a mode is known as pin muxing, short for pin multiplexing. To use a pin in a certain mode, the software must enable and configure this pin through the kernel's interface. This can be manually performed or scripted, but the easiest method is to use a BeagleBone cape.

During the kernel startup, the software will probe the I2C bus looking...

Search

Your notes and bookmarks