diff options
Diffstat (limited to 'report/chapters')
| -rw-r--r-- | report/chapters/5-con-f.tex | 47 |
1 files changed, 24 insertions, 23 deletions
diff --git a/report/chapters/5-con-f.tex b/report/chapters/5-con-f.tex index 0a459b4..0273c5e 100644 --- a/report/chapters/5-con-f.tex +++ b/report/chapters/5-con-f.tex @@ -6,15 +6,15 @@ about building and creating things in a self-motivated and self-directed way.}{\textit{Moxie Marlinspike}} -combox is at a stage where it can be used by users as a tool to use -the storage provided by two file storage providers -- Google Drive and -Dropbox -- such that only part of each file in the encrypted form is -stored on the computers of the file storage providers; this method of -storing files on file storage providers makes it difficult but not -impossible for ``third parties'' to gain access to the user's personal -files. +combox is at a stage where it can be used as a tool to use the storage +provided by two file storage providers -- Google Drive and Dropbox -- +such that only part of each file in the encrypted form is stored on +the data store of the file storage providers; this method of storing +files on file storage providers makes it difficult but not impossible +for file storage providers or ``third parties'' to gain access to the +user's personal files. -combox is at version 0.2.2, it is a python package licensed under the +combox is at version 0.2.3, it is a python package licensed under the GNU General Public License version 3 or later. It is compatible with GNU/Linux and OS X. The program is considered to be in ``alpha'' stage and must be used for experimental use only, it is not recommended to @@ -43,30 +43,30 @@ follows is a non-exhaustive list of things to do in the future: to the node directories. This assumption was found to be not true when manually testing combox with node clients (Google Drive and Dropbox client that sync files to/from the respective node - directories to/from their respective servers); both the Google Drive - and the Dropbox client make modifications to the Google Drive and - Dropbox directory respectively whenever pulling a modified shard - from their server to this computer, this behavior broke combox and - major changes were made to the \verb+combox.events+ module to make - it understand the node client's behavior in the node directory; - these changes, increased the complexity of the classes defined in - the \verb+combox.events+; it would be great to re-think this module - in such a way that it reduces its complexity. + directories to/from their respective data stores); both the Google + Drive and the Dropbox client make modifications to the Google Drive + and Dropbox directory respectively whenever pulling a modified shard + from their data store to the user's computer, this behavior broke + combox and major changes were made to the \verb+combox.events+ + module to make it understand the node client's behavior in the node + directory; these changes, increased the complexity of the classes + defined in the \verb+combox.events+; it would be great to re-think + this module in such a way that it reduces its complexity. \item Evaluate if more information needs to tracked about each file in the combox directory; at the moment, combox only keeps track of the - SHA256 hash of each file stored in the combox directory. + SHA-256 hash of each file stored in the combox directory. \item Support more file storage providers; for this, ideally no code needs to be written for supporting a new file storage provider, combox must be tested with the new file storage provider's directory as a node directory. If the new file storage provider's client (that - sync's the shards their servers) makes non-standard changes to its + sync's the shards their data store) makes non-standard changes to its directory (like the official Dropbox and Google Drive clients do), then the \verb+combox.events.NodeDirMonitor+ must be accordingly updated to make combox cognizant about the file storage provider client's non-standard behavior. \item Make unit tests more modular. At the moment, there are some unit test functions that test more than one usecase/facet of a function - or class; for instance, the \verb+test_CDM+ test method part of the + or class; for instance, the \verb+test_CDM+ test method, part of the the \verb+tests.events_test.TestEvents+ test class tests the correctness of the \verb+combox.events.ComboxDirMonitor+ for file creation, deletion, rename and modification; this method would @@ -77,9 +77,10 @@ follows is a non-exhaustive list of things to do in the future: \ref{a-python3c} for more information on this. \item Support Microsoft Windows. The way to make combox compatible with Windows will be to run unit tests on Windows, the failing tests - might give pointers to what parts of combox needs to be changed in - order for it to be compatible with Windows. Individuals interested - in making combox compatible with Windows might find + might give pointers to what parts of combox needs to be + changed/updated in order for it to be compatible with + Windows. Individuals interested in making combox compatible with + Windows might find \url{https://ricketyspace.net/combox/setup/#windows} useful; it contains information about setting up the development environment for combox on Windows. |