veyepar: Making Mobile Communications Secure

Author(s):	Paul Gardner-Stephen
Location	MCC5
Date	jan Wed 30	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	11:25	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30058/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Making_Mobile_Communications_Secure.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

GSM/3G are surprisingly insecure, which is sad since good cryptographic frameworks exist.  During the past year the Serval Project has been working on integrating very strong security into voice, text and data transfers on a mesh network. Rather than implement a secure SIP and secure RTP combination, we have taken a fresh approach and created a light-weight but secure packet and voice transport that is designed from the ground up with mesh networking in mind.  One of the key innovations is using public keys as the network address, so that no key exchange or verification is required to setup an end-to-end encrypted channel.  Consideration has also been given to how to defeat man-in-the-middle attacks for peers who are not able to verify each others keys prior to connection.

The system will be demonstrated in it's intended application in open-source Serval Mesh telephones to allow secure telephone calls.

Part of the talk will discuss the technical details of the security model, but (hopefully) in a fairly accessible manner that most developers should be able to follow, and in particular avoiding getting buried in mathematics.  Feedback on the security model is invited so that any obvious vulnerabilities can be addressed before the software becomes widely distributed.

Comment:

production notes