From f7708feda1e91f5da6e8ca2797d7594ed2f3350f Mon Sep 17 00:00:00 2001 From: Laurent Ghigonis Date: Mon, 17 Jun 2013 20:08:58 +0200 Subject: jsaccess: WIP on a real file store --- jsaccess/README.txt | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) (limited to 'jsaccess/README.txt') diff --git a/jsaccess/README.txt b/jsaccess/README.txt index 16f2c98..97813bd 100644 --- a/jsaccess/README.txt +++ b/jsaccess/README.txt @@ -31,10 +31,10 @@ Deployment There are 2 parts: * The jsa/ directory that contains html / javascript files, for the user to -access files list and download. jsa/files/ is the files store. +access files list and download. jsa/store/ is the files store. * The store.sh script for the web server owner to encrypt files It is recomanded to run store.sh on your laptop, and then syncronise the -jsa/files/ file store with your server. +jsa/store/ file store with your server. Put jsa/ directory on your web server, publicly available. @@ -48,9 +48,9 @@ On your laptop: $ ./store.sh myfile # Then enter the passphase you want to use for encryption. # It will tell you something like: -jsa/files/af022cd820fdad6cbcac8e15ac565c639a47dab0 -CREATED jsa/files/af022cd820fdad6cbcac8e15ac565c639a47dab0/065e18a7f246b800242a778a6e8dd07a3321dac6 -UPDATED jsa/files/af022cd820fdad6cbcac8e15ac565c639a47dab0/index.txt +jsa/store/af022cd820fdad6cbcac8e15ac565c639a47dab0 +CREATED jsa/store/af022cd820fdad6cbcac8e15ac565c639a47dab0/065e18a7f246b800242a778a6e8dd07a3321dac6 +UPDATED jsa/store/af022cd820fdad6cbcac8e15ac565c639a47dab0/index.txt 2. Syncronise the file store with you online server On your laptop: @@ -64,23 +64,23 @@ $ rsync jsa/ user@myserver:/var/www/htdocs/ How it works ============ -store.sh creates a directory jsa/files//. +store.sh creates a directory jsa/store//. It encrypts your file using AES256 with the passphrase and stores the result in -jsa/files//. +jsa/store//. It also updates the index of available files per directory called index.txt, that contains real file names. The index is also encrypted using AES256 with the passphrase. Web UI generates rmd160 hash from the passphrase and get the list of files -available for this passphrase (jsa/files//index.txt), +available for this passphrase (jsa/store//index.txt), decrypts it and shows the list of files. When the user clicks on Download, it fetches the file from the rmd160 name, decrypts it with the passphrase and stores it with the real name using the Filesaver JS API. -Dependencies -============ +Dependencies / Compatibility +============================ On the host that runs store.sh: * openssl @@ -90,22 +90,25 @@ On the web server: * Serving static files is enough * optional: https, to protect against clients targeted attacks +On the web user machine: +* Tested with Firefox 21 and Chrome 27 + Git content =========== jsa/ - should be on your webserver, can be renamed -jsa/files// - directory of files to download for a given password -jsa/files//index.txt - list of file name available +jsa/store// - directory of files to download for a given password +jsa/store//index.txt - list of file name available store.sh - to encrypt your files before uploading them to your web server TODO ==== -* Download progress +* web: download progress -* Decrypting progress +* web: decrypting progress Need to modify gibberish-aes -* Make password field appear as full of dots after validation +* web: make password field appear as full of dots after validation -- cgit v1.2.3-59-g8ed1b