operating system support for mobile devices

Security and Cooperation, Wrap up

4/23/2009

Richard Yang

Admin.

Projects due May 12

We will continue to hold regular office hours until May 12 or you can send email to make appointments

Recap: Adaptive Mobile Applications

Client: informs service capability/status makes best use of available resource/data

Service: adapts to client capability/status audio/image/video/web content adaption

client service

request

result

Example: Adapting Web Content

One major goal of the World Wide Web Consortium (W3C) has been device-independent content by decoupling layout from rendering

What are some arguments that we need to adapt web content for mobile devices?

Web Content Adaption Approaches HTML auto formatting

Variant selection (e.g., according to HTTP accept or x-wap-profile of UAProf)

Content negotiation RFC 2295: Transparent Content Negotiation in

Transcoding E.g., pdf to html, html to XHTML-MP/WML

Example: Adapting Web Content

WAP defines wireless application environment (WAE) to produce content suitable for wireless devices XHTML-MP (mobile profile) in WAP 2.0 Wireless Markup Language (WML) in earlier versions of

WAP 2.0 Architecture

Servicediscovery

Securityservices

External services EFI

Provisioning

NavigationDiscovery

ServiceLookup

Cryptolibraries

Authenti-cation

Identification

Securetransport

Securebearer

Multimedia Messaging (Email)

WAE/WTA User Agent (WML, XHTMLMP)

Content formats

Datagrams(WDP, UDP)

Connections(TCP with

wireless profile)

Hypermedia transfer (WTP+WSP, HTTP)

Strea-ming

PushOTA

Capability Negotiation

Synchronisation Cookies

Was: WAP Forum, co-founded by Ericsson, Motorola, Nokia, Unwired Planet now: Open Mobile Alliance (Open Mobile Architecture + WAP Forum + SyncML + …)

Session

Transport

Datagram

Transport layer security

Wireless Markup Language

W3C XML-based language

Tag-based browsing language: screen management (text, images) data input (text, selection lists, etc.) hyperlinks & navigation support

WML High-Level Structure

WML pages are called DECKS

Each deck consists of a set of CARDS, related to each other with links

When a WML page is accessed from a mobile phone, all the cards in the page are downloaded from the WAP server

WML Elements Deck/Card Elements wml card template head access meta

Tasks go prev refresh noop

Event Elements do ontimer onpick onevent postfield

onenterforward onenterbackward

Variables setvar

User input input select option optgroup fieldset

Anchors, Images, and Timers a anchor img timer

Text Formatting br p table tr td

Header

Card1Navigation

Variable

SelectElements

WML Example

<?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> <WML> <CARD> <DO TYPE=“ACCEPT”> <GO URL=“#eCard”/> </DO> Welcome! </CARD> <CARD NAME=“eCard”> <DO TYPE=“ACCEPT”> <GO URL=“/submit?N=$(N)&S=$(S)”/> </DO> Enter name: <INPUT KEY=“N”/> Choose speed: <SELECT KEY=“S”> <OPTION VALUE=“0”>Fast</OPTION> <OPTION VALUE=“1”>Slow</OPTION> <SELECT> </CARD></WML>

<WML> <CARD> <DO TYPE="ACCEPT" LABEL="Next"> <GO URL="#card2"/> </DO> Dalhousie<BR/>Directory </CARD>

<CARD NAME="card2"> <DO TYPE="ACCEPT"> <GO URL="?send=$type"/> </DO> Services <SELECT KEY="type"> <OPTION VALUE="em">1.Email</OPTION> <OPTION VALUE="ph">2.Phone</OPTION> <OPTION VALUE="fx">3.Fax</OPTION> </SELECT> </CARD></WML>

DalhousieDirectory_____________Next

Services1. Email2. Phone3. Fax .OK

Navigation Path: An Example

Third Party Adaptation: WAP Gateways

Translate, e.g., between text WML and binary WML (WMLC) from HTML web sites to WML, WMLC, or

XHTML-MP

Add additional information to each request this would be configured by the operator and

could include telephone numbers, location, billing information, and handset information

