Re: "secure Dropbox clone" (was: Re: [IAB] IETF88 Technical Plenary hums)

Vinayak Hegde <vinayakh@gmail.com> Thu, 07 November 2013 14:18 UTC

Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B3E11E81CA for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 06:18:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsEKyMSlp6y5 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 06:18:06 -0800 (PST)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 33F2211E824D for <ietf@ietf.org>; Thu, 7 Nov 2013 06:18:05 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id rq13so640924pbb.20 for <ietf@ietf.org>; Thu, 07 Nov 2013 06:18:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=v3YzIBF4raGpqyayYNoGR+gY7R5T7ncK8YRnESh7tf8=; b=g0qfh7a6QOr76568JzrkY0aBXxoSjAa37GVMRbuLi4EObway7THgyRxNOxt4rGrPRk IK1mnYv/FJi9k3A6aDYO7sWQ0C75ZWHwIdB88KnHKOXYV/lEuq9s08U6l8AE+c6s2b1T MbWXsPsdilMrtUbbZbwfXrXtvpsVQF/0nknMqxuZGkCNg8XJpkimcYr60q23tHu1CfBN TNMN2yGdv01EavnRImV7fgFaHnsOabYAcJh+rdfh2twaer+cff2VzLEzCUsR5pyPf3Ge qAXD3wnRHAVyXHo5xgrqrGr/X61UrFILJ5YHYOxQcfVaxF88YLK+GiJPMupa4jB6Mazk lhbQ==
MIME-Version: 1.0
X-Received: by 10.68.58.137 with SMTP id r9mr9267930pbq.148.1383833884907; Thu, 07 Nov 2013 06:18:04 -0800 (PST)
Received: by 10.66.26.112 with HTTP; Thu, 7 Nov 2013 06:18:04 -0800 (PST)
In-Reply-To: <559FCA81-CC65-437D-AD91-6693E219A991@netapp.com>
References: <D1A50FE6-2A1E-47C9-A440-3A0655B9E188@isoc.org> <50B4387E-8E32-4E73-91F8-44268C5F5865@vigilsec.com> <559FCA81-CC65-437D-AD91-6693E219A991@netapp.com>
Date: Thu, 7 Nov 2013 19:48:04 +0530
Message-ID: <CAKe6YvM93SbQuNLoCOk1c9iCKOeh2-71xd_uST-EJ7XTaftO6A@mail.gmail.com>
Subject: Re: "secure Dropbox clone" (was: Re: [IAB] IETF88 Technical Plenary hums)
From: Vinayak Hegde <vinayakh@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=bcaec544ef2223644404ea96ef29
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 14:18:07 -0000

There is Unison[1] which can sync across computers across networks and
across OSes (Windows ,Linux, etc). It is open-source (GPL-licensed ) and
trivial to setup. The transfer connections can be tunneled over encrypted
SSH.

I have been using it for a while and it works well for the set of
requirements you have noted.

-- Vinayak

1. http://www.cis.upenn.edu/~bcpierce/unison/


On Thu, Nov 7, 2013 at 6:31 PM, Eggert, Lars <lars@netapp.com> wrote:

> Hi,
>
> On 06 Nov 2013, at 12:41, Russ Housley <housley@vigilsec.com> wrote:
> > 5.  Many insecure protocols are used in the Internet today, and the IETF
> should create a secure alternative for the popular ones.
>
> since a "secure DropBox alternative" was brought up: the pieces for
> building such do exist, but some exist outside the IETF. For example,
> SNIA's CDMI (http://www.snia.org/cdmi) could be useful, and on the IETF
> side we have of course WebDAV.
>
> In many cases, the reason that such alternatives don't exist probably
> isn't because there aren't any open protocols available to build them with,
> it's that the proprietary services have polished clients that are simple to
> set up, available for many clients, and that they have a robust and
> well-managed backend. There's not much the IETF can do about these factors.
>
> In the specific case of DropBox clones, several vendors of storage systems
> (incl. my employer) are making or will shortly be making mobile clients
> available that use said storage systems as a backend instead of the public
> cloud. So at least for that particular application, there are alternatives
> available.
>
> Lars
>
>