Wired

Webmonkey

  • Web Dev & Design
    • Ajax
    • Backend
    • Blog Publishing
    • CSS
    • Databases
    • Fonts
    • Frameworks
    • HTML
    • HTML 5
    • JavaScript
    • Mobile
    • Multimedia
    • Programming
    • Security
    • UI/UX
    • Web Standards
  • Software & Apps
    • Browsers
    • Software
    • Web Apps
  • Platform & APIs
    • APIs
    • Identity
    • Location
    • Social
    • Web Services
  • Reference
    • Color Charts
    • HTML Cheat Sheets
    • Special Characters
    • Glossary
    • Templates
    • Code Snippets
  • twitter
  • facebook
  • RSS Feeds
Apr 23 2008
File Under: Web Basics

Keeping Hosted Data Secure from Its Host

  • By Paul Adams

ClipperzAs more and more applications move online, the issue of keeping secret data secret remains important. Lots of attention is paid to keeping third parties from snooping or stealing your hosted data — force SSL for your Gmail connection — but much less attention is paid to keeping data hidden from the host.

Nobody seems to mind Gmail’s bots reading through their email, and it seems to be widely okay that, for the convenience of putting your data on someone else’s server, you trust them to play nice with it.

That seems like a bizarrely trusting security model. It reminds me of the trusting design of SMTP, which worked great at first but, as it turned out, did nothing to inhibit spam. I think distrust should be the default.


When I played around with gmailfs, a clever hack that lets you mount all six-plus gigs of free Gmail storage as a Linux filesystem, I didn’t like the idea of Google having my data. So I wrapped it in encfs, which transparently encrypted everything I put on Google’s servers.

Likewise, when backing up to a third-party host, I use duplicity, which encrypts incremental archives.

Before smart people would consider keeping their password database remotely hosted, they’d want to feel pretty secure. Clipperz, an online password manager, manages that by doing JavaScript encryption, in the browser, so that the host never has the unencrypted data, ever. They can’t use it themselves, they can’t leave it on a bus, and they can’t be subpoenaed for it.

The “zero-knowledge” algorithm and protocol are designed to be fully auditable by the user. Here is a detailed explanation of how it works. The JavaScript crypto library they use is open-licensed and freely available.

I’d love to see that sort of security become standard for any web application that stores user data! Till then, there’s FireGPG.

See Also:

  • Encryption Still Good; Sleeping Mode Not So Much, PGP Says
  • Google Health Wants to Digitize Your Medical Records
  • Border Agents Can Search Laptops Without Cause, Appeals Court Rules
  • Yahoo Trumps Google With New Data Retention Policy

Tags: Security
  • Post Comment  | 
  • Permalink

Comments (3)

All fields required
  • Posted by: tim | 04/23/08 | 10:30 am

    sweet I was looking for Javascript crypto library.

  • Posted by: Tara Kelly | 04/23/08 | 1:17 pm

    What keeps the data unreadable by the host is the Host-Proof Hosting pattern — first theorized by Richard Schwartz in 2005: http://tinyurl.com/4ljh3g

    However “zero-knowledge web application” in the sense used by Clipperz, is not an algorithm, nor a protocol. It’s a conceptual extension of the Host-Proof Hosting pattern.

    A disclaimer is in order here: I’m a founder at PassPack online password manager. Both systems are based on the Host-Proof Hosting Pattern. And yes - it would be fantastic if we could get other SaaS apps to follow suit and really protect people’s data.

    Keep spreading the word!

    Cheers,
    Tara Kelly
    http://passpack.com

  • Posted by: sdga | 04/25/08 | 3:09 am

    http://www.minfish.cn
    http://www.utsource.net/sitemap/site_map-2407.htm
    http://www.utsource.net/sitemap/site_map-2406.htm
    http://www.utsource.net/sitemap/site_map-2405.htm

Webmonkey's Picks

Browse Our Tutorials

HTML, JavaScript, design and more

Cheat Sheets

HTML, CSS and special characters

Color Charts

Brighten up your pages

Cut & Paste Code

Templates and snippets you can steal

Recent Comments

  • Cialis-Injury-Lawyer on HTML Cheatsheet
  • John Bauer on Get Started With Python
  • Charles on Google Launches Web Store for Cloud-Based Apps
  • Abe on Drupal’s Creator Envisions Web Publishing’s Plug-and-Play Future
  • Marti on The Top Ten Reasons iTunes Sucks
  • Recent Articles

  • Webmonkey Goes South, Then West, for SXSWi
  • Shocker: New Study Shows Web Video Is Still a Mess
  • Google Launches Web Store for Cloud-Based Apps
  • Facebook Finds its Place in the Location-Sharing Landscape
  • Google Gets a New Geocoder
  • Corrections | Sitemap | FAQ | Contact Us | Wired Staff | Advertising | Press Center | Subscription Services | Newsletter | RSS Feeds
    Condé Nast Web Sites:
    Webmonkey | Reddit | ArsTechnica | Details | Golf Digest | GQ | New Yorker

    Registration on or use of this site constitutes acceptance of our User Agreement (Revised 4/1/2009) and Privacy Policy (Revised 4/1/2009).

    Wired.com © 2010 Condé Nast Digital. All rights reserved.

    The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of Condé Nast Digital.