WAP Gateway for Web Provides a link between a mobile network and Internet Converts the 'Web' response into a 'WAP' response, e.g.,

HTML -> WML pages, or WML bytecode (WMLC) to reduce the size and number of packets

Web Server

Content

WAP Gateway

Encoder,Decoder

WMLScriptCompiler

Protocol Adapters

Client

WML-Script

WAP HTTP

Request URL Request

HTTP Request

HTTP Response

Response WML Content

Example Message Flow

Example:

http://en.wikipedia.org/wiki/Wikipedia:WAP_access

Status

WAP 2.0 is moving towards XHTML-MP XHTML-MP removes many WML features

http://www.developershome.com/wap/xhtmlmp/xhtml_mp_tutorial.asp?page=wmlFeaturesLost

Given emergence of newer phones such as iPhone and Android, it is not clear special content encoding is necessary

Summary

Adaptation is a key design consideration of mobile application/systems

It involves efforts of both clients and services

Big Picture

Foundational Primitives: Communications, Location, Service Discovery,

UI/Media, Power Management, Security

Application Development Framework

Applications (Adaptation, and support for adaptations)

Security and Cooperation in Wireless and Mobile

Networks

Introduction

This is a vast and active field, a course by itself

Many references on wireless security A good book on wireless cooperation:

Thwarting Malicious and Selfish Behaviorin the Age of Ubiquitous Computing, by Levente Buttyan and Jean-Pierre Hubaux, Cambridge University Press, 2007.

available at: http://secowinet.epfl.ch/

Generic Network Security Attack Models

authenticity; incentive-compatibility

confidentiality

integrity

availability

Why is Security Challenging in Wireless/Mobile Networks? No inherent physical protection

physical connections between devices are replaced by logical associations

sending and receiving messages do not need physical access to the network infrastructure (cables, hubs, routers, etc.)

Broadcast communications wireless usually means radio, which has a broadcast

nature transmissions can be overheard by anyone in range anyone can generate transmissions,

• which will be received by other devices in range• which will interfere with other nearby transmissions

Thus it is easier to implement jamming, eavesdropping, injecting bogus messages, and replaying previously recorded messages

Why is Security Challenging in Mobile Networks?

Since mobile devices typically have limited resources (e.g., CPU cycles, battery supply), the designer might want to select simple security mechanisms

However, this may lead to serious security flaws bad example: Wired Equivalent Protection

(WEP), the original security protocol for 802.11

WEP: A Bad Example

802.11 Message Flow

data messagesprotected by WEP

Wired Equivalent Privacy (WEP)

WEP was intended to provide comparable confidentiality to a traditional wired network, thus the name

WEP implements message confidentiality and integrity

WEP encryption is used in 802.11 authentication

WEP Security

WEP confidentiality through encryption using RC4, a stream-

based encryption algorithm using a shared key

WEP integrity through message check sum using encrypted

cyclic redundancy check (CRC)

WEP authentication through challenge/response

WEP Encryption

For each message to be sent: RC4 is initialized with the shared secret

between station STA and access point (AP)• WEP allows up to 4 shared keys

RC4 produces a pseudo-random byte sequence (key stream) from the shared key

This pseudo-random byte sequence is XORed to the message

WEP Encryption To avoid using the same key stream, WEP

encrypts each message with a different key stream the RC4 generator is initialized with the

shared secret plus a 24-bit IV (initial value)• shared secret is the same for each message• 24-bit IV for each message• there is no specification on how to choose the IV;

sender picks the IV value

WEP Integrity

WEP integrity protection is based on computing ICV (integrity check value) using CRC and appended to the message

The message and the ICV are encrypted together

IV secret key RC4RC4

message | ICV

message | ICVIV

IV secret key RC4RC4

message | ICV

encode

decode

CRCCRC

check CRC

Active Attack on WEP: IV Replay Attacks

A known plain-text message is sent to an observable wireless LAN client (how?)

The network attacker will sniff the wireless LAN looking for the predicted cipher-text

The network attacker will find the known frame, derive the key stream (corresponds to the give IV+K), and reuse the key stream

Active Attack on WEP: Bit-Flipping Attack

