I am a fourth year Computer Science PhD student at Stanford University. I work with David Mazières in the Secure Computer Systems group and Phil Levis in the Stanford Information Networks Group. I work on a new framework for building secure web platforms called Hails and a network architecture for Bluetooth Low Energy called Beetle. I am also collaborating with folks at Stanford, Berkeley and Michigan on a new operating system for embedded devices. I’m generally interested in distributed systems, embedded systems, security, privacy, programming languages and good will towards people.

I am also currently working on MemCachier - memcache-as-a-service for web applications hosted on platforms like Heroku, cloudControl or directly on EC2. I do not generally recommended starting a business while in grad school, but if you have to – and sometimes you have to – I highly recommend doing it with someone pleasant, like my co-conspirator David Terei.

Background

In December 2010 I graduated from the University of Washington with an MSc in Computer Science and a BSc in Computer Science and Economics. On the computer science side of things, I worked with Roxana Geambasu, Hank Levy, Tadayoshi Kohno and Arvind Krishnamurthy on web privacy and distributed systems. On the economics side of things I worked on writing exams with as little preparation as possible. In hind sight I should have taken classes in something useful, like history, instead.

Between UW and Stanford I sat at StartPad, a co-working space in Seattle, where I worked on projects with my friend Courty Stanton for fun and profit.

I’ve interned at Google (a popular surveillance system and search engine), once developing distributed testing tools and again building tools to help developers schedule their cluster jobs. Before that I worked at the Grameen Foundation as an intern on the MIFOS (Micros Finance Open Source) project. Before that, I spent my summers as a day-camp counselor at a performing arts camp.

Current Projects

Beetle

Bluetooth Low Energy is an ultra-low power link layer designed for personal area networks and ubiquitous computing. This efficiency comes at the cost of flexibility: each ultra-low power peripheral can communicate with at most one controller (phone) and only one application on that phone can interact with it. These and other restrictions preclude many interesting applications. Beetle is a new communication architecture which removes many of Bluetooth Low Energy’s restrictions. Using Beetle, peripherals that share a coordinator can directly communicate with one another, many applications can use a peripheral simultaneously, and peripherals can share phone services such as its sensors as well as data from the Internet.

Next-Gen Mote Platforms

Forthcoming…

Hails

Hails is a web platform framework that obviates the traditional trade-off in extensible web applications between privacy/confidentiality and extensibility. Hails leverages language-level information flow control in Haskell to enable feature rich applications to share data while ensuring that security policies are carried over and enforced along with the data. Traditionally, web applications allow extensibility by exposing an API. “Blessed” third-party apps that granted access to the API (or a subset of the API) are entrusted with (often sensitive) user data to do what they please. This is problematic not only because third-party app developers may be malicious, but more practically because it reduces the trustworthiness of a platform to the least trustworthy third-party developers (who is often incentivized to prioritize features over security). Hails addresses this problem by tying security policies to data using information-flow-control labels. In Hails, a common, trusted, platform ensures that apps that have seen sensitive data may communicate with users, files, database etc, that are not privileged to see that data. Moreover, as opposed to traditional platforms where there is a host application that has more access to data than third-party apps, in Hails all apps have the same access to data. This enables developers to build complete alternatives to applications without requiring users to migrate their data or give up network effects.

Previous Projects

Comet

Comet extended the distributed key-value storage abstraction to facilitate the sharing of a single storage system by applications with diverse needs, allowing them to reap the consolidation benefits inherent in today’s massive clouds. Distributed key-value storage systems are widely used in corporations and across the Internet. We wanted to greatly expand the application space for these systems through application-specific customization. We designed and implemented Comet, an extensible, distributed key-value store. Each Comet node stores a collection of active storage objects (ASOs) that consist of a key, a value, and a set of handlers. Comet handlers run as a result of timers or storage operations, such as get or put, allowing an ASO to take dynamic, application-specific actions to customize its behavior. Handlers are written in a simple sandboxed extension language, providing safety and isolation properties. We implemented a Comet prototype for the Vuze distributed hash table, deployed Comet nodes on Vuze from PlanetLab, and built and evaluated over a dozen Comet applications.

Vanish

