[Redoubt-checkins] CVS: docs index.html,1.1,1.2

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/redoubt/docs
In directory usw-pr-cvs1:/tmp/cvs-serv8214

Modified Files:
	index.html 
Log Message:
minor updates

Index: index.html
===================================================================
RCS file: /cvsroot/redoubt/docs/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** index.html	2002/01/17 19:24:52	1.1
--- index.html	2002/01/17 20:09:48	1.2
***************
*** 6,15 ****
  <H2>What it does</h2>

! The redoubt backup system lets you backup your files to one or
! more offsite
! computers that you do not fully trust (like the computer of a friends).
! All files will be encrypted before they are stored, and it allows you to use
! multiple mirrors or RAID like error correction so that you can restore your
! files even if some of your backup servers are no longer accessible.

  <h2>Main Features</h2>
--- 6,15 ----
  <H2>What it does</h2>

! The redoubt backup system lets you backup your files to one or more
! offsite computers that you do not fully trust (like the computer of a
! friend).  Redoubt encrypts all data before sending it anywhere, and it
! also allows you to use multiple mirrors or RAID-like error correction
! so that you can restore your files even if some of your backup servers
! are not accessible.

  <h2>Main Features</h2>
***************
*** 17,37 ****
  <ul>
  <li><b>Encryption:</b>
!      all files are encrypted using well known and configurable encryption
!      algorithm. There is even an option where every file is encrypted with a
!      different key. Even the original filenames are not visible in the
!      archive.
       <p>

  <li><b>Secure connection:</b>
!      If desired all connections to the backup servers use SSL in order
!      to avoid leaking any information to sniffers. 
       <p>

  <li><b>Redundancy:</b>
!      Your files can either be backed up on one server, or, if you prefer
!      to have a bigger success of restoring your data, you can use one of
       the following options:
       <ul>
!      <li><i>Mirroring:</i> 
            this option lets you store a copy of your files on as many
            servers as you want. As long as you have access to at least
--- 17,38 ----
  <ul>
  <li><b>Encryption:</b>
!      All files are encrypted using well known and configurable encryption
!      algorithms such as AES (Rijndael). It will be possible to
!      encrypt every file with a different key and even the original
!      filenames are not visible in the archive.
       <p>

  <li><b>Secure connection:</b>
!      SSL is the default transport mechanism between clients and
!      backup servers to prevent eavesdropping, tampering, and message
!      forgery.
       <p>

  <li><b>Redundancy:</b>
!      Your files can be backed up on one server, or, if you prefer
!      to have better odds restoring your data, you can use one of
       the following options:
       <ul>
!      <li><i>Mirroring:</i>
            this option lets you store a copy of your files on as many
            servers as you want. As long as you have access to at least
***************
*** 52,65 ****

  <li><b>Multiple Policies:</b>
!      The configuration allows you to specify which files are more important 
!      than others. The important once will be backed up more regularly than the
!      others. This way you can preserve some bandwidth and avoid clogging 
!      your network pipe.
       <p>

  <li><b>Server options:</b>
!      If you offer your friends to host a backup server you can specify the 
       upload and download bandwidth each of your friends can use and vary it
!      during the day. This way you can avoid that one of them takes up all 
       the bandwidth on your DSL/Cable line. Additionally you can define the
       maximum number of bytes each friend can use on your system.
--- 53,66 ----

  <li><b>Multiple Policies:</b>
!      The configuration allows you to specify which files are more important
!      than others.  More important files can be backed up more often
!      than less important ones. This way you can preserve some bandwidth
!      and avoid overloading your network pipe.
       <p>

  <li><b>Server options:</b>
!      If you offer your friends to host a backup server you can specify the
       upload and download bandwidth each of your friends can use and vary it
!      during the day. This way you can avoid that one of them takes up all
       the bandwidth on your DSL/Cable line. Additionally you can define the
       maximum number of bytes each friend can use on your system.
***************
*** 68,81 ****
  <li><b>Multiple Backups:</b>
       You can specify how many versions of each file should be kept on the
!      server.
       <p>

  <li><b>Small Bandwidth:</b>
!      The protocol used to talk to the server has been optimized for backups,
!      in order to preserve as much bandwidth, Server CPU cycles and space as
!      possible while creating backups. Restoring single files is cheap too, but
!      restoring the full backup is slightly more expensive on the server side,
!      as it has to create some listings that need to be sent to the restoring
!      computer.
       <p>

--- 69,82 ----
  <li><b>Multiple Backups:</b>
       You can specify how many versions of each file should be kept on the
!      server.  (So you can restore older versions of any file.)
       <p>

  <li><b>Small Bandwidth:</b>
!      The client-server protocol has been optimized for backups
!      in order to use as little bandwidth, server CPU cycles, and space as
!      possible.  Restoring single files is inexpensive too, but
!      restoring the full backup is slightly more expensive on the
!      server side since it must generate file listings to be sent to
!      the restoring computer.
       <p>

***************
*** 90,97 ****

  <li><b>Reusing Technology:</b>
!      To simplify the implementation we decided to use apache as a backup
!      server (using cgi scripts for the prototype and eventually a real
       module). This means that we will also use the standard HTTP and HTTPS
!      protocol. 
       <p>

--- 91,98 ----

  <li><b>Reusing Technology:</b>
!      To simplify the implementation we decided to use Apache as a backup
!      server (using CGI scripts for the prototype and eventually an Apache
       module). This means that we will also use the standard HTTP and HTTPS
!      protocol.
       <p>

***************
*** 101,111 ****
  <h2>Current Status</h2>

! We are currently creating the specs for backup clients, backup servers and the
! protocol and implementing a prototype. 

  <h2>Sourceforge</h2>

! All important files are accessible via our 
! <a href=http://sourceforge.net/projects/redoubt/>sourceforge page</a>
!           
! 
--- 102,112 ----
  <h2>Current Status</h2>

! We are currently creating the specifications for backup clients,
! backup servers, and the redoubt API as we implement the initial
! prototype.

  <h2>Sourceforge</h2>

! All important files are accessible via the <a
! href=http://sourceforge.net/projects/redoubt/>redoubt SourceForge
! page</a>