The attacker sniffs a frame on the wireless LAN The attacker captures the frame and flips random bits in the data

payload of the frame The attacker modifies the ICV (detailed later) The attacker transmits the modified frame The access point receives the frame and verifies the ICV based

on the frame contents The AP accepts the modified frame The destination receiver de-encapsulates the frame and

processes the Layer 3 packet Because bits are flipped in the higher layer packet, the Layer 3

checksum fails The receiver IP stack generates a predictable ICMP error The attacker sniffs the wireless LAN looking for the encrypted

error message Upon receiving the error message, the attacker derives the key

stream as with the IV replay attack

Bit-Flipping Attack

Generating Valid CRC

The crucial step of the flipping attack is to allow the frame to pass the ICV check of the AP

Unfortunately, the CRC algorithm allows generating valid encrypted ICV after bit flipping

Bypassing Encrypted ICV

CRC is a linear function wrt to XOR:

CRC(X Y) = CRC(X) CRC(Y)

- Attacker observes (M | CRC(M)) K where K is the key stream output- for any M, the attacker can compute CRC(M) - hence, the attacker can compute:

([M | CRC(M]) K) [M | CRC(M)] = ([M M) | (CRC(M) CRC(M)]) K= [M M) | CRC(M M)] K

WEP Authentication

Two authentication modes

open authentication --- means no authentication !

• an AP could use SSID authentication and MAC address filtering, e.g., at Yale

shared key authentication based on WEP

WEP Shared Key Authentication Shared key authentication is based on a

challenge-response protocol:…AP STA: rSTA AP: IV | (r K)…

where K is a 128 bit RC4 output on IV and the shared secret

An attacker can compute r (r K) = K

Then it can use K to impersonate STA later:…AP attacker: r’attacker AP: IV | (r’ K)…

WEP: Lessons

WEP has other problems, e.g., short IV space, weak RC4 keys

Engineering security protocols is difficult one can combine otherwise OK building blocks in a

wrong way and obtain an insecure system at the end• example 1:

– stream ciphers alone are OK– challenge-response protocols for entity authentication are OK– but they shouldn’t be combined

• example 2:– encrypting a message digest to obtain an ICV is a good principle– but it doesn’t work if the message digest function is linear wrt to the

encryption function

Fixing WEP

After the collapse of WEP, Wi-Fi Protected Access (WPA) was proposed in 2003

Then the full 802.11x standard (also called WPA2) was proposed in 2004

But WEP is still in use

Cooperation in Wireless, Mobile Networks

Cooperation in Wireless Networks

A special case of “security attack” is by rational nodes drop packets, mis-represent information

Motivation wireless networks have limited capacity wireless nodes have limited resource—battery power unlike the Internet, where commercial relationship is

worked out, many mesh network nodes belong to different users and may not have incentive to forward others’ traffic

• similar free-riding problems in P2P applications

Reward-based Routing The network (authority) rewards the nodes so

that they will forward traffic from a source to a destination

Each node has a (private energy/transmission) cost of sending one packet to a neighbor

The objective of the authority is to choose the lowest cost path assume cost reflects energy thus extending network

life time/maximizing capacity—the community benefit

Node Utility Assume each node wants to maximize its utility The utility of being on the path P of a source-

destination pair:

where - pi is the amount the network rewards node i - 1P(i) is 1 if node i is on the path P; otherwise 0

- ci is the cost of the link used in P, if a link from i is used

)(1 icpu Piii

Discussion

How about we reward nodes according to their claimed costs?

)(1 icpu Piii

Payment Using VCG Mechanism VCG stands for Vickrey, Clarke and Groves The VCG mechanism

each node sends the costs of its links to the authority the authority computes the lowest cost path from the

source S to the destination D the payment to node i:

where - LCP(S,D) is the lowest cost path from S to D: {S->R1, R1->R2, …, Rk->D}

- LCP(S,D)\{i} is the previous path but does not include the link from i to its next hop, if i is on the path; if i is not on the path, it is just the previous path

- LCP(S,D;-i) is the lowest cost path from S to D without using i, i.e. remove node i from the graph and then find path

}){\),((cost));,((cost iDSLCPiDSLCPpi

Example: N1

- assume N1 declares the cost as 2, how much will N1 berewared according to the VCG mechanism? (1+3)-1 = 3

- assume N1 declares the cost as 1, how much will N1 berewarded according to the VCG mechanism?

- what is the utility of N1? 3 - 2 = 1

(1+3)-1 = 3- what is the utility of N1? 3 - 2 = 1

- assume N1 declares the cost as 4, how much will N1 berewared according to the VCG mechanism?

Assume the true cost of N1 to D is 2

(1+3)-(1+3) = 0- what is the utility of N1? 0 - 0 = 0

}){\),((cost));,((cost iDSLCPiDSLCPpi

Formal Results

Each node reports its link costs truthfully

Thus the network chooses the lowest cost path for each source-destination pair

Analysis on Truthfulness

By contradiction Assume node i’s true costs for its links are Ci but

reports Wi

think of Wi and Ci as vectors of link costs

The node decides to declare Wi instead of Ci only if the utility is higher

The best scenario a node can be in is that it is given the declared costs of all other nodes’ links and then decides its declarations of the costs of its links in order to maximize its utility action chosen in this way is called dominant strategy

VCG Proof

Assume the lowest cost path computed is - LCP when the node reports Ci, and

- LCP’ when reports Wi

it must be the case that (1P(i) meant i on path P)

)(1}){\),((cost));,((cost

)(1}){\),('(cost));,('(cost ''

iciDSLCPiDSLCP

iciDSLCPiDSLCPLCPLCP

LCPLCPi

)(1}){\),((cost)(1}){\),('(cost '' iciDSLCPiciDSLCP LCPLCPi

LCPLCPi

)(1}){\),((cost)(1}){\),('(cost '' iciDSLCPiciDSLCP LCPLCPi

LCPLCPi

Right hand side is LCP we computed; left hand side is one path. Contradiction.

Revisit some slides of first class

Enabling Technologies

Development and deployment of wireless/mobile technology and infrastructure in-room, in-building, on-campus, in-the-field, MAN,

WAN, GPS Miniaturization of computing machinery . . . -> PCs -> laptop -> PDAs/smart phones ->

embedded computers/sensors Improving device capabilities/software

development environments, e.g., andriod: http://code.google.com/android/ iphone: http://developer.apple.com/iphone/ windows mobile

At Home

cellular

bluetooth

satellite

WiFi 802.11g/n

At Home

Source: http://teacher.scholastic.com/activities/science/wireless_interactives.htm

UMTS,DECT2 Mbit/s

UMTS Rel. 6400 kbit/s

LAN100 Mbit/s,WLAN54 Mbit/s

UMTS Rel. 5400 kbit/s

GSM 115 kbit/s,WLAN 11 Mbit/s

GSM 53 kbit/sBluetooth 500 kbit/s

GSM/EDGE 135 kbit/s,WLAN 780 kbit/s

LAN, WLAN780 kbit/s

Mobile and Wireless Services – Always Best Connected

Habitat Monitoring: Example on Great Duck Island

Patch Network

Transit Network

Basestation

Gateway

A 15-minute human visit leads to 20% offspring mortality

Why is the Field Challenging?

Challenge 1: Unreliable and Unpredictable Wireless Coverage

Asymmetry vs. PowerReception v. Distance

*Cerpa, Busek et. al

What Robert Poor (Ember) calls “The good, the bad and the ugly”

Wireless links are not reliable: they may vary over time and space

Challenge 2: Open Wireless Medium

Wireless interference

Hidden terminals

Exposed terminal

S1 R1 S2

R1 S1 S2 R2

Challenge 2: Open Wireless Medium

Wireless interference

Hidden terminals

Exposed terminal

Wireless security eavesdropping, denial of service, …

S1 R1 R2

R1 S1 S2 R2

Challenge 3: Mobility

Mobility causes poor-quality wireless links

Mobility causes intermittent connection under intermittent connected networks,

traditional routing, TCP, applications all break

Mobility changes context, e.g., location

Challenge 4: Portability

Limited battery power Limited processing, display and storage

Sensors,embeddedcontrollers

Mobile phones• voice, data• simple graphical displays• GSM/3G

PDA phone• data• simpler graphical displays• 802.11/3G

Laptop• fully functional• standard applications• battery; 802.11

PPerformanceerformance/Weight/Power Consumption/Weight/Power Consumption

Challenge 5: Changing Regulation and Multiple Communication Standards

cellular phones satellites wireless LAN

cordlessphones

1992:GSM

1994:DCS 1800

2001:IMT-2000

1982:Inmarsat-

1992:Inmarsat-BInmarsat-M

1998:Iridium

1989:CT 21991:DECT 199x:

proprietary

1997:IEEE 802.11

1999:802.11b, Bluetooth

1988:Inmarsat-

analogue

digital

1991:D-AMPS

1991:CDMA

1981:NMT 450

1986:NMT 900

CT01984

1983:AMPS

1993:PDC

2000:GPRS

2000:IEEE 802.11a

Fourth Generation

(Internet based)

Topics not Covered

There are several topics that are quite interesting but we do not have time to cover in more detail, e.g., Cognitive radio Virtualization of wireless networks Sync (e.g., SyncML) /replicate management Context-aware applications design Mobile device management Controlled mobility

Summary

Driven by technology and vision infrastructure (communication/location) device miniaturization mobile computing platforms

The field is moving fast and has many opportunities

Backup Slides on Cooperation

Backup Slides on Sync/Replicate Management

Discussion

What challenges does the file system face in wireless/mobile environment?

The Problems Caused by Mobility

Read miss stalls progress (the user has to stop working)

Synchronization/consistency issues may need to synchronize multiple copies of

the same file if multiple users, may need to solve

consistency problems

Heterogeneous device types each device has its own file systems and

naming convention, e.g., digital camera, ipod

Approaches

Read miss explicit user file selection, e.g., MS briefcase automatic hoarding, e.g., CODA, SEER

Synchronization/consistency issues keep modification logs and develop merge tools, e.g.,

Bayou efficient file comparisons and merging, e.g., rsync,

Heterogeneous device types masks the differences , e.g., EnsemBlue

SEER: automatic prediction of related files to avoid user manual configuration of

hoarding

SEER: A Predictive Hoarding System

Views user activities as composed of projects than individual files

Predicates files in a project and fetch them together

Discussion: how do you predicate all of the files a project may use?

Basic Idea of SEER: Semantic Distance Quantifies user’s intuition about

relationship between files smaller closer in relation

Infers relationship static (done by an external investigator), e.g.,

• observes directory structure/membership• observes naming convention• #include in a program

dynamic• watches user’s behavior

Lifetime Semantic Distance Looks at file open/close (not file content !!) Lifetime semantic distance:

The lifetime semantic distance between an open of file A and an open of file B is defined as 0 if A has not been closed before B is opened and the number of intervening file opens (including the open of B) otherwise

End up with multiple lifetime semantic distances between two events of two files needs distance between two files, not events uses geometric mean to convert to a single distance

Sample file access sequence

Semantic distance- AB , AC is 0- AD is 3

Basic Idea of SEER: Clustering Algorithm Based on algorithm by

Jarvis and Patrick Allows overlapping clusters Steps

calculates n nearest neighbors for each file

Phase 1: if two points (files here) have at least kn overlapping neighbors, combine their clusters into one

Phase 2: if two points have more than kf but less than kn overlapping neighbors, overlap the clusters i.e. add each to the other cluster

Relation Action

kn ≤x

kf≤x<kn

Combine clustersOverlapping clustersNo action

Summary of clustering algorithm

Example

Seven files , A-G{A} {B} {C} {D} {E} {F}

Phase 1: {A, B} {A, B, C}{D, E} {F, G} {D,E,F, G}

Phase 2:two pairs {A, C} {C, D}

{A, C} : same cluster already{C, D} overlap clusters

Final result {A, B, C, D} {C,D, E, F,G}

Number of shared neighbors

From ToA B C D E F G

ABCDEFG

kn kf kn kf kn

Using Both Lifetime Semantic Distance and the Input of External Investigator

Essentially gives application specific info

Example large directory distance => looser

relationship• subtract directory distance from shared neighbor

Real World Anomalies: Special Cases Many special cases

authors use a heuristic to solve each

Shared libraries e.g. : library X might cause unwanted clustering Heuristic: files which represent more than a

certain percentage of all references marked as “frequently-referenced” (1%)

• eliminate from calculation

Critical files (e.g. : startup files) rarely accessed but important use heuristic and hoard

• special control file that specifies such files• detect by names e.g. .login etc

Temporary files (e.g. : in /tmp) transient and don’t depict correct relationship might displace other important files from n closest heuristic: ignore files in /tmp etc. completely

Simultaneous access e.g. : read mail & compile code independent streams are intermixed ! maintain reference-history on a per-process basis

More Special Cases …

Scheduling of Multimedia Applications

Earliest deadline first (EDF) scheduling

- allocate cycle budget per job

- execute job with earliest deadline and positive budget

- charge budget by number of cycles consumed

- preempt if budget is exhausted

Bayou: automatic conflict update

Bayou: Managing Update Conflicts

Basic idea: application specific conflict detection and update

Two mechanisms for automatic conflict detection and resolution dependency check merge procedure

Bayou Write Operation: An Example

Mobile file systems: dealing with low bandwidth: LBFS: efficient file comparison and merging

Motivation

The CODA system assumes that modifications are kept as logs (CML) a user sends the logs to the servers to update

If the storage of a client is limited, it may not be able to save logs then upon reconnection, the cache manager needs to

find the difference between the stored file and its local cached copy

same problem exists for the rsync tool !

Question: how to efficiently compare the differences of two remote files (when the network connection is slow)?

LBFS: Low-Bandwidth File System

Break Files into chunks and transfer only modified chunks

Fixed chunk size does not work well why?

Flexible Chunk Size

Compute hash value of every 48 byte block if the hash value equals to a magic value, it is

a chunk boundary

What is data synchronization?

Data synchronization “is the process of making two sets of data look identical” (source: syncml.org white paper)

Data Synchronization

Datastore1 Datastore2

A CB C A BA CB

Exchange data modifications Resolve conflicts

What is a “data synchronization protocol”?

• Method of communication for a data synchronization session

• Protocol features:– naming and identification of records– common protocol commands– identification and resolution of

synchronization conflicts

SyncML defined…

“SyncML is a new industry initiative to develop and promote a single, common data synchronization protocol that can be used industry-wide.” (syncml.org)

“SyncML is a specification for a common data synchronization framework and XML-based format […] for synchronizing data on networked devices.” (syncml.org)

“SyncML is a […] protocol for conveying data synchronization operations.” (syncml.org)

SyncML sponsors

SyncML features

• Synchronize any type of data

• Multiple protocol bindings– HTTP, WSP, OBEX

• Security

• Interoperability

client modifications

SyncML: clients & servers

SyncMLserver

server modifications

SyncML synchronization types

• Two-way sync

• Slow sync

• One-way sync from client only

• Refresh sync from client only

SyncML synchronization types (cont.)

• One-way sync from server only

• Refresh sync from server only

• Server alerted sync

SyncML terminology

• Message

• Package

• Command

• Status code

• Datastore

• Device info

• Meta info

• Capabilities exchange

SyncML and XML

• Abbreviated naming convention– Ex: ”protocol version” is <VerProto>

• XML prolog is not required

• WBXML– WAP Binary XML

SyncML documents

• <SyncML> DTD

• Meta info DTD

• Device info DTD

<SyncML> document

<?xml version="1.0"?>

<!DOCTYPE … >

</SyncHdr>

</SyncBody>

</SyncML>

• “A SyncML Message is a well-formed, but not necessarily valid, XML document.” (syncml.org)

• Contains data synchronization commands (operations)

<SyncHdr> element

<VerProto>SyncML/1.0</VerProto>

<SessionID>session41</SessionID>

</SyncHdr>

<SyncBody> element

</Add>

</SyncBody>

SyncML commands

• <Add>

• <Alert>

• <Atomic>

• <Copy>

• <Delete>

• <Exec>

• <Get>

• <Map>

• <Put>

• <Replace>

• <Results>

• <Search>

• <Sequence>

• <Status>

• <Sync>

Meta Info document

• Contains sync session parameters

<MaxMsgSize>586

</MaxMsgSize>

</MetInf>

Device Info document

• Describes device capabilities

• For both client and server

</DevInf>

Sync4j project

• Java implementation of SyncML protocol

• Sync4j client

• Sync4j server

• open source

Sync4j audience

• developers who:– know Java but don’t know SyncML– know SyncML but may not know Java

• commercial application developers

• open source application developers

API design ideas

• SAX API– standard set of interfaces– multiple implementations– usage model: callbacks

• JDOM API– concrete classes; single implementation– root Document object contains Element

objects

API design ideas (cont.)

• Servlet API– usage model: developer builds a new servlet

by subclassing HTTPServlet

• Auto-generate API classes from DTD using an XML data-binding tool - ?

Sync4j design goals

• Hide complexity of the SyncML specification from Java programmers– XML documents, XML parsing– multiple transport protocols

• A complete SyncML implementation

• Interoperability– with existing SyncML clients & servers

Sync4j design goals (cont.)

• API should be natural and familiar to Java programmers– direct object instantiation– exceptions– use Collection API / arrays, where appropriate– event notification via event listeners– familiar naming conventions

Sync4j design goals (cont.)

• API must be familiar to developers who already know the SyncML DTD’s

• API must enforce any restrictions that are defined in the SyncML specification

Sync4j’s modular design

• “core” protocol message library

• transport protocol libraries

• extensible client framework

• extensible server framework

• client application

• server application

Sync4j implementation

• Immutable objects

• Exception class for each SyncML “status code”

• Declaration of constants– public final static variables

• Command object hierarchy

Sync4j command hierarchy

AbstractCommand

ResponseCommandRequestCommand

AddCommand, DeleteCommand,

ReplaceCommand,…

ResultsCommand,StatusCommand

Sync4j toolset

• Jakarta Ant

• JDOM

• Apache Xerces-J

• CVS

• log4j

• Sun JDK 1.4.0

• Sun J2EE SDK

• JUnit

• Apache Tomcat

• Netbeans

Sync4j packages

• sync4j.core

• sync4j.transport

• sync4j.framework

• sync4j.client

• sync4j.server

• sync4j.tests

Sync4j core classes

• Message

• DeviceInfo

• MetaInfo

• Command classes:– AddCommand– DeleteCommand– ReplaceCommand

sync4j.core.Message

• Two ways to construct a Message object:– from a String of XML– from more basic sync4j objects

Sync4j Message example 1

String strXML = “<SyncML> … </SyncML>”;

Message msg;

msg = new Message(strXML);

catch (InvalidMarkupException ex)

catch (XMLSyntaxException ex)

Sync4j Message example 2

SyncHeader header = new SyncHeader(...);

SyncBody body = new SyncBody(...);

Message msg;

msg = new Message(header, body);

String strXML = msg.toXML();

Summary

• Use SyncML to synchronize data between mobile applications and server applications

• SyncML is a complex and powerful data synchronization protocol

• Sync4j hides the complexity of SyncML from Java programmers

For more information…

Please visithttp://sync4j.sourceforge.net/

Backup Slides on TELA

TELSA: A Positive Example

Digital Signatures Do Not Work

Problem statement: authentication of packets

The typical approach in the Internet is to

attach a digital signature on each packet

However, signatures are expensive, e.g., RSA

1024 on a 2.1 GHz desktop: high signature cost (~5 ms)

high communication cost (128 bytes/packet)

More expensive on low-end processors

http://www.cryptopp.com/benchmarks.html

Timed Efficient Stream Loss-tolerant Authentication

Uses only symmetric cryptography

Basic Authentication Mechanism

F(K)AuthenticCommitment

MAC(K,P)

Kdisclosed

1: Verify K

2: Verify MAC

3: P Authentic!

F: public one-way function; MAC: message digest function

TELSA Security Condition

Sender distributes initial commitment and key

disclosure schedule using, say, digital signature

Security condition (for packet P):

on arrival of P, receiver is certain that sender did not

yet disclose K

If security condition not satisfied, drop packet

TESLA: Example

K4 K5 K6 K7

tTime 4 Time 5 Time 6 Time 7

Verify MACs

Authenticate K3

Keys disclosed 2 time intervals after use

TESLA Summary

Advantages low overhead

• communication (~ 20 bytes)• computation (~ 1 MAC computation per packet)

tolerate packet loss

Problems time synchronization delayed authentication

Secure Efficient Ad hoc Distance Vector (SEAD)

Uses one-way hash chains to authenticate metric and sequence number for DSDV

Assumes a limit k-1 on metric (as in other distance vector protocols such as RIP, where k=16) metric value infinity can be represented as k

SEAD Metric Authenticators

Each node generates a hash chain and distributes the last element (CN+1) to allow verification: chain values CN-k+1, …, CN authenticate metrics

0 through k-1 for sequence number 1 CN-2k+1,…CN-k authenticate metrics 0 through k-1

for sequence number 2 CN-ik+1,…CN-(i-1)k authenticate metrics 0 through k-1

for sequence number iC0 C1 C3C2 C5C4

C6 C7 C9C8 C10 C12C11

Each node generates a hash chain anddistributes the last element (CN+1) to allow verification: Chain values CN-k+1, …, CN authenticate

metrics 0 through k-1 for sequence number 1

CN-2k+1,…CN-k authenticate metrics 0 through k-1 for sequence number 2

CN-ik+1,…CN-(i-1)k authenticate metrics 0 through k-1 for sequence number i

C0 C1 C3C2 C5C4

C6 C7 C9C8 C10 C12C11

Each node generates a hash chain and distributes the last element (CN+1) to allow verification: Chain values CN-k+1, …, CN authenticate metrics

0 through k-1 for sequence number 1 CN-2k+1,…CN-k authenticate metrics 0 through

k-1 for sequence number 2

CN-ik+1,…CN-(i-1)k authenticate metrics 0 through k-1 for sequence number i

C0 C1 C3C2 C5C4

C6 C7 C9C8 C10 C12C11

Each node generates a hash chain and distributes the last element (CN+1) to allow verification: Chain values CN-k+1, …, CN authenticate metrics

0 through k-1 for sequence number 1 CN-2k+1,…CN-k authenticate metrics 0 through k-1

for sequence number 2 CN-ik+1,…CN-(i-1)k authenticate metrics 0 through

k-1 for sequence number i

C0 C1 C3C2 C5C4

C6 C7 C9C8 C10 C12C11

Within a sequence number i: CN-ik+1 represents metric 0

CN-ik+2 represents metric 1

CN-ik+m+1 represents metric m

CN-ik+k represents metric k-1

C9 C10 C11

Metric 0 Metric 1 Metric 2When a node receives a routing update:• It first checks the metric authenticator• If the update is to be accepted:

– It increments the metric by one

– and hashes the authenticator

– then adds the metric and authenticator to routing table

operating system support for mobile devices

text wml

wml features http

adapting web content

html wml pages

wap response

wireless markup language

wireless security

wap gatewayfor web

Documents

mobile applications applications operating on mobile...

mobile testing solutions€¦ · mobile testing, with...

mobile devices

operating systems for wireless mobile devices dr. tal lavian...

system operating systems mobile devices and systems

limitations of mobile devices and mobile devices and · pdf...

adding and operating satel devices in partizan mobile

energy management in mobile devices with the cinder...

picking a winner - soti.neta mobile operating system is...

seeyou mobile help -...

operating systems for wireless mobile devices (cont)

introduction to the windows mobile guide - vodafone.de ·...

operating systems for wireless mobile devices

operating systems for wireless mobile devices (cont) dr. tal...

energy management in mobile devices with the cinder...

energy management in mobile devices with the cinder...

operating system support for mobile devices

software tools for low-level software and operating ... ·...

mobile device & os compatibility · 2020-05-04 · mobile...

social media on mobile handheld devices: the platforms,...