Today’s technical and legal landscape presents formidable challenges to personal data privacy. First, our increasing reliance on Web services causes personal data to be cached, copied, and archived by third parties, often without our knowledge or control. Second, the disclosure of private data has become commonplace due to carelessness, theft, or legal actions. In Vanish our goal was to protect the privacy of past, archived data - such as copies of e-mails maintained by an email provider - against accidental, malicious, and legal attacks. Specifically, we wanted to ensure that all copies of data become unreadable after a user-specified time, without any specific action on the part of a user, and even if an attacker obtains both a cached copy of that data and the user’s cryptographic keys and passwords. Vanish achieved this by integrating cryptographic techniques with global-scale, peer-to-peer, distributed hash tables.

Workload Characterization

During summer 2010, I worked with Joseph L. Hellerstein at Google. We targeted a set of key questions that developers scheduling jobs on a cluster care about, but are hard or impossible to answer with existing tools: Will a job schedule? What changes to a job would make it more likely to schedule? Which resources can a job consume more of without impacting the ability to schedule it? Our challenge was to define metrics that accurately and predictively describe a job given the cluster it was scheduled on, and to compute those metrics efficiently enough to allow for interactive exploration of job configuration. We chose to estimate the number of scheduling slots available to a job over the past two weeks. However, computing the actual count is too expensive to do interactively. Our approach was to perform continuous statistical characterization of machine loads, and to compute an estimate of the number of slots based on that characterization. As a result we were able to build tools that give developers a meaningful way to compare different job configurations.

Conferences

Demos

Technical Reports

Graduate Coursework

Stanford

Functional Systems in Haskell (CS 240H): Autumn 2011, instructor David Mazières Project: FriendStar: Extensible Web Applications with Information Flow Control. Paper [PDF], Code [GitHub]

University of Washington

Implementation of Programming Languages (CSE 501): Autumn 2010, instructor Michael Ernst
Project: Faster Real-Time Classification Using Compilation. Materials forthcoming.

Molecular Programming (CSE 505): Spring 2010, instructor Georg Seeling

Human Computer Interaction (CSE 510): Spring 2010, instructor James Fogarty
Project: Community detection in Social Networks. Presentation [PPTX, PDF], Paper [PDF]

Operating Systems and the Web (CSE 599W): Winter 2010, instructor Steve Gribble

Design and Analysis of Algorithms (CSE 521): Winter 2010, instructor Paul Beame

Computer Systems Research (CSE 551): Autumn 2009, instructor Tom Anderson.
Project: Distribued Queue. Presentation [PDF], Paper [PDF]

Selected Undergraduate Coursework

Design & Implementation of Large Scale Clusters (CSE 490H):
Autumn 2009, instructor Ed Lazowska.
Project: Distributed Hash Table. Website (contains paper and presentation links)

Teaching

I have been a teaching assistant for three courses over seven quarters

  • CSE 143 (Intro II) - Spring, Summer, Fall 07, Winter 08
  • CSE 190M (Web Programming) - Spring 08
  • CSE 341 (Programming Languages) - Fall 08, Winter 09

Simple

Source: GitHub Package: Hackage Website: http://simple.cx

Simple is “framework-less” web framework for Haskell web applications. Unlike many other frameworks, Simple does not enforce a particular structure or paradigm for web applications. Rather, Simple provides enough infrastructure to help you create your own patterns (or re-create existing ones). Simple is minimalist, providing a lightweight base. Everything else (e.g. sessions, controllers, persistence, caching) is provided in composable units, so you can include only the ones you need in your app, and easily replace with your own components.


Postgresql-ORM

Source: GitHub Package: Hackage

An ORM (Object Relational Mapping) and migrations DSL for PostgreSQL. See Database.PostgreSQL.ORM for documentation.


MemJS

Source: GitHub Packge: npm Documentation: WWW

MemJS is a pure Node.js client library for accessing the MemCachier service and other memcache servers. It uses the binary protocol and support SASL authentication. It is currently my most popular project, with nearly 2000 downloads a day from npm (it is used extensively by Heroku app-developers, and Heroku recompiles app dependencies once a day, so this probably accounts for most of the downloads).


dp

Source: GitHub

