SliTaz Repositories

     1.1 --- a/README	Sat Jun 11 18:08:22 2011 +0200
     1.2 +++ b/README	Sat Jun 11 18:59:59 2011 +0100
     1.3 @@ -2,77 +2,77 @@
     1.4  ===============================================================================
     1.5  
     1.6  
     1.7 -Ssfs is a personnal and secure, fast and light online file storage powered by
     1.8 -SSH, Rsync, Lsyncd and SHell script. It monitor a local folder and automaticaly
     1.9 -synchronize the remote server, when files are tranfert they are compressed and
    1.10 -encrypted with SSH. Connection to the remote host is automate with a RSA key,
    1.11 -and for each client the key must be sent to the server via SSH password login.
    1.12 +Ssfs is personal, secure, fast and light online file storage powered by
    1.13 +SSH, Rsync, Lsyncd and SHell script. It monitors a local folder and automatically
    1.14 +synchronizes the remote server. When files are transferred they are compressed and
    1.15 +encrypted with SSH. Connections to the remote host are automated with a RSA key,
    1.16 +and for each client the key must be sent to the server via a SSH password login.
    1.17  
    1.18 -Using ssfs let you have a live synchronized and secure folder between many
    1.19 -computers with an online copy on a secure Linux server. But even without
    1.20 -connections you have access to your files. Connection to the remote server
    1.21 +Using ssfs lets you have a live synchronized and secure folder between many
    1.22 +computers with an online copy on a secure Linux server. But even without any
    1.23 +connections you have access to your files. Connections to the remote server
    1.24  can also be done using the command line and 'ssh' from any clients such as
    1.25  BSD, Android, OSX or Windows via Putty.
    1.26  
    1.27 -Ssfs is very easy to install, setup and configure to make you own secure online
    1.28 -file storage. It provide a cmdline tool for the client and the server with a
    1.29 -build in help, this README is also a howto in itself.
    1.30 +Ssfs is very easy to install, setup and configure to make your own secure online
    1.31 +file storage. It provides a cmdline tool for the client and the server with a
    1.32 +built in help. This README is also a howto in itself.
    1.33  
    1.34  On the server side admin can choose by creating standard accounts or chrooted
    1.35 -accounts wich enforce server security by restricting available commands in a
    1.36 +accounts which enforce server security by restricting available commands in a
    1.37  minimal chroot environment. User $HOME should be set to 0700 so users can't see
    1.38  other users files.
    1.39  
    1.40  
    1.41  Installation
    1.42  ------------
    1.43 -To work you need an SSH client, 'rsync' and 'lsyncd' installed, on SliTaz you
    1.44 -can simply install ssfs and it dependencies or to 'make install' from the
    1.45 +To work you need a SSH client, 'rsync' and 'lsyncd' installed. On SliTaz you
    1.46 +can simply install ssfs and it's dependencies or 'make install' from the
    1.47  source directory (see the Development section). 
    1.48  
    1.49  
    1.50  Client help and setup
    1.51  ---------------------
    1.52 -The cmdline interface ssfs let you setup a client and start the daemon and live
    1.53 -synchronization with your system session via the Window Manager autostart
    1.54 -script or your personnal ~/.profile file. To get a list of commands with
    1.55 +The cmdline interface ssfs lets you setup a client and start the daemon and
    1.56 +synchronize live with your system session via the Window Manager autostart
    1.57 +script or your personal ~/.profile file. To get a list of commands with
    1.58  a short description:
    1.59  
    1.60  $ ssfs help
    1.61  
    1.62  To setup a client by creating a Lua configuration file and sending the RSA key
    1.63  to the server, you can use the command 'setup'. Setup needs a login name and
    1.64 -server name or IP adress and it will also create a secure RSA if no existing:
    1.65 +server name or IP address and it will also create a secure RSA if none exists:
    1.66  
    1.67  $ ssfs setup --login=user --host=server
    1.68  
    1.69  
    1.70  GUI & Web interface
    1.71  -------------------
    1.72 -Actually they is a smal GTK/Yad but no web interface. The tool ssfs-box will
    1.73 -dipply info if a configuration file exist or start the setup box.
    1.74 +Actually there is a small GTK/Yad but no web interface. The tool ssfs-box will
    1.75 +display info if a configuration file exists or start the setup box.
    1.76  
    1.77  
    1.78  Get configs on boot
    1.79  -------------------
    1.80 -Ssfs can be used in a boot scripts to connect to remote host and retrive data
    1.81 -before user session is started. It can be usful to provide persitent data for
    1.82 +Ssfs can be used in a boot scripts to connect to a remote host and retrieve data
    1.83 +before a user session is started. It can be useful to provide persistent data for
    1.84  Live systems and web boot.
    1.85  
    1.86  
    1.87  Server setup
    1.88  ------------
    1.89  On the server you must have a SSH server running and an user account with a
    1.90 -~/Sync folder. If you want to create a chroot for users you can use use the
    1.91 +~/Sync folder. If you want to create a chroot for users you can use the
    1.92  tool ssfs-server. Here is a short example to create a chroot and create a user
    1.93 -login 'tux-sync' with a protected $HOME in the chroot, the root directory can
    1.94 +login 'tux-sync' with a protected $HOME in the chroot. The root directory can
    1.95  be specified on the command line or changed in the configuration file:
    1.96  
    1.97  # ssfs-server gen-chroot
    1.98  # ssfs-server adduser --login=tux-sync --id=2000 --pass=tuX0cc
    1.99  
   1.100 -Users can be listed or completely deleted including all file in home. More
   1.101 -information with: ssfs-server usage
   1.102 +Users can be listed or completely deleted including all files in home. More
   1.103 +information can be found with: ssfs-server usage
   1.104  
   1.105  
   1.106  Server users config
   1.107 @@ -84,19 +84,19 @@
   1.108  
   1.109  Development and Bugs
   1.110  --------------------
   1.111 -If you want to install latest code to test and help in developement you can
   1.112 -clone ssfs Mercurial repository. As usual cose folloy SliTaz light philosofy
   1.113 -with speed and security in mind:
   1.114 +If you want to install the latest code to test and help in development you can
   1.115 +clone the ssfs Mercurial repository. As usual, closely follow the SliTaz light 
   1.116 +philosophy with speed and security in mind:
   1.117  
   1.118   $ hg clone http://hg.slitaz.org/ssfs
   1.119  
   1.120 -Install with 'make install' (DESTDIR is supported for packaging), update POT
   1.121 -file if any new string have been added with 'make pot' and merger PO files with
   1.122 -the command 'make msgmerge'. Any ideas are welcome and can be discuss, if you
   1.123 +Install with 'make install' (DESTDIR is supported for packaging), update the POT
   1.124 +file if any new strings have been added with 'make pot', and merger PO files with
   1.125 +the command 'make msgmerge'. Any ideas are welcome and can be discussed. If you
   1.126  are searching for something to do you can have a look to the TODO file :-)
   1.127  
   1.128 -Bugs can be reported on SliTaz mailing list, forum or scn since devel forum is
   1.129 -synced, all sites are liked from the main website at: http://www.slitaz.org/
   1.130 +Bugs can be reported on the SliTaz mailing list, forum or scn since the devel forum 
   1.131 +is synced. All sites are liked from the main website at: http://www.slitaz.org/
   1.132  
   1.133  
   1.134  ===============================================================================

     2.1 --- a/TODO	Sat Jun 11 18:08:22 2011 +0200
     2.2 +++ b/TODO	Sat Jun 11 18:59:59 2011 +0100
     2.3 @@ -1,4 +1,4 @@
     2.4  
     2.5 -	* Check if can use only Dropbear as SSH clinet and server.
     2.6 +	* Check if we can use only Dropbear as SSH client and server.
     2.7  	* A Web interface in CGI (SHell or Python) or PHP.
     2.8  	* Handle user quota.