1. ObliviSync: Practical Oblivious File Backup and Synchronization 2017 NDSS ORAM Storage
    Adam J. Aviv and Seung Geol Choi and Travis Mayberry and Daniel S. Roche
    [View PDF on eprint.iacr.org]
    [Show BibTex Citation]

    author = {Adam J. Aviv and
    Seung Geol Choi and
    Travis Mayberry and
    Daniel S. Roche},
    title = {ObliviSync: Practical Oblivious File Backup and Synchronization},
    booktitle = {24th Annual Network and Distributed System Security Symposium, {NDSS}
    2017, San Diego, California, USA, February 26 - March 1, 2017},
    year = {2017},
    url = {https://www.ndss-symposium.org/ndss2017/ndss-2017-programme/oblivisync-practical-oblivious-file-backup-and-synchronization/},
    timestamp = {Tue, 16 Jan 2018 15:43:37 +0100},
    biburl = {https://dblp.org/rec/bib/conf/ndss/AvivCMR17},
    bibsource = {dblp computer science bibliography, https://dblp.org}

Oblivious RAM (ORAM) protocols are powerful techniques that hide a client’s data as well as access patterns from untrusted service providers. We present an oblivious cloud storage system, ObliviSync, that specifically targets one of the most widely-used personal cloud storage paradigms: synchronization and backup services, popular examples of which are Dropbox, iCloud Drive, and Google Drive. This setting provides a unique opportunity because the above privacy properties can be achieved with a simpler form of ORAM called write-only ORAM, which allows for dramatically increased efficiency compared to related work. Our solution is asymptotically optimal and practically efficient, with a small constant overhead of approximately 4x compared with non-private file storage, depending only on the total data size and parameters chosen according to the usage rate, and not on the number or size of individual files. Our construction also offers protection against timing-channel attacks, which has not been previously considered in ORAM protocols. We built and evaluated a full implementation of ObliviSync that supports multiple simultaneous read-only clients and a single concurrent read/write client whose edits automatically and seamlessly propagate to the readers. We show that our system functions under high work loads, with realistic file size distributions, and with small additional latency (as compared to a baseline encrypted file system) when paired with Dropbox as the synchronization service.