FinalS06.Angela History

Hide minor edits - Show changes to markup - Cancel

April 22, 2006, at 12:36 PM by 69.114.53.120
Changed line 17 from:

FINAL PROJECT PROPOSAL \\

to:

FINAL PROJECT: INITIAL PROPOSAL \\

April 22, 2006, at 12:36 PM by 69.114.53.120
Changed lines 14-16 from:
to:
April 22, 2006, at 12:35 PM by 69.114.53.120
Deleted lines 14-15:
April 22, 2006, at 12:34 PM by 69.114.53.120
Changed line 7 from:
to:
Deleted lines 8-9:

Visual Diagram coming soon... \\

April 22, 2006, at 12:32 PM by 69.114.53.120
Added lines 4-6:

Final Presentation, 4/19
(Michael, I'll be updating this prior to Wed with add'l images + references to context)

April 05, 2006, at 08:54 AM by 69.114.53.120
Changed lines 16-17 from:
to:
April 05, 2006, at 08:54 AM by 69.114.53.120
Changed lines 15-17 from:
to:
April 05, 2006, at 08:52 AM by 69.114.53.120
Changed line 8 from:
to:

Schedule

April 05, 2006, at 08:14 AM by 69.114.53.120
Changed line 10 from:

Tech Research: BlueSMiRF (work in progress!)

to:

Tech Research: BlueSMiRF

April 05, 2006, at 08:13 AM by 69.114.53.120
Added lines 12-13:

Code Samples \\

April 05, 2006, at 03:06 AM by 69.114.53.120
Changed line 10 from:

Tech Research: BlueSMiRF

to:

Tech Research: BlueSMiRF (work in progress!)

April 05, 2006, at 01:41 AM by 216.165.95.5
Changed line 10 from:
to:

Tech Research: BlueSMiRF

March 29, 2006, at 06:54 PM by 216.165.95.5
Changed line 4 from:
to:
Changed line 6 from:

Visual Diagram coming soon...

to:

Visual Diagram coming soon...

Changed line 16 from:

FINAL PROJECT PROPOSAL#1 \\

to:

FINAL PROJECT PROPOSAL \\

Changed line 83 from:

March 29, 2006 #3\\

to:

March 29, 2006 \\

March 29, 2006, at 06:40 PM by 216.165.95.5
Changed lines 12-13 from:

Related Projects? coming soon...

to:
March 29, 2006, at 06:36 PM by 216.165.95.5
Changed line 8 from:
to:
March 29, 2006, at 06:31 PM by 216.165.95.5
Changed line 10 from:

Tech Research: BlueSMiRF coming soon...

to:
March 29, 2006, at 06:27 PM by 216.165.95.5
Changed lines 1-16 from:

FINAL PROJECT PROPOSAL \\

to:

FINAL PROJECT - Spring 2006
Jammer / ReMember?

Proposal
Visual Diagram coming soon...
Work Completed To-Date 03/29/06
Tech Research: BlueSMiRF coming soon...
Related Projects? coming soon...


FINAL PROJECT PROPOSAL#1 \\

Changed line 83 from:

March 29, 2006 \\

to:

March 29, 2006 #3\\

March 29, 2006, at 08:14 AM by 69.114.53.120
Changed lines 81-84 from:

Informal surveys regarding types of checks people perform to make sure their devices, keys, and wallets are present. What do you do??

to:

Informal surveys regarding types of checks people perform to make sure their devices, keys, and wallets are present. What are your habits?

March 29, 2006, at 08:12 AM by 69.114.53.120
Changed lines 79-80 from:

Researching various types of feedback and informal surveys of users who heavily rely on their cell phones, PDAs?, etc.

to:

Researching various types of feedback for ReMember? layer of project.

Informal surveys regarding types of checks people perform to make sure their devices, keys, and wallets are present. What do you do??

March 29, 2006, at 07:57 AM by 69.114.53.120
Changed lines 73-76 from:

+++ ->Enter configuration mode
ATSI, 2 Find chip's name
ATSN, newName ''Allows you to rename chip"

to:

+++ (Enter configuration mode)
ATSI, 2 (Find chip's name)
ATSN, newName (Allows you to rename chip)

March 29, 2006, at 07:56 AM by 69.114.53.120
Changed line 73 from:

+++ Enter configuration mode \\

to:

+++ ->Enter configuration mode \\

March 29, 2006, at 07:55 AM by 69.114.53.120
Changed line 74 from:

ATSI, 2 ''Find chip's name" \\

to:

ATSI, 2 Find chip's name \\

March 29, 2006, at 07:54 AM by 69.114.53.120
Added lines 66-80:

March 29, 2006
Work Completed To-Date:

Working with BlueSMiRF Basic Model. Setup of Bluetooth chip on breadboard, naming and recognition with laptop via Bluetooth Setup Assistant on Mac laptop. Ran ZTerm? serial communication and entered following AT commands:

+++ Enter configuration mode
ATSI, 2 Find chip's name"
ATSN, newName
Allows you to rename chip"

Python installation and testing of basic scripts on Nokia 6630 cell phone.

Researching various types of feedback and informal surveys of users who heavily rely on their cell phones, PDAs?, etc.

March 29, 2006, at 07:42 AM by 69.114.53.120
Changed lines 58-60 from:

Project blog

A list of compiled resources to date

to:

Group project blog

A list of compiled resources to date (del.icio.us links)

March 29, 2006, at 07:42 AM by 69.114.53.120
Changed lines 23-24 from:

ReMember? – We are interested in commenting on our social attachment to external technological devices. Through wearable technology, and providing some form of audio or visual feedback (TBD), a physical layer of the project will look at our sense of “completeness” when our devices are present.

to:

ReMember? – We are interested in commenting on our social attachment to external technological devices. Through wearable technology, and providing some form of audio or visual feedback (TBD), a physical layer of the project will look at our sense of “completeness” when our devices are present.

March 29, 2006, at 07:41 AM by 69.114.53.120
Changed lines 6-7 from:

CONCEPT

to:

CONCEPT \\

Changed lines 15-16 from:

PROBLEM

to:

PROBLEM \\

Changed lines 20-21 from:

GOAL / PURPOSE OF THE PROJECT

to:

GOAL / PURPOSE OF THE PROJECT \\

Changed lines 48-49 from:

DESIGN & IMPLEMENTATION

to:

DESIGN & IMPLEMENTATION \\

Changed lines 57-58 from:

REFERENCES

to:

REFERENCES \\

Changed lines 61-63 from:

Rivest, Ronald L. Chaffing and Winnowing: Confidentiality without Encryption. 1998. < http://theory.lcs.mit.edu/~rivest/chaffing.txt>

to:




1. Rivest, Ronald L. Chaffing and Winnowing: Confidentiality without Encryption. 1998. < http://theory.lcs.mit.edu/~rivest/chaffing.txt>

March 29, 2006, at 07:40 AM by 69.114.53.120
Changed lines 12-14 from:
''adding fake packets with bogus MACs?. The chaff packets have the correct overall format, have reasonable serial numbers and reasonable message contents, but have MACs? that are not valid. The chaff packets may be randomly intermingled with the good (wheat) packets to form the

transmitted packet sequence.''(1)

to:
adding fake packets with bogus MACs?. The chaff packets have the correct overall format, have reasonable serial numbers and reasonable message contents, but have MACs? that are not valid. The chaff packets may be randomly intermingled with the good (wheat) packets to form the transmitted packet sequence.(1)
March 29, 2006, at 07:39 AM by 69.114.53.120
Added lines 1-69:

FINAL PROJECT PROPOSAL
Group Project: Angela Pablo, Pollie Barden, Sonali Sridhar
Combined with Every Bit You Make

CONCEPT

Jammer is an exploration in mobile communication through open Bluetooth sockets. It will look into the possibilities of creating conversation between two open Bluetooth devices which creates “noise”. At this point, if these devices encounter vulnerability to being snooped or hacked, the only data available to grab would be this noise (such as false SMS or contact lists) being transmitted from one Bluetooth device to another.

In effect, this broadcast intentionally sends out garbled data or chaff:

''adding fake packets with bogus MACs?. The chaff packets have the correct overall format, have reasonable serial numbers and reasonable message contents, but have MACs? that are not valid. The chaff packets may be randomly intermingled with the good (wheat) packets to form the

transmitted packet sequence.''(1)

This is also an exploration of a community that can be created by the interlinking of mobile objects on our body thus playing out the idea of the technological ever-present second skin. ReMember? comments on the creation of this second skin through dependence on these external elements and conversations that occur between them.

PROBLEM

With the bluetooth specification becoming more popular in the US, along with our dependence upon external devices such as our cell phones, PDAs?, and laptops to communicate and store personal information, the vulnerability of our information is growing as well.

A number of hacking methods have emerged, including bluesnarfing, bluebugging, and bluesniping. Hackers can gain control of your mobile device, make long distance phone calls, steal your contacts, and read your SMS messages.

GOAL / PURPOSE OF THE PROJECT

Jammer – Rather than hiding or encrypting information, Jammer injects chaff into the Bluetooth network, thereby jamming it with a flood of data.

ReMember? – We are interested in commenting on our social attachment to external technological devices. Through wearable technology, and providing some form of audio or visual feedback (TBD), a physical layer of the project will look at our sense of “completeness” when our devices are present.

AREAS OF RESEARCH

Social Aspects
* Social impact of Bluetooth technology
* Behavioral changes among users
* User dependence on technological devices (psychological, emotional, physical)
* Feedback loop
* Continuous passive attention

Code Elements
* Tcpdump/Kismac/Ethereal
* Bluetooth (AT commands)
* Bluesnarfing
* Python
* Chaffing & winnowing (broadcast)

Physical & Hardware
* Nokia Series 60 (6630 and N70 models)
* Bluetooth Modem (BlueSMiRF?)
* Hardware wiring of project components
* Wearables
* Physical locking device

DESIGN & IMPLEMENTATION

Jammer – We will utilize tcpdump/KisMAC?/Ethereal to retrieve data from the surrounding wifi network. This will then serve as the content for the garbled information/conversations between the Bluetooth devices. We will be working with primarily a Nokia 6630 cell phone to both store data and broadcast the garbled conversations and other information.

The broadcast will occur between the cell phone, wallet and keys – all of which will be embedded with Bluetooth technology.

Based on our initial research, the method of chaffing and winnowing\ as presented by Ronald L. Rivest from the MIT Lab for Computer Science, may perform the task of protecting the data in our scenario. The garbled data will be fed via Bluetooth from laptop to cellphone, and a Python script will broadcast the chaff.

ReMember? – A wearable will also be designed to hold the following elements: cell phone, wallet, keys. These pieces will “converse” with each other to inform the user of their presence/absence. When locked in, the wearable will provide the user some type of audio or visual feedback to confirm they are in place. Should they go missing, an alert will notify the user of their absence.

REFERENCES

Project blog

A list of compiled resources to date

Rivest, Ronald L. Chaffing and Winnowing: Confidentiality without Encryption. 1998. < http://theory.lcs.mit.edu/~rivest/chaffing.txt>


Page last modified April 22, 2006, at 12:36 PM