A simple tool that uses the great powers of daemon tools to give a simple way to manage a long-lived process on a remote server. Think of it like a cheap and cheerful Heroku interface to your server for running and deploying simple applications.

Coypond

Source: GitHub Gem: RubyGems

Coypond is a semantic grep-like tool for Ruby. You can use coypond to search through ruby code for class, module, or method definitions. It indexes the class, module and method names in a Ruby code base, noting the files they were found in and the locations within those files. It can search through specific files, source code directory trees, or through locally installed gems.

Coypond uses ripper (a built in library as of Ruby 1.9) to generate parse trees from Ruby source files. These parse trees are then use to create an inverted index of the code, annotated with semantic information like whether the definition is a class, module or method.


Jsss - JavaScript Secret Sharing

Source: GitHub

A Shamir Secret Sharing library in JavaScript. Shamir Secret Sharing splits data into n shares, such that only k (<=n) are needed to reconstruct the original data. Possession of any fewer than k shares discloses nothing about the original data. The algorithm generates shares by evaluating a k-1 polynomial, based on the data, at n arbitrary points. We get the data back by performing polynomial interpolation over k of the shares.

Javascript uses variable length numbers natively but breaks arbitrarily when computing large numbers. To mitigate this, the library uses Matthew Crumley‘s BigInteger library and a rational number class that uses fractions under the hood to compute arbitrarily complex numbers accurately. This reduces the speed of generating and recombining shares, but it computation is not feasible and pretty low values of k otherwise.


Source: GitHub

I built the first version of this when I was in Central America in Winter 2011, used it to put up a bunch of content for that trip and my visits to grad schools - it was great. Later, I rebuilt it to use Rails 3.1, lost all of my data and started using the new version for my trip to Berlin with Courty.

The only real benefit over any other CMS is that checking into a location (like a city somewhere in Nicaragua) is a built in feature and pretty easy. It means that I can update my blog without writing anything, and have to checkin with my family a little less often. Checkins are strung together into trips, and posts can be tied to those trips, or even specific checkins. This means that getting an overview of where/how someone has traveled and what they did along the way is easy. Unfortunately, it is highly feature incomplete…

GPG Key: A211 AA8C B817 13AF 6352 F8B5 838F A1C7 17F6 0F73

Some Friends’ Websites:

A Partial List of Awesome Movies…

  • Pulp Fiction
  • Y tu mamá también
  • The Diving Bell & The Butterfly
  • Eternal Sunshine of the Spotless Mind
  • Volver
  • Annie Hall
  • Slackers
  • I Heart Huckabees
  • The Life Aquatic, The Royal Tenenbaums, Fantastic Mr. Fox, and everything else Wes Anderson…
  • The Bubble
  • Le Placard

Special Category: The Room

Places I’ve Traveled

I try to travel as much as possible - usually alone, but sometimes with friends. I don’t normally take pictures or keep a journal or anything, so this is mostly for me to remember where I’ve been. Alphabetically by region, then country, I’ve been to:

  • Americas:
    • Canada: Vancouver, Victoria, Montreal, Jasper, Lake Louise
    • Mexico: Cancun, Chichen Itza, Tulum, Valladolid, Playa del Carmen, Cozumel
    • Guatemala: Antigua
    • El Salvador: San Salvador, Los Cobanos, Morazan
    • Honduras: San Pedro Sula, Utila
    • Nicaragua: Leon, San Juan Del Sur
    • Costa Rica: San Jose, Alajuale, Monteverde, Tamarindo, Samara
  • Asia:
    • Thailand: Chiang Mai, Ko Tao
  • Europe:
    • Belgium: Bruges
    • Denmark: Copenhagen
    • France: Paris, La Plagne, Chamonix
    • Germany: Frankfurt, Berlin
    • Hungary: Budapest
    • Italy: Rome, Florence, Bologna, Milan, Venice, Padua, Treviso, Trieste, Ischia
    • Spain: Barcelona, Granada, Seville
    • Switzerland: Geneva, Zurich, Gimmelwald
    • Netherlands: Amsterdam
    • Sweden: Gothenburg
    • UK: London, Edinburgh
  • Middle East:
    • Jordan: Petra
    • Palestine: Bethlehem