OREFS

Open Remote Encrypted File Synchronization

Orefs is a file synchronization application. The need for Orefs came from the discontinuation of Apple's iDisk. Orefs provides a means to backup to a remote host. Orefs encrypts and compresses backups to save space and provide a layer of security not found in iDisk or other backup schemes. Backups are stored as individual files to provide finer granularity in recover if everything else falls apart.

Orefs is also a demonstration of the Opee gem which utilizes an alternative approach to dealing with multiple threads.

Source

GitHub repo: https://github.com/ohler55/orefs

RubyGems repo: https://rubygems.org/gems/orefs

Links of Interest

Object-based Parallel Evaluation Environment the gem Orefs is built on.

Release Notes

Release 0.1.0

Plans and Notes

Orefs has only recently been opened up for public viewing. It is barely ready for use. I am using it to backup some financial records but I am also keeping copies on more than one computer in case something fails. So far the basic backup functionality works with backups encrypted and compressed on a remote server. Adding new files and making modifications works just fine. Removing files has not been implemented yet and changing ownership or mode only take effect if the file is touched as well. Feel free to give it a try and let me know when you run into bugs.

Installation

Installation requires Ruby 1.9.3. After that, install the orefs gem.

gem install orefs

The net-ssh and net-sftp gems are also needed as are the oj and opee gems.

gem install net-ssh
gem install net-sftp
gem install oj
gem install opee

GnuPG must be installed. It can be down loaded from GnuPG.org. Follow the instruction on GnuPG.org site for installation.

Orefs is now ready to use.

Usage

After a directory has been selected for backing up orefs_sync can be run to copy the directory to a remote server. For purposes of this description the directory to be backed up is ~/backup.

A passphrase file will also be needed for encryption. The recommended location is in a ~/.orefs directory. The contents of the file will be the passphrase for gpg.

Make sure you have a remote server that has an sftp and ssh daemon running. Your credentials must be set in the authorized_keys file. If you can login without a password it is set up correctly.

The first time orefs_sync is used to backup a directory information about the remote server must be provided. After the first time that information is not needed again. Alternatively a ~/.orefs/remotes file can be set up before running orefs_sync.

To backup to my_server.remote.com for user me to the backup directory on the remote server with a passphrase file of ~/.orefs/backup.pass the following command should be executed.

orefs_sync -r me@my_server.remote.com:~/.orefs/backup.pass ~/backup

A file named ~/backup/.orefs/remote will be created with the connection information for future invocations so that the next time a backup is made on the ~/backup directory the command only needs to be:

orefs_sync ~/backup

License:

Copyright (c) 2012, Peter Ohler
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

 - Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.

 - Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.

 - Neither the name of Peter Ohler nor the names of its contributors may be
   used to endorse or promote products derived from this software without
